Loading...
Loading...
Found 265 Skills
Audit and automatically optimize a lovstudio skill against repo conventions and official Anthropic skill-creator best practices, then bump the semver version and append a CHANGELOG entry. Checks SKILL.md frontmatter/trigger quality, script CLI hygiene, directory naming, README badge, and progressive disclosure structure. Prioritizes issues raised in the current conversation (e.g. bugs the user just hit) over a generic sweep. Use when the user asks to "optimize", "refine", "audit", or "polish" an existing skill, or when they say "bump version", "update changelog", or "fix this skill". Also trigger when the user mentions "优化 skill", "skill 审计", "刷一遍 skill", "skill-optimizer", "bump skill version", "update skill changelog".
Use when an agent needs to send outreach, reply to inbound, sign up for a service, or log into a site via the user's autark-provisioned AgentMail inbox. Everything goes through `autark mail`.
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
Validate TypeScript/JavaScript code quality with ESLint, Prettier, type checking, and security analysis. Use for TypeScript/JS codebases to ensure code quality and standards.
Run full project validation (typecheck + lint + format + test + build (optional))
Validate, lint, audit, or fix .gitlab-ci.yml pipelines, stages, and jobs.
Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs with useEffect, or when an agent adds useEffect "just in case." Provides the five replacement patterns and the useMountEffect escape hatch.
Lift a proven skill from a host repo (e.g. your OpenClaw fork) back into gbrain's bundle so other clients can scaffold it. Editorial workflow: the CLI does the file copy + privacy lint; this skill drives the judgment-heavy genericization (scrub real names, generalize triggers, lift fork-specific conventions to references).
Lint a clojure project using clojure-lsp CLI when user requests to lint
This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.
Writing skill for Chinese technical documentation and product copy — enforces clarity, correct typography, and avoids buzzwords.
Review Go implementations against spec acceptance tests. References go-conventions and agent-conduct.