Index of every page on this site: llms.txt
All skills
mattpocock avatar

/setup-matt-pocock-skills

@abeeaf9 official
by Matt Pocockmattpocock/skills329k stars
27,654
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/mattpocock/skills/setup-matt-pocock-skills

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈1.8k when used: this file. ≈3.5k more on demand in 6 files.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

This Skill turns off automatic use in Claude Code. Its description stays out of the automatic Skill list by default.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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 GLOSSARY.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?
  • GLOSSARY.md and GLOSSARY-MAP.md at the repo root, and the legacy CONTEXT.md / CONTEXT-MAP.md. If a legacy file exists, offer to git mv it to its GLOSSARY name and rewrite those names in docs/agents/domain.md.
  • 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. Skills like to-tickets, triage, and to-spec read from and write to it. They need to know whether to call gh issue create, write a markdown file under .scratch/, or follow some other workflow you describe. Pick the place you actually track work for this repo.

Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:

  • GitHub: issues live in the repo's GitHub Issues (uses the gh CLI)
  • GitLab: issues live in the repo's GitLab Issues (uses the glab CLI)
  • Local markdown: issues live as files under .scratch/<feature>/ in this repo (good for solo projects or repos without a remote)
  • Other (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose

Record the choice in docs/agents/issue-tracker.md. The GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted off. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.

A GitHub or GitLab tracker needs a reachable repo. When the user picks one and no git remote points at that host, get the repo URL from them and wire it up (git init if needed, git remote add origin <url>) before going further. Done when gh repo view / glab repo view prints the project from inside this directory; if it can't, stop and tell the user what's missing.

Section B: Triage label vocabulary. Skip this section entirely if the triage skill isn't installed (exploration told you), since an uninstalled skill needs no labels.

If it is installed, ask exactly one question:

Do you want to keep the default triage labels? (recommended: yes)

The defaults are the five canonical roles, each label string equal to its name: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. On yes, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. bug:triage for needs-triage), collect the overrides so triage applies existing labels instead of creating duplicates.

Section C: Domain docs. Default to single-context (one GLOSSARY.md + docs/adr/ at the repo root). This fits almost every repo; write it without asking.

Offer multi-context (a root GLOSSARY-MAP.md pointing to per-context GLOSSARY.md files) only when exploration found monorepo signals. Then confirm which layout they want.

3. Confirm and edit

Show the user a draft of:

  • The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)
  • The contents of docs/agents/issue-tracker.md, docs/agents/domain.md, and docs/agents/triage-labels.md (the last only when triage is installed)

Let them edit before writing.

4. Write

Pick the file to edit:

  • If CLAUDE.md exists, edit it.
  • Else if AGENTS.md exists, edit it.
  • If neither exists, ask the user which one to create; don't pick for them.

Never create AGENTS.md when CLAUDE.md already exists (or vice versa); always edit the one that's already there.

If an ## Agent skills block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.

The block:

## Agent skills

### Issue tracker

[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.

### Triage labels

[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.

### Domain docs

[one-line summary of layout: "single-context" or "multi-context"]. See `docs/agents/domain.md`.

Include the ### Triage labels sub-block, and write docs/agents/triage-labels.md, only when triage is installed and Section B ran. When it isn't, both are omitted.

When Section B ran on GitHub or GitLab, create each configured label the tracker lacks (gh label create / glab label create).

Then write the docs files using the seed templates in this skill folder as a starting point:

For "other" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.

5. Done

Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit docs/agents/*.md directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    This skill is a repository configuration utility that sets up documentation and issue tracker settings. It uses standard developer tools like Git, GitHub CLI (gh), and GitLab CLI (glab) to perform its tasks. No malicious behavior was detected.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at abeeaf9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 4 weeks ago
disable-model-invocation
true
  • Documentation
  • github
  • gitlab
  • configuration
  • agents
  • workflow
  • issue-tracker
  • triage

README badge

README badge for mattpocock/skills/setup-matt-pocock-skills

Sets up per-repo configuration files that the Matt Pocock engineering skills (triage, to-issues, diagnose, tdd, etc.) read to understand your issue tracker location, label vocabulary, and domain documentation layout. Run this once before using those skills, or if they appear to lack context about your repo's workflow and documentation structure.

Generated from the current SKILL.md.

What does this skill do?
This skill scaffolds per-repo configuration files that other Matt Pocock engineering skills (to-issues, triage, diagnose, tdd, etc.) depend on: issue tracker location, triage label vocabulary, and domain docs layout.
When should I run this skill?
Run it once before first use of any dependent skill, or if those skills appear to be missing context about your issue tracker, triage labels, or domain docs. Re-run only if you want to switch issue trackers or restart configuration.
What issue trackers does this support?
GitHub (default), GitLab, local markdown under `.scratch/`, or any other tracker if you describe your workflow in prose.
Do I need to have existing labels in my issue tracker?
No. If your repo has no labels yet, the skill uses sensible defaults (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). If you already use different label names, you can map them so the skill applies the ones you've configured.
Does this work with monorepos?
Yes. The skill supports both single-context repos (one CONTEXT.md at the root) and multi-context layouts (CONTEXT-MAP.md pointing to per-context CONTEXT.md files).

Generated from the current SKILL.md. These answers refresh after source changes.