Skills catalogue
All 27 skills in agent-skills. Install them once, then call one by name or describe what you want, and the agent picks the skill.
Filter by name or description
Skills shown:
Workflow
Move a task from a ticket to a commit, and keep the project around it healthy.
taskTask workflow
Runs a task from a tracker issue or a sentence to an approved local commit.
Use it when: You start, resume or hand over any piece of work.
Example:
/task 482commitCommit in project style
Proposes a message in the project's convention and commits only after you approve.
Use it when: A change is ready, or mixed changes need splitting.
Example:
/commithandoffHandoff and resume
Saves or reads a state file, so another agent or a new session can continue.
Use it when: You near a usage limit, switch agents or end the day.
Example:
/handoff resume 482orchestrateParallel subagents
Splits big work into independent parts, runs them in parallel, then merges and verifies.
Use it when: A job spans many independent modules or pages.
Example:
/orchestrate migrate all formsestimateTask estimation
Sizes a task in hours, with risks and open questions, without touching code.
Use it when: You need to size work before planning it.
Example:
/estimate 482ci-setupCI pipeline setup
Creates or fixes GitHub Actions or GitLab CI, and reviews workflows for security problems.
Use it when: A project has no CI, or CI is slow or flaky.
Example:
/ci-setupdeps-updateSafe dependency upgrades
Groups outdated packages by risk and upgrades one group at a time, with tests and a commit each.
Use it when: Dependencies are behind, or before a framework upgrade.
Example:
/deps-update
Quality and tests
Find problems before they reach a commit.
test-loopFocused test loop
Runs only the checks affected by the change and fixes failures in up to three attempts.
Use it when: You want green checks for the current change.
Example:
/test-loopbackend-testsBackend tests
Writes and runs backend tests with a test database, factories and mocked HTTP.
Use it when: New backend code needs tests.
Example:
/backend-testsapi-testsAPI contract tests
Contract and integration tests for REST and GraphQL, including sign-in flows and error cases.
Use it when: An API changes, or the spec and the code may disagree.
Example:
/api-testse2e-testsPlaywright end-to-end tests
Playwright specs for changed user flows, with flaky tests fixed at the cause.
Use it when: A user-facing flow changes or a test is flaky.
Example:
/e2e-testsload-testLoad testing
Runs k6, autocannon or Locust from smoke to stress and reads the results through a summary.
Use it when: You need capacity numbers or want to confirm a fix under load.
Example:
/load-test GET /api/ordersreviewSelf-review before commit
Reviews the diff before committing, with severity,
file:lineand a fix for each finding.Use it when: Before every commit or pull request.
Example:
/reviewdebugRoot-cause debugging
Reproduces, narrows down and proves the cause, then applies the smallest fix.
Use it when: Something is broken or a regression appeared.
Example:
/debugrefactorBehaviour-preserving refactor
Writes characterization tests first, then moves in small verified steps.
Use it when: Code must be split or cleaned up without changing what it does.
Example:
/refactor split OrderServicedb-migrationsSafe database migrations
Reviews and writes zero-downtime migrations for Django, Laravel, Prisma, Alembic, Flyway and Rails.
Use it when: A migration touches an existing table, especially a big one.
Example:
/db-migrationsi18nTranslations and i18n
Finds missing, empty and extra keys and placeholder mismatches, and extracts hard-coded strings.
Use it when: UI text changes or a language is added.
Example:
/i18nbrowser-checkHeadless browser check
Takes desktop and mobile screenshots of only the changed element and reports console errors, with your consent.
Use it when: A visible change should be checked.
Example:
/browser-check
Performance
Measure first, then prove the gain.
pagespeedPageSpeed and Web Vitals
Measures Core Web Vitals with PageSpeed Insights or local Lighthouse, then runs a fix-and-measure loop.
Use it when: A page is slow, or before a launch.
Example:
/pagespeed http://localhost:3000perf-backendBackend performance
Finds N+1 queries, adds indexes from EXPLAIN and proves the gain with before and after numbers.
Use it when: An endpoint is slow or runs too many queries.
Example:
/perf-backend
Security and accessibility
Check for what should never ship.
security-auditSecurity audit
Checks for secrets, vulnerable dependencies and dangerous code patterns. It only reads.
Use it when: Before a release or merge, or after adding sign-in or uploads.
Example:
/security-auditwcag-auditWCAG 2.2 AA audit
Reviews changed UI with axe-core and a targeted checklist, and gives concrete fixes.
Use it when: UI changes, or before an accessibility review.
Example:
/wcag-auditdockerDocker and compose review
Reviews and fixes Dockerfiles and compose files: multi-stage builds, pinned images, non-root users and secrets.
Use it when: You containerise an app, or before deploying.
Example:
/docker
Docs
Keep what people and agents read up to date.
project-docsProject knowledge docs
Builds a
.docs/folder and a shortAGENTS.mdorCLAUDE.mdthat points to it.Use it when: You bring agents or people into a project.
Example:
/project-docsseo-auditTechnical SEO audit
Checks meta tags, headings, canonical links, robots, sitemaps, hreflang, Open Graph and JSON-LD.
Use it when: You launch or move pages, or pages are not indexed.
Example:
/seo-auditrelease-notesRelease notes
Writes release notes and changelog entries from git history, in the project's style.
Use it when: You prepare a release.
Example:
/release-notes
Meta
Rules for how an agent works.
token-saverToken saver
Gives an agent rules for small context: search first, read line ranges and condense logs.
Use it when: A session grows long or you near a usage limit.
Example:
/token-saver
No skill matches. Try another word or show all categories.