Agent Skills
Read from each publisher's repository, labelled by what each skill lets an agent do. Nothing is run.
2,104 skills
- test-driven-developmentobra (Jesse Vincent)Use when implementing any feature or bugfix, before writing implementation codeInstructions only
- using-git-worktreesobra (Jesse Vincent)Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackInstructions only
- using-superpowersobra (Jesse Vincent)Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questionsInstructions only
- verification-before-completionobra (Jesse Vincent)Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysInstructions only
- writing-plansobra (Jesse Vincent)Use when you have a spec or requirements for a multi-step task, before touching codeInstructions only
- writing-skillsobra (Jesse Vincent) · 1 scriptUse when creating new skills, editing existing skills, or verifying skills work before deploymentRuns commands1 finding
- ask-mattMatt PocockAsk which skill or flow fits your situation. A router over the skills in this repo.Instructions only
- chief-of-staffMatt PocockPursue a long-running goal in a single session by co-ordinating subagents.Instructions only
- claude-handoffMatt PocockHand the current conversation off to a fresh background agent that picks up the work immediately.Instructions only
- code-reviewMatt PocockReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews i…Instructions only
- codebase-designMatt PocockShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabu…Instructions only
- diagnosing-bugsMatt Pocock · 1 scriptDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Reaches the networkRuns commands
- domain-modelingMatt PocockBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.Instructions only
- git-guardrails-claude-codeMatt Pocock · 1 scriptSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.Destructive commandsRuns commands1 high finding
- grill-meMatt PocockA relentless interview to sharpen a plan or design.Instructions only
- grill-with-docsMatt PocockA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.Instructions only
- grillingMatt PocockGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.Instructions only1 high finding
- handoffMatt PocockCompact the current conversation into a handoff document for another agent to pick up.Instructions only
- implementMatt PocockImplement a piece of work based on a spec or set of tickets.Instructions only
- implement-specMatt PocockImplement the result of /to-spec and /to-tickets in code.Instructions only
- improve-codebase-architectureMatt PocockScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Instructions only
- loop-meMatt PocockGrill me about specs for the workflows I want to build, within this workspace.Instructions only
- migrate-to-shoehornMatt PocockMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.Instructions only
- prMatt PocockUse when writing a PR body.Instructions only
- prototypeMatt PocockBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.Instructions only
- researchMatt PocockInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.Instructions only
- retroMatt PocockConduct a retrospective on a coding session.Instructions only
- scaffold-exercisesMatt PocockCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.Instructions only
- setup-matt-pocock-skillsMatt PocockConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.Instructions only
- setup-pre-commitMatt PocockSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.Instructions only
- setup-ts-deep-modulesMatt Pocock · 1 scriptWire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.Runs commands
- tddMatt PocockTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Instructions only
- teachMatt PocockTeach the user a new skill or concept, within this workspace.Instructions only
- to-questionnaireMatt PocockTurn a decision you can't fully answer into a questionnaire for someone else to fill in.Instructions only
- to-specMatt PocockTurn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.Instructions only
- to-ticketsMatt PocockBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).Instructions only
- triageMatt PocockMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.Instructions only
- wait-whatMatt PocockStop. That last message did not land: re-pitch it.Instructions only
- wayfinderMatt PocockPlan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.Instructions only
- wizardMatt Pocock · 1 scriptGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don'…Reaches the networkRuns commands1 high finding
Labels come from the skill's own files, read on the date shown: the tools its frontmatter allows and the scripts it ships. They are not a safety rating, and no finding is not a safety guarantee. How skills are checked.