[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P3DF5163WXZ249B30XPFF":3,"skill-same:01M71P3DF5163WXZ249B30XPFF":93},{"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":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":66},"01M71P3DF5163WXZ249B30XPFF","setup-sh4dow-skills",null,"Set up a repository for the engineering skills: its issue tracker, domain docs and base glossary, and coding standards with guardrail commands. Run once per repository, and again when any of them changes.","drsh4dow\u002Fpi-setup","drsh4dow","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F45247070?v=4","01M71P068NASGHSWS11VWW416N","Daniel Moretti","01M71P0698BH81N65NP04X9NVN",10,"MIT","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"setup","setup sh4dow skills","issue","base","commands","engineering skills","repository","run","tracker","changes","with","when","glossary","true","up","for","domain","guardrail","SET","standards","2026-11-10 10:56:23",false,"---\nname: setup-sh4dow-skills\ndescription: \"Set up a repository for the engineering skills: its issue tracker, domain docs and base glossary, and coding standards with guardrail commands. Run once per repository, and again when any of them changes.\"\ndisable-model-invocation: true\nuser-invokable: true\n---\n\n# Setup sh4dow skills\n\nWrite the per-repository **config record** the engineering skills read instead of guessing:\n\n| File | Records | Read by |\n| --- | --- | --- |\n| `docs\u002Fagents\u002Fissue-tracker.md` | Where issues live and how to create, read, search, edit, comment on, nest, block, and close them | **to-spec**, **to-tickets**, **triage**, **code-review**, **writing-good-tickets**, **reflect** |\n| `docs\u002Fagents\u002Fdomain.md` | The glossary and ADR layout, and how to use them | **domain-modeling**, **grill-with-docs**, **improve-codebase-architecture**, **to-spec**, **to-tickets** |\n| `docs\u002Fagents\u002Fstandards.md` | Where the coding standards live, and the guardrail commands that check the code | **code-review**, **reflect** |\n| `GLOSSARY.md` | The project's core domain terms | every skill that names a domain concept |\n\nThe record is committed, so every agent and collaborator in the repository reads the same facts. An `## Agent skills` block in the repository's agent file points at it.\n\nThe run is idempotent. A second run on an unchanged repository asks nothing and writes nothing.\n\n## 1. Explore\n\nFinding facts is your job. Read what exists and assume nothing:\n\n- **Prior record.** `docs\u002Fagents\u002F*.md` and the `## Agent skills` block. When they exist, this is a rerun: compare each recorded fact to what you find now.\n- **Agent file.** `CLAUDE.md` and `AGENTS.md` at the repository root.\n- **Tracker.** `git remote -v`. Whether `gh auth status` or `glab auth status` succeeds. Which MCP servers declared to you reach a tracker, such as Linear, Jira, or Notion. Any tracker the README or agent file names.\n- **Domain docs.** `GLOSSARY.md`, `GLOSSARY-MAP.md`, `docs\u002Fadr\u002F`, and `*\u002Fdocs\u002Fadr\u002F`. Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field, `go.work`, a Cargo workspace, or several `packages\u002F*` with their own sources.\n- **Standards.** `CODING_STANDARDS.md`, `CONTRIBUTING.md`, style guides, `.editorconfig`, and linter and formatter configs.\n- **Guardrails.** The format, lint, typecheck, and test commands, from `package.json` scripts, `Makefile`, `justfile`, `Taskfile.yml`, `pyproject.toml`, `Cargo.toml`, or `go.mod`. The CI workflows that run them. Pre-commit hooks (`.husky\u002F`, `.pre-commit-config.yaml`, `lefthook.yml`).\n- **Code.** Whether the repository has source code yet. Without it, the repository is greenfield.\n\nRun each lint and typecheck command once. A command that fails, or a repository whose CI and hooks run no guardrail at all, is a finding to report in section C.\n\nExploration is done when every bullet above has an answer, \"none\" included.\n\n## 2. Ask, one section at a time\n\nSummarize what you found, then take the sections in order, per the **grilling** skill: one section, one answer, then the next. Lead with the recommended answer, worded so \"yes\" accepts it. Skip a section when exploration settled it, or when the prior record still matches what you found, and say it is unchanged.\n\n**A. Issue tracker.** Recommend the tracker the remote, the README, or the agent file names, else one an MCP server declared to you reaches. A CLI that is not authenticated, or a project you cannot reach, does not change the recommendation: record that tracker and report the access failure as a finding. Recommend local Markdown only when nothing names a tracker.\n\n- **GitHub**, through `gh`. Template: [issue-tracker-github.md](issue-tracker-github.md).\n- **GitLab**, through `glab`. Template: [issue-tracker-gitlab.md](issue-tracker-gitlab.md).\n- **Local Markdown** in the state folder, for a repository with no tracker. Template: [issue-tracker-local.md](issue-tracker-local.md).\n- **Other**, such as Linear, Jira, or Notion. Template: [issue-tracker-other.md](issue-tracker-other.md). Fill each operation with the exact MCP tool or CLI command that performs it, found by listing the server's tools, and ask the user only for what the tools cannot tell you, such as the team or project to file into.\n\n**B. Domain docs and base glossary.** Write the single-context layout without asking, unless exploration found monorepo signals. Then offer multi-context.\n\nFor the base glossary, a brownfield repository seeds it from the code. Run a subagent per the **subagents** skill to propose five to fifteen candidate terms, each with the code that uses it. A greenfield repository seeds it from the user: ask for the core nouns of the domain, or skip the glossary until the first term is settled. Resolve each term with the user per the **domain-modeling** skill and write it in that skill's glossary format. Leave `docs\u002Fadr\u002F` until the first decision needs recording. Template: [domain.md](domain.md).\n\n**C. Standards and guardrails.** Show the standards sources and guardrail commands you found, each with where you found it, and every failing or missing guardrail. Offer to record them as found. Adding a missing guardrail is separate work: record it as a finding in the file rather than building it here. Template: [standards.md](standards.md).\n\n## 3. Confirm\n\nPick the agent file first: `CLAUDE.md` when it exists, else `AGENTS.md`. When neither exists, ask which to create. Never create one beside the other. When the agent file already has a section that records the tracker or the standards in its own words, the drafts fold its facts into the record and replace the section with the block, so each fact lives in one place.\n\nShow the user a draft of every file you will write or change, and of the `## Agent skills` block. Let them edit before anything is written.\n\n## 4. Write\n\nThe record has no triage labels, and setup creates no labels in the tracker.\n\nWrite the `## Agent skills` block into the agent file, or update it in place when it exists, leaving the rest of the file untouched:\n\n```markdown\n## Agent skills\n\nThe engineering skills read this repository's config record in `docs\u002Fagents\u002F`.\nRerun the **setup-sh4dow-skills** skill when the tracker, the domain layout, or the\nguardrails change.\n\n- Issue tracker: [one-line summary]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n- Domain docs: [single-context or multi-context]. See `docs\u002Fagents\u002Fdomain.md`.\n- Standards: [one-line summary]. See `docs\u002Fagents\u002Fstandards.md`.\n```\n\nWrite each `docs\u002Fagents\u002F` file from its template, and write `GLOSSARY.md` when terms were settled.\n\nCommit only the files this run wrote, in one commit, per the **writing-good-commits** skill.\n\n## 5. Report\n\nList each file written or left unchanged, and every finding from section C. Name the skills that now read the record.\n","# Setup sh4dow skills\n\nWrite the per-repository **config record** the engineering skills read instead of guessing:\n\n| File | Records | Read by |\n| --- | --- | --- |\n| `docs\u002Fagents\u002Fissue-tracker.md` | Where issues live and how to create, read, search, edit, comment on, nest, block, and close them | **to-spec**, **to-tickets**, **triage**, **code-review**, **writing-good-tickets**, **reflect** |\n| `docs\u002Fagents\u002Fdomain.md` | The glossary and ADR layout, and how to use them | **domain-modeling**, **grill-with-docs**, **improve-codebase-architecture**, **to-spec**, **to-tickets** |\n| `docs\u002Fagents\u002Fstandards.md` | Where the coding standards live, and the guardrail commands that check the code | **code-review**, **reflect** |\n| `GLOSSARY.md` | The project's core domain terms | every skill that names a domain concept |\n\nThe record is committed, so every agent and collaborator in the repository reads the same facts. An `## Agent skills` block in the repository's agent file points at it.\n\nThe run is idempotent. A second run on an unchanged repository asks nothing and writes nothing.\n\n## 1. Explore\n\nFinding facts is your job. Read what exists and assume nothing:\n\n- **Prior record.** `docs\u002Fagents\u002F*.md` and the `## Agent skills` block. When they exist, this is a rerun: compare each recorded fact to what you find now.\n- **Agent file.** `CLAUDE.md` and `AGENTS.md` at the repository root.\n- **Tracker.** `git remote -v`. Whether `gh auth status` or `glab auth status` succeeds. Which MCP servers declared to you reach a tracker, such as Linear, Jira, or Notion. Any tracker the README or agent file names.\n- **Domain docs.** `GLOSSARY.md`, `GLOSSARY-MAP.md`, `docs\u002Fadr\u002F`, and `*\u002Fdocs\u002Fadr\u002F`. Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field, `go.work`, a Cargo workspace, or several `packages\u002F*` with their own sources.\n- **Standards.** `CODING_STANDARDS.md`, `CONTRIBUTING.md`, style guides, `.editorconfig`, and linter and formatter configs.\n- **Guardrails.** The format, lint, typecheck, and test commands, from `package.json` scripts, `Makefile`, `justfile`, `Taskfile.yml`, `pyproject.toml`, `Cargo.toml`, or `go.mod`. The CI workflows that run them. Pre-commit hooks (`.husky\u002F`, `.pre-commit-config.yaml`, `lefthook.yml`).\n- **Code.** Whether the repository has source code yet. Without it, the repository is greenfield.\n\nRun each lint and typecheck command once. A command that fails, or a repository whose CI and hooks run no guardrail at all, is a finding to report in section C.\n\nExploration is done when every bullet above has an answer, \"none\" included.\n\n## 2. Ask, one section at a time\n\nSummarize what you found, then take the sections in order, per the **grilling** skill: one section, one answer, then the next. Lead with the recommended answer, worded so \"yes\" accepts it. Skip a section when exploration settled it, or when the prior record still matches what you found, and say it is unchanged.\n\n**A. Issue tracker.** Recommend the tracker the remote, the README, or the agent file names, else one an MCP server declared to you reaches. A CLI that is not authenticated, or a project you cannot reach, does not change the recommendation: record that tracker and report the access failure as a finding. Recommend local Markdown only when nothing names a tracker.\n\n- **GitHub**, through `gh`. Template: [issue-tracker-github.md](issue-tracker-github.md).\n- **GitLab**, through `glab`. Template: [issue-tracker-gitlab.md](issue-tracker-gitlab.md).\n- **Local Markdown** in the state folder, for a repository with no tracker. Template: [issue-tracker-local.md](issue-tracker-local.md).\n- **Other**, such as Linear, Jira, or Notion. Template: [issue-tracker-other.md](issue-tracker-other.md). Fill each operation with the exact MCP tool or CLI command that performs it, found by listing the server's tools, and ask the user only for what the tools cannot tell you, such as the team or project to file into.\n\n**B. Domain docs and base glossary.** Write the single-context layout without asking, unless exploration found monorepo signals. Then offer multi-context.\n\nFor the base glossary, a brownfield repository seeds it from the code. Run a subagent per the **subagents** skill to propose five to fifteen candidate terms, each with the code that uses it. A greenfield repository seeds it from the user: ask for the core nouns of the domain, or skip the glossary until the first term is settled. Resolve each term with the user per the **domain-modeling** skill and write it in that skill's glossary format. Leave `docs\u002Fadr\u002F` until the first decision needs recording. Template: [domain.md](domain.md).\n\n**C. Standards and guardrails.** Show the standards sources and guardrail commands you found, each with where you found it, and every failing or missing guardrail. Offer to record them as found. Adding a missing guardrail is separate work: record it as a finding in the file rather than building it here. Template: [standards.md](standards.md).\n\n## 3. Confirm\n\nPick the agent file first: `CLAUDE.md` when it exists, else `AGENTS.md`. When neither exists, ask which to create. Never create one beside the other. When the agent file already has a section that records the tracker or the standards in its own words, the drafts fold its facts into the record and replace the section with the block, so each fact lives in one place.\n\nShow the user a draft of every file you will write or change, and of the `## Agent skills` block. Let them edit before anything is written.\n\n## 4. Write\n\nThe record has no triage labels, and setup creates no labels in the tracker.\n\nWrite the `## Agent skills` block into the agent file, or update it in place when it exists, leaving the rest of the file untouched:\n\n```markdown\n## Agent skills\n\nThe engineering skills read this repository's config record in `docs\u002Fagents\u002F`.\nRerun the **setup-sh4dow-skills** skill when the tracker, the domain layout, or the\nguardrails change.\n\n- Issue tracker: [one-line summary]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n- Domain docs: [single-context or multi-context]. See `docs\u002Fagents\u002Fdomain.md`.\n- Standards: [one-line summary]. See `docs\u002Fagents\u002Fstandards.md`.\n```\n\nWrite each `docs\u002Fagents\u002F` file from its template, and write `GLOSSARY.md` when terms were settled.\n\nCommit only the files this run wrote, in one commit, per the **writing-good-commits** skill.\n\n## 5. Report\n\nList each file written or left unchanged, and every finding from section C. Name the skills that now read the record.\n",{"name":5,"description":7,"user-invokable":44,"disable-model-invocation":44},true,"main","f7936596c1ba2e1472dadccc3f111b9d517fa96c","agent\u002Fskills\u002Fsetup-sh4dow-skills",2,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup","https:\u002F\u002Fgithub.com\u002Fdrsh4dow","https:\u002F\u002Fdanielmoretti.com\u002F","Toss A Coin To Your Witcher :pirate_flag: ","2026-11-03 22:13:53",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":44},[56,59,62],{"tool":57,"command":58},"npx","npx skills add drsh4dow\u002Fpi-setup --skill setup-sh4dow-skills",{"tool":60,"command":61},"bunx","bunx skills add drsh4dow\u002Fpi-setup --skill setup-sh4dow-skills",{"tool":63,"command":64},"pnpm","pnpm dlx skills add drsh4dow\u002Fpi-setup --skill setup-sh4dow-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002FSKILL.md",[67,73,77,81,85,89],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"domain.md","REFERENCE","参考文档",1109,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fdomain.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"issue-tracker-github.md",1526,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fissue-tracker-github.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"issue-tracker-gitlab.md",1498,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fissue-tracker-gitlab.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"issue-tracker-local.md",1431,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fissue-tracker-local.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"issue-tracker-other.md",578,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fissue-tracker-other.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"standards.md",816,"https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fsetup-sh4dow-skills\u002Fstandards.md",[94,114,145,162,183,194],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"01M71P4GPJMBK21BTZBKY9T8EE","changelog","Write the changelog entry for a pull request. Use when a PR changes behavior that users, operators, or integrators can notice.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fevals\u002Fharness-lessons\u002Ffixtures\u002Fchangelog-skill\u002FSKILL.md",[],[96,101,102,103,28,104,105,106,34,107,108,109,110,111,30,112,113],"users","pull","notice","operators","pr","pull request","request","behavior","entry","write","use","can","changelog entry",{"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":130,"publishedAt":39},"01M71P4E9AZM56JBY227P2G1SC","writing-good-tickets","Write, file, or update an issue or ticket that an agent or a developer can take to one PR. Use when filing a bug or feature, updating an issue, or breaking a plan into tickets.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-good-tickets\u002FSKILL.md",[120,125],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[131,132,133,134,105,135,136,137,111,138,30,139,140,112,141,142,110,143,144,21],"good","writing","tickets","writing good tickets","feature","filing","ticket","false","file","one","plan","update","bug","take",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":153,"publishedAt":39},"01M71P4C0B0DXTRRSG9RA6Y687","writing-good-prs","Write or update a pull request title and body that a reviewer can trust and own. Use when opening a PR or editing its description.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-good-prs\u002FSKILL.md",[151,152],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[131,154,132,155,102,156,105,157,111,138,30,112,158,159,106,107,142,110,160,161],"prs","writing good prs","trust","editing","reviewer","title","opening a pr","body",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":170,"publishedAt":39},"01M71P49D1AG2MR6AYNPMMT34Z","writing-good-commits","Write or reword a git commit message and size the commit it describes. Use when committing, or when reshaping commits during a rebase.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-good-commits\u002FSKILL.md",[168,169],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[171,131,132,172,173,174,110,175,176,177,111,138,178,179,30,180,181,182],"commits","writing good commits","message","size","git commit message","git","git commit","rebase","commit message","committing","commit","it",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":39},"01M71P480BDE55JMPVVEBCFS7P","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[189,190],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[192,34,132,157,111,138,193,30],"writing for agents","documents",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":39},"01M71P45SNCD7DDSA6FRVCPA17","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fdrsh4dow\u002Fpi-setup\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwizard\u002FSKILL.md",[],[196,201,202,34,33,203,204,205,111,206,138,30,207,140,208,112,209,210,211,212],"running","setting","ci","provisioning infrastructure","only","invoke","Bash","interactive","credentials","dashboard","generate","human"]