[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75VVB3M4KKS5JNZ3PBY3TCF":3,"skill-same:01M75VVB3M4KKS5JNZ3PBY3TCF":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M75VVB3M4KKS5JNZ3PBY3TCF","setup-matt-pocock-skills",null,"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.","gahjelle\u002Fkoalaty","gahjelle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F728076?v=4","01M75VTC8W2B5QA7KB4B9V1ZZP","Geir Arne Hjelle","01M75VTCB045WMQ7QCX6ESDRC3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: setup-matt-pocock-skills\ndescription: 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.\ndisable-model-invocation: true\n---\n\n# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels** — the strings used for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root — does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F` — does this skill's prior output already exist?\n- `.scratch\u002F` — sign that a local-markdown issue tracker convention is already in use\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's answer, then move to the next. Don't dump all three at once.\n\nAssume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-issues`, `triage`, `to-prd`, and `qa` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault 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:\n\n- **GitHub** — issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab** — issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\n**Section B — Triage label vocabulary.**\n\n> Explainer: When the `triage` skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings *you've actually configured*. If your repo already uses different label names (e.g. `bug:triage` instead of `needs-triage`), map them here so the skill applies the right ones instead of creating duplicates.\n\nThe five canonical roles:\n\n- `needs-triage` — maintainer needs to evaluate\n- `needs-info` — waiting on reporter\n- `ready-for-agent` — fully specified, AFK-ready (an agent can pick it up with no human context)\n- `ready-for-human` — needs human implementation\n- `wontfix` — will not be actioned\n\nDefault: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.\n\n**Section C — Domain docs.**\n\n> Explainer: Some skills (`improve-codebase-architecture`, `diagnosing-bugs`, `tdd`) read a `CONTEXT.md` file to learn the project's domain language, and `docs\u002Fadr\u002F` for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend\u002Fbackend contexts) so they look in the right place.\n\nConfirm the layout:\n\n- **Single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. Most repos are this.\n- **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Ftriage-labels.md`, `docs\u002Fagents\u002Fdomain.md`\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one that's already there.\n\nIf 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.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nThen write the three docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n","# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels** — the strings used for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root — does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F` — does this skill's prior output already exist?\n- `.scratch\u002F` — sign that a local-markdown issue tracker convention is already in use\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's answer, then move to the next. Don't dump all three at once.\n\nAssume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-issues`, `triage`, `to-prd`, and `qa` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault 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:\n\n- **GitHub** — issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab** — issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\n**Section B — Triage label vocabulary.**\n\n> Explainer: When the `triage` skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings *you've actually configured*. If your repo already uses different label names (e.g. `bug:triage` instead of `needs-triage`), map them here so the skill applies the right ones instead of creating duplicates.\n\nThe five canonical roles:\n\n- `needs-triage` — maintainer needs to evaluate\n- `needs-info` — waiting on reporter\n- `ready-for-agent` — fully specified, AFK-ready (an agent can pick it up with no human context)\n- `ready-for-human` — needs human implementation\n- `wontfix` — will not be actioned\n\nDefault: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.\n\n**Section C — Domain docs.**\n\n> Explainer: Some skills (`improve-codebase-architecture`, `diagnosing-bugs`, `tdd`) read a `CONTEXT.md` file to learn the project's domain language, and `docs\u002Fadr\u002F` for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend\u002Fbackend contexts) so they look in the right place.\n\nConfirm the layout:\n\n- **Single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. Most repos are this.\n- **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Ftriage-labels.md`, `docs\u002Fagents\u002Fdomain.md`\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one that's already there.\n\nIf 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.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nThen write the three docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","2ce876312b6a0f10550c2aedce874ca56f7d3df6",".agents\u002Fskills\u002Fsetup-matt-pocock-skills",0,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty","https:\u002F\u002Fgithub.com\u002Fgahjelle","2026-06-27 08:32:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add gahjelle\u002Fkoalaty --skill setup-matt-pocock-skills",{"tool":38,"command":39},"bunx","bunx skills add gahjelle\u002Fkoalaty --skill setup-matt-pocock-skills",{"tool":41,"command":42},"pnpm","pnpm dlx skills add gahjelle\u002Fkoalaty --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"domain.md","REFERENCE","参考文档",2045,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"issue-tracker-github.md",1065,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"issue-tracker-gitlab.md",1465,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"issue-tracker-local.md",838,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75VYPDPMFSN2TFWA2VVH5XH","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75VYKSA7CY2M6XQX31MN25W","triage","Move issues through a state machine of triage roles — categorise, reproduce, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75VYHXPF87ZYWEGR6XZ5YHY","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fto-prd\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M75VYEY7MPKGW7XGMYP60PWS","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M75VYD2ZN01F1CPSWSDAXWN0","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M75VYAHEBQSPVWEGVFZN3A9V","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]