Matt Pocock's agent skills, reworked on Google's Open Knowledge Format
Skill Claude CodeCodex
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 more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Skill Claude CodeCodex
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Skill Claude CodeCodex
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Skill Claude Code
A relentless interview to sharpen a plan or design.
Skill Claude Code
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Skill Claude Code
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Skill Claude Code
Compact the current conversation into a handoff document for another agent to pick up.
Skill Claude Code
Implement a piece of work based on a spec or set of tickets.
Skill Claude Code
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Reconcile the OKF knowledge bundle (knowledge/) with what a completed code change built, over that change's diff. Use once a change has finished landing — the build closeout, just before committing — or when the user asks to reconcile knowledge against code.
Skill Claude CodeCodex
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 gathered, or reading legwork delegated to a background agent.
Skill Claude Code
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.
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Skill Claude Code
Teach the user a new skill or concept, within this workspace.
Skill Claude Code
Turn the current conversation into a spec and save it to the OKF knowledge bundle — no interview, just synthesis of what you've already discussed.
Skill Claude Code
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 a local file, or native blocking links on a real tracker.
Skill Claude Code
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Skill Claude CodeCodex
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 (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude Code
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Skill Claude Code
Ask which skill or flow fits your situation. A router over the skills in this repo.
Skill Claude Code
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: