Are mattpocock skills safe?
We index 38 public skills from mattpocock. 38 graded A. Each one is pinned to its content hash and rescanned nightly.
- A
ask-matt
297kmattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
No security findings - A
chief-of-staff
297kmattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
No security findings - A
claude-handoff
297kmattpocock/skills
Hand the current conversation off to a fresh background agent that picks up the work immediately.
No security findings - A
code-review
297kmattpocock/skills
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/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
No security findings - A
codebase-design
297kmattpocock/skills
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.
No security findings - A
diagnosing-bugs
297kmattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
No security findings - A
domain-modeling
297kmattpocock/skills
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.
No security findings - A
git-guardrails-claude-code
297kmattpocock/skills
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 operations, add git safety hooks, or block git push/reset in Claude Code.
No security findings - A
grill-me
297kmattpocock/skills
A relentless interview to sharpen a plan or design.
No security findings - A
grill-with-docs
297kmattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
No security findings - A
grilling
297kmattpocock/skills
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.
1 low - A
handoff
297kmattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
No security findings - A
implement
297kmattpocock/skills
Implement a piece of work based on a spec or set of tickets.
No security findings - A
implement-spec
297kmattpocock/skills
Implement the result of /to-spec and /to-tickets in code.
No security findings - A
improve-codebase-architecture
297kmattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
No security findings - A
loop-me
297kmattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.
No security findings - A
migrate-to-shoehorn
297kmattpocock/skills
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.
1 low - A
pr
297kmattpocock/skills
Use when writing a PR body.
No security findings - A
prototype
297kmattpocock/skills
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.
No security findings - A
research
297kmattpocock/skills
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.
No security findings - A
retro
297kmattpocock/skills
Conduct a retrospective on a coding session.
No security findings - A
scaffold-exercises
297kmattpocock/skills
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 up a new course section.
No security findings - A
setup-matt-pocock-skills
297kmattpocock/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.
No security findings - A
setup-pre-commit
297kmattpocock/skills
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-staged, or add commit-time formatting/typechecking/testing.
2 low - A
setup-ts-deep-modules
297kmattpocock/skills
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-invoked.
No security findings - A
tdd
297kmattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
1 low - A
teach
297kmattpocock/skills
Teach the user a new skill or concept, within this workspace.
No security findings - A
to-questionnaire
297kmattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
No security findings - A
to-spec
297kmattpocock/skills
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.
No security findings - A
to-tickets
297kmattpocock/skills
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 file per ticket locally, or native blocking links on a real tracker).
No security findings - A
triage
297kmattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
No security findings - A
wait-what
297kmattpocock/skills
Stop. That last message did not land: re-pitch it.
No security findings - A
wayfinder
297kmattpocock/skills
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 destination is clear.
No security findings - A
wizard
297kmattpocock/skills
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 unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
No security findings - A
writing-beats
297kmattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
No security findings - A
writing-for-agents
297kmattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
No security findings - A
writing-fragments
297kmattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
No security findings - A
writing-shape
297kmattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
No security findings