[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72THD8EW8AHCDB0KATZ9Y35":3,"skill-same:01M72THD8EW8AHCDB0KATZ9Y35":68},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M72THD8EW8AHCDB0KATZ9Y35","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.","Mekann2904\u002Fmekann","Mekann2904","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F149444390?v=4","01M72TBR4X3TE5S6305ZXYHZYH","Mekann","01M72TBR5E4BWYB1VBWHTHEG5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-10 22:39:42",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` at the repo root — does it exist, and is there already an `## Agent skills` section?\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`, and `to-prd` 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\nIf — and only if — the user picked **GitHub** or **GitLab**, ask one follow-up:\n\n> Explainer: Open-source repos often receive feature requests as pull requests, not just issues — a PR is an issue with attached code. If you turn this on, `triage` pulls *external* PRs into the same queue and runs them through the same labels and states as issues (collaborators' in-flight PRs are left alone). Leave it off if PRs aren't a request surface for you.\n\n- **PRs as a request surface** — yes \u002F no (default: no). Record the answer in `docs\u002Fagents\u002Fissue-tracker.md`. For local-markdown and other trackers, skip this question — there are no PRs.\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`, `diagnose`, `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 `AGENTS.md`\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**Edit Pi's repository instruction file:**\n\n- If `AGENTS.md` exists, edit it.\n- If it does not exist, ask before creating it.\n\nDo not create or edit harness-specific instruction files used by other coding agents.\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, plus whether external PRs are a triage surface]. 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` at the repo root — does it exist, and is there already an `## Agent skills` section?\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`, and `to-prd` 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\nIf — and only if — the user picked **GitHub** or **GitLab**, ask one follow-up:\n\n> Explainer: Open-source repos often receive feature requests as pull requests, not just issues — a PR is an issue with attached code. If you turn this on, `triage` pulls *external* PRs into the same queue and runs them through the same labels and states as issues (collaborators' in-flight PRs are left alone). Leave it off if PRs aren't a request surface for you.\n\n- **PRs as a request surface** — yes \u002F no (default: no). Record the answer in `docs\u002Fagents\u002Fissue-tracker.md`. For local-markdown and other trackers, skip this question — there are no PRs.\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`, `diagnose`, `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 `AGENTS.md`\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**Edit Pi's repository instruction file:**\n\n- If `AGENTS.md` exists, edit it.\n- If it does not exist, ask before creating it.\n\nDo not create or edit harness-specific instruction files used by other coding agents.\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, plus whether external PRs are a triage surface]. 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","ffd7ea99bf2436d312931261a5616ba93f865f62","mekann\u002Fskills\u002Fsetup-matt-pocock-skills","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann","https:\u002F\u002Fgithub.com\u002FMekann2904","https:\u002F\u002Fblog.mekann.workers.dev","琉大 y23 ","2026-08-07 01:44:53",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Mekann2904\u002Fmekann --skill setup-matt-pocock-skills",{"tool":39,"command":40},"bunx","bunx skills add Mekann2904\u002Fmekann --skill setup-matt-pocock-skills",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Mekann2904\u002Fmekann --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"domain.md","REFERENCE","参考文档",2041,"https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"issue-tracker-github.md",3744,"https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"issue-tracker-gitlab.md",3825,"https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"issue-tracker-local.md",1748,"https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M72THYFJF13P93N2F0SCN7BF","writing-assistant","Create, edit, and improve articles and technical documents by planning structure, clarifying dependencies, preserving technical accuracy, and tightening prose. Use when the user wants to draft, revise, or improve an article, guide, reference, design document, proposal, or other technical writing.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fwriting-assistant\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M72THVWJNXRBYKRV9KERZETA","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72THSWAY2FKT4B2CMPATPPA","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\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fto-prd\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M72THQ5B1G8M2SNFJ1XEZ82N","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\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M72THMPT2V3TK4FS4512Z7TE","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M72THJ3JCC5F3H02C80WQM9F","teach","Teach the user a new skill or concept through a persistent, source-grounded learning workspace. Use when the user wants multi-session teaching, lessons, exercises, or a structured learning path.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]