[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P775BJ7SFJEP56HZFTTK2G":3,"skill-same:01M6P775BJ7SFJEP56HZFTTK2G":90},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":63},"01M6P775BJ7SFJEP56HZFTTK2G","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.","asushiroo\u002Fdotfiles","asushiroo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113016352?v=4","01M6P6Z9RW9SDSR9XHPMBAYVE6","asushiro","01M6P6Z9WSWDRXZNZCSB4W5JC2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"setup","matt pocock","setup matt pocock skills","repo","for","true","layout","domain","tracker","issue","up","use","engineering skills","configure","first","doc","SET","engineering","run","triage","2026-11-10 10:12:30",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- 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.\n- Monorepo signals — a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. Present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order — one section, one answer, then the next.\n\nLead 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).\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, `to-spec`, 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\nRecord the choice in `docs\u002Fagents\u002Fissue-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.\n\n**Section B — Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you) — an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe 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.\n\n**Section C — Domain docs.** Default to **single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. This fits almost every repo; write it without asking.\n\nOffer **multi-context** — a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files — only when exploration found monorepo signals. Then confirm which layout they want.\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\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\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\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\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- [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 (only if `triage` is installed)\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- 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.\n- Monorepo signals — a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. Present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order — one section, one answer, then the next.\n\nLead 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).\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, `to-spec`, 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\nRecord the choice in `docs\u002Fagents\u002Fissue-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.\n\n**Section B — Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you) — an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe 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.\n\n**Section C — Domain docs.** Default to **single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. This fits almost every repo; write it without asking.\n\nOffer **multi-context** — a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files — only when exploration found monorepo signals. Then confirm which layout they want.\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\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\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\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\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- [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 (only if `triage` is installed)\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":44},true,"main","820a8ecb416e59312ffc2b60c29b66eaf5aa27a4",".codex\u002Fskills\u002Fsetup-matt-pocock-skills","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fasushiroo","2026-10-02 15:40:43",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":44},[53,56,59],{"tool":54,"command":55},"npx","npx skills add asushiroo\u002Fdotfiles --skill setup-matt-pocock-skills",{"tool":57,"command":58},"bunx","bunx skills add asushiroo\u002Fdotfiles --skill setup-matt-pocock-skills",{"tool":60,"command":61},"pnpm","pnpm dlx skills add asushiroo\u002Fdotfiles --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[64,70,74,78,82,86],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"domain.md",2045,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"issue-tracker-github.md",3745,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"issue-tracker-gitlab.md",3826,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"issue-tracker-local.md",1846,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[91,114,129,142,156,180],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":107,"publishedAt":39},"01M6P7AB02738RGKB9RM8QHCA5","writing-shape","Writing, exploit — shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[97,102],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[108,109,110,111,112,113,24],"shape","writing shape","writing","exploit","article","material",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":122,"publishedAt":39},"01M6P7A81YB2M6P1V7C0BC5YP9","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[120,121],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[110,123,124,125,126,127,128,24,23],"writing great skills","editing","reference","vocabulary","make","principles",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":137,"publishedAt":39},"01M6P7A57S23PPT7MY9E9E08AB","writing-fragments","Writing, explore — mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[135,136],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[138,110,139,140,141,24],"writing fragments","mine","explore","structure",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":39},"01M6P7A2S5VH0PPWAJTBBH6987","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\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[148,149],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},[110,151,111,24,152,153,113,154,155],"writing beats","grounding","it","journey","assemble",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M6P79J16SAK6T4CF0RDN62W6","wizard","Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.","https:\u002F\u002Fgithub.com\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwizard\u002FSKILL.md",[],[158,163,164,165,166,167,168,169,170,171,172,173,174,175,24,176,177,178,179,110],"transition","party","values","manual","github actions","env","third-party","human","files","migration","interactive","Bash","secrets","actions","state","generate","github",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":39},"01M6P79EMS5ZYR75Z3WJBZGG9P","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\u002Fasushiroo\u002Fdotfiles\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[182,27,187,188,189,190,191,192,193,194,24,28,195,196,197,198,199,200,201,202],"more","issue tracker","tickets","clear","as","shared","time","map","session","one at a time","work","decision","plan","chunk","at","can"]