Agent skill · Documentation

setup-matt-pocock-skills

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

stevesolungithub.com/stevesolunGitHub ↗
claude-codeMIT
Install
npx skills add stevesolun/ctx --skill setup-matt-pocock-skills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 7 KB
Bundled scripts: none
Path: imported-skills/mattpocock/setup-matt-pocock-skills/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 569
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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/` — sign that a local-markdown issue tracker convention is already in use ### 2. Present findings and ask Summarise what's present and what's missing. Then walk the user through the three decisi

What's inside
Steps it walks through
  1. Process
  2. 1. Explore
  3. 2. Present findings and ask
  4. 3. Confirm and edit
  5. 4. Write
  6. 5. Done
Ships with 5 files
  • domain.md
  • issue-tracker-github.md
  • issue-tracker-gitlab.md
  • issue-tracker-local.md
  • triage-labels.md
More from ctx
All skills →
About this skill
What does the setup-matt-pocock-skills skill do?

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

How do I install it?

Run `npx skills add stevesolun/ctx --skill setup-matt-pocock-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From stevesolun/ctx, a repository with 569 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going