mattpocock/skills

Agent skills in the GitHub repository mattpocock/skills, each with its code score out of 100.

Skills for Real Engineers. Straight from my .agents directory.

Repository score

62 / 100 C

Skills

39

Verified

0

Average skill score

54

GitHub stars

322,426

License

MIT

Open mattpocock/skills on GitHub

39 skills in this repository

1. setup-pre-commit

   Set 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-…

   79B
2. diagnosing-bugs

   Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

   78B
3. migrate-to-shoehorn

   Migrate 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.

   74B
4. domain-modeling

   Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

   73B
5. wizard

   Generate 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…

   67C
6. code-review

   Review 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 (doe…

   66C
7. wayfinder

   Plan 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 des…

   63C
8. to-tickets

   Break 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 f…

   62C
9. scaffold-exercises

   Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set…

   61C
10. codebase-design

    Shared 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…

    60C
11. setup-ts-deep-modules

    Wire 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-in…

    60C
12. prototype

    Build 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.

    59C
13. research

    Investigate 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 ga…

    59C
14. setup-matt-pocock-skills

    Configure 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.

    59C
15. tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    57C
16. triage

    Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

    57C
17. writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

    57C
18. grilling

    Grill 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.

    55C
19. git-guardrails-claude-code

    Set 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 operation…

    54D
20. improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    52D
21. to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

    52D
22. software-factory

    Shared language for designing a software factory: the tasks it runs and the services it plugs into.

    51D
23. implement-spec

    Implement the result of /to-spec and /to-tickets in code.

    50D
24. loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    50D
25. retro

    Conduct a retrospective on a coding session.

    50D
26. writing-beats

    Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

    50D
27. to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    48D
28. ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    47D
29. teach

    Teach the user a new skill or concept, within this workspace.

    47D
30. writing-shape

    Writing, exploit: shape raw material into an article, paragraph by paragraph.

    47D
31. writing-fragments

    Writing, explore: mine raw fragments, no structure yet.

    46D
32. pr

    Use when writing a PR body.

    45D
33. handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    43D
34. implement

    Implement a piece of work based on a spec or set of tickets.

    43D
35. wait-what

    Stop. That last message did not land: re-pitch it.

    42D
36. chief-of-staff

    Pursue a long-running goal in a single session by co-ordinating subagents.

    40D
37. grill-me

    A relentless interview to sharpen a plan or design.

    40D
38. grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    40D
39. claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    36F

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.