[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAV28F6VZ5VC8WB3Q5Q0DM":3,"skill-same:01M7FAV28F6VZ5VC8WB3Q5Q0DM":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7FAV28F6VZ5VC8WB3Q5Q0DM","mpc_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.","boarlabsxyz\u002Fskills","boarlabsxyz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F183485413?v=4","01M7FAAY4JD8XATY5VPC07M8PA","01M7FAAY574ZFBK3KWT1V57ETE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_setup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: mpc_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.\"\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 (the repository's GitHub Issues)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `GLOSSARY.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, decide by the presets in step 2, write, then report what you wrote. It asks the user nothing.\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, and is either a symlink (`ls -l`)? Is there already an `## Agent skills` section in either?\n- `GLOSSARY.md` and `GLOSSARY-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- Is the `mpc_triage` skill installed? (a `mpc_triage` skill folder alongside this one, or `mpc_triage` in your available skills.) This decides whether labels are written at all.\n- `gh label list`: the labels the tracker already has.\n\n### 2. Decide\n\nEvery choice is preset for this plugin; ask the user none of them.\n\n- **Issue tracker**: the GitHub Issues of the repository's `origin`, through the `gh` CLI. `boar_review` and `boar_codex` read tickets with `gh`, so no other tracker is offered. The \"PRs as a request surface\" flag in the template stays **off**.\n- **Triage labels**: the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. Only where `gh label list` shows an existing label that plainly plays one of these roles under another name (e.g. `bug:triage` for `needs-triage`) use that label instead, so `mpc_triage` applies it rather than creating a duplicate. Skip labels altogether when `mpc_triage` isn't installed.\n- **Domain docs**: **single-context** (one `GLOSSARY.md` + `docs\u002Fadr\u002F` at the repo root). Use multi-context (a root `GLOSSARY-MAP.md` pointing to per-context `GLOSSARY.md` files) only when the repo already has a `GLOSSARY-MAP.md`.\n- **Agent file**: `CLAUDE.md` holds the `## Agent skills` block, and `AGENTS.md` is a symlink to it, so Claude, Codex and any other agent read one text.\n\n### 3. Write\n\n**The agent file.** Make `CLAUDE.md` a regular file and `AGENTS.md` a symlink to it, by the starting state:\n\n- Neither exists: create `CLAUDE.md` with the block, then `ln -s CLAUDE.md AGENTS.md`.\n- Only `CLAUDE.md` exists: edit it, then `ln -s CLAUDE.md AGENTS.md`.\n- Only `AGENTS.md` exists, as a regular file: rename it (`git mv AGENTS.md CLAUDE.md` when it is tracked, else `mv`), edit it, then `ln -s CLAUDE.md AGENTS.md`.\n- `AGENTS.md` is already a symlink to `CLAUDE.md`: edit `CLAUDE.md`.\n- Both are regular files with the same content: replace `AGENTS.md` with the symlink and edit `CLAUDE.md`.\n- Both are regular files that differ: edit `CLAUDE.md` and leave `AGENTS.md` untouched; in the report, say that `AGENTS.md` is a separate file that Codex reads instead of `CLAUDE.md`, and that merging it into `CLAUDE.md` and replacing it with the symlink would give every agent one text.\n- `CLAUDE.md` is a symlink to `AGENTS.md`: the two are already one file; edit it through `CLAUDE.md` and leave the link as it is.\n\nIf an `## Agent skills` block already exists in the 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\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `mpc_triage` is installed. When it isn't, both are omitted.\n\nWhen labels are written, create each one the tracker lacks (`gh label create`).\n\nThen write the 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- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `mpc_triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\n### 4. Done\n\nTell the user the setup is complete: what was written (the agent file and its symlink, `docs\u002Fagents\u002F*.md`, the labels created), and which skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary to 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 (the repository's GitHub Issues)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `GLOSSARY.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, decide by the presets in step 2, write, then report what you wrote. It asks the user nothing.\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, and is either a symlink (`ls -l`)? Is there already an `## Agent skills` section in either?\n- `GLOSSARY.md` and `GLOSSARY-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- Is the `mpc_triage` skill installed? (a `mpc_triage` skill folder alongside this one, or `mpc_triage` in your available skills.) This decides whether labels are written at all.\n- `gh label list`: the labels the tracker already has.\n\n### 2. Decide\n\nEvery choice is preset for this plugin; ask the user none of them.\n\n- **Issue tracker**: the GitHub Issues of the repository's `origin`, through the `gh` CLI. `boar_review` and `boar_codex` read tickets with `gh`, so no other tracker is offered. The \"PRs as a request surface\" flag in the template stays **off**.\n- **Triage labels**: the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. Only where `gh label list` shows an existing label that plainly plays one of these roles under another name (e.g. `bug:triage` for `needs-triage`) use that label instead, so `mpc_triage` applies it rather than creating a duplicate. Skip labels altogether when `mpc_triage` isn't installed.\n- **Domain docs**: **single-context** (one `GLOSSARY.md` + `docs\u002Fadr\u002F` at the repo root). Use multi-context (a root `GLOSSARY-MAP.md` pointing to per-context `GLOSSARY.md` files) only when the repo already has a `GLOSSARY-MAP.md`.\n- **Agent file**: `CLAUDE.md` holds the `## Agent skills` block, and `AGENTS.md` is a symlink to it, so Claude, Codex and any other agent read one text.\n\n### 3. Write\n\n**The agent file.** Make `CLAUDE.md` a regular file and `AGENTS.md` a symlink to it, by the starting state:\n\n- Neither exists: create `CLAUDE.md` with the block, then `ln -s CLAUDE.md AGENTS.md`.\n- Only `CLAUDE.md` exists: edit it, then `ln -s CLAUDE.md AGENTS.md`.\n- Only `AGENTS.md` exists, as a regular file: rename it (`git mv AGENTS.md CLAUDE.md` when it is tracked, else `mv`), edit it, then `ln -s CLAUDE.md AGENTS.md`.\n- `AGENTS.md` is already a symlink to `CLAUDE.md`: edit `CLAUDE.md`.\n- Both are regular files with the same content: replace `AGENTS.md` with the symlink and edit `CLAUDE.md`.\n- Both are regular files that differ: edit `CLAUDE.md` and leave `AGENTS.md` untouched; in the report, say that `AGENTS.md` is a separate file that Codex reads instead of `CLAUDE.md`, and that merging it into `CLAUDE.md` and replacing it with the symlink would give every agent one text.\n- `CLAUDE.md` is a symlink to `AGENTS.md`: the two are already one file; edit it through `CLAUDE.md` and leave the link as it is.\n\nIf an `## Agent skills` block already exists in the 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\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `mpc_triage` is installed. When it isn't, both are omitted.\n\nWhen labels are written, create each one the tracker lacks (`gh label create`).\n\nThen write the 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- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `mpc_triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\n### 4. Done\n\nTell the user the setup is complete: what was written (the agent file and its symlink, `docs\u002Fagents\u002F*.md`, the labels created), and which skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary to restart from scratch.\n",{"name":5,"description":7},"main","70822f79cdb0fbf902c74433bbb4a7bc4ac033cc","skills\u002Fmpc_setup-matt-pocock-skills","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz","2026-10-21 20:41:04",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add boarlabsxyz\u002Fskills --skill mpc_setup-matt-pocock-skills",{"tool":35,"command":36},"bunx","bunx skills add boarlabsxyz\u002Fskills --skill mpc_setup-matt-pocock-skills",{"tool":38,"command":39},"pnpm","pnpm dlx skills add boarlabsxyz\u002Fskills --skill mpc_setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_setup-matt-pocock-skills\u002FSKILL.md",true,[43,49,53],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"domain.md","REFERENCE","参考文档",2044,"https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_setup-matt-pocock-skills\u002Fdomain.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"issue-tracker-github.md",4143,"https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_setup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"triage-labels.md",1057,"https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_setup-matt-pocock-skills\u002Ftriage-labels.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7FAW878DNGW855BTMPHJGGT","mpc_writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-shape\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7FAW53VT22GATJ9VNEQ21HY","mpc_writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-fragments\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7FAW2E42FBEKVX4RH82RZ55","mpc_writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-for-agents\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7FAVZ8S0KT45XMZPWMA2KCS","mpc_writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_writing-beats\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7FAVV4EQBCDJA10KAHRKFSQ","mpc_wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_wayfinder\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M7FAVR30JXV3830GWCJSVJZP","mpc_wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fboarlabsxyz\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmpc_wait-what\u002FSKILL.md",[],[]]