Agent skill · operations · mattpocock
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.
Why this skill is useful
Adds a structured configuration process for issue tracking and documentation that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 207,363 stars on the source repository.
What this skill does
Setup Matt Pocock's Skills Scaffold the per-repo configuration that the engineering skills assume: Issue tracker: where issues live (GitHub by default; local markdown is also supported out of the box) Triage labels: the strings used for the five canonical triage roles Domain docs: where CONTEXT.md and ADRs live, and the consumer rules for reading them This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. Process 1. Explore Look at the current repo to understand its starting state. Read whatever exists; don't assume: git remote -v and .git/config: is this a GitHub repo? Which one? AGENTS.md and CLAUDE.md at the repo root: does either exist? Is there already an ## Agent skills section in either? CONTEXT.md and CONTEXT-MAP.md at the repo root docs/adr/ and any src//docs/adr/ directories docs/agents/: does this skill's prior output already exist? .scratch/: a sign that a local-markdown issue tracker convention is already in use Is the triage skill installed? (a triage skill folder alongside this one, or triage in your available skills.) This decides whether Section B runs at all. Monorepo signals: a pnpm-workspace.yaml, a workspaces field in package.json, or a populated packages/ with its own src/. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo. 2. Present findings and ask Summarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next. Lead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when triage isn't installed, Section C when there's no monorepo). Section A: Issue tracker. Explainer: The "issue tracker" is where issues live for this repo. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mattpocock/setup-matt-pocock-skills