Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/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.
Passed 13 of 17 test cases with the skill, and 2 of 17 without it.
and 14 more in the full report
14 fixed3 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
What are the exact file paths under docs/agents/ that are written or updated at the conclusion of this setup workflow?
| Checked | Without skill | With skill |
|---|---|---|
| The response lists docs/agents/issue-tracker.md, docs/agents/triage-labels.md, and docs/agents/domain.md as the generated files. | Missed | Passed |
The instructions your model reads when the skill loads.
Scaffold the per-repo configuration that the engineering skills assume:
CONTEXT.md and ADRs live, and the consumer rules for reading themThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
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 rootdocs/adr/ and any src/*/docs/adr/ directoriesdocs/agents/: does this skill's prior output already exist?.scratch/: a sign that a local-markdown issue tracker convention is already in usetriage skill installed? (a triage skill folder alongside this one, or triage in your available skills.) This decides whether Section B runs at all.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.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, andto-specread from and write to it. They need to know whether to callgh 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:
gh CLI)glab CLI).scratch/<feature>/ in this repo (good for solo projects or repos without a remote)test cases passed, vs 2 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.