[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZK2VMXQQYN1JSX6N4NT4B":3,"skill-same:01M6FZK2VMXQQYN1JSX6N4NT4B":69},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6FZK2VMXQQYN1JSX6N4NT4B","desk-flip",null,"Autopsy a stuck project, extract salvageable artifacts, and route to a fresh start via \u002Fbootstrap-repo reset or new-repo bootstrap","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fteardown\u002Fclaude\u002Fdesk-flip\u002Farchive\u002Fv0.5\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"desk flip","v0","via","fresh","reset","project","repo bootstrap","route","alignment","bootstrap","extract","repo","page","execution","autopsy","start","artifacts","2026-11-10 10:12:30",false,"---\nname: desk-flip\ndescription: Autopsy a stuck project, extract salvageable artifacts, and route to a fresh start via \u002Fbootstrap-repo reset or new-repo bootstrap\ntype: execution\nversion: v0.5\nrequired_conventions: [alignment-page]\nargument-hint: \"\u003Cproject-path>\"\n---\n\n# Desk Flip\n\nAutopsy a stuck project, extract salvageable artifacts (lessons, valid specs, non-code assets), and route the user to a fresh start either in a new repo or by resetting the existing repo with `\u002Fbootstrap-repo` (repo-maintenance pack) `--reset-existing`.\n\nAlways desk-flip. If the user invoked it, the decision to restart is already made — do not offer incremental migration or attempt to fix the old project in place.\n\n## Process\n\n1. **Identify the stuck project.**\n   - Accept an optional project path from `$ARGUMENTS`; default to the current working directory.\n   - Verify the target is a git repo with existing code (not an empty repo).\n   - If the project appears to already use the new workflow (file-backed specs, prototype-first artifacts, healthy structure), warn the user and confirm before proceeding.\n\n2. **Survey the project.**\n   - Read `CLAUDE.md`, `README.md`, `package.json` or equivalent manifest, and directory structure.\n   - Read `tasks\u002F`, `specs\u002F`, `docs\u002F` directories if they exist.\n   - Scan recent git history (last ~50 commits) for commit patterns and timeline.\n   - Read any existing `tasks\u002Flessons.md` or post-mortem docs.\n\n3. **Run the autopsy** using subagents in parallel:\n   - **Lessons extraction:** What went wrong? Look for evidence of failure modes — infrastructure before prototype, late testing, chat-driven alignment drift, scope creep, untestable architecture. Cite specific commits, files, or timeline evidence.\n   - **Spec\u002Fdesign extraction:** Identify specs, designs, research docs, interview logs, and product briefs that capture valid domain knowledge or user needs — regardless of whether the implementation matched. Mark each as `valid`, `partially valid`, or `stale` with a one-line rationale.\n   - **Asset inventory:** Find non-code assets worth preserving — icons, images, copy, API contracts, design tokens, brand assets, research documents.\n\n   Do NOT extract code, dependencies, database schemas, or infrastructure config.\n\n4. **Write the autopsy report.**\n   - Produce `desk-flip-report.md` in the project root with these sections:\n\n   ```\n   ## Project Summary\n   What the project was and what state it's in now.\n\n   ## What Went Wrong\n   Specific failure modes with evidence (commits, files, timeline).\n\n   ## Salvageable Specs & Designs\n   List with file paths, validity status, and one-line descriptions.\n\n   ## Salvageable Assets\n   Non-code assets with file paths.\n\n   ## Lessons for the Fresh Start\n   Actionable guidance for the new project to avoid the same mistakes.\n\n   ## Recommended Bootstrap Input\n   A condensed brief suitable as input to \u002Fbootstrap-repo.\n   ```\n\n5. **Choose the fresh-start path.**\n   - If the user explicitly wants a new repository, route to `\u002Fbootstrap-repo` (repo-maintenance pack) `\u003Ccondensed brief>`.\n   - If the user wants to keep the existing repository, or the current repo name, remotes, issues, deployment linkage, or local tooling are valuable, route to `\u002Fbootstrap-repo` (repo-maintenance pack) `--reset-existing \u003Ccondensed brief>`.\n   - For in-place reset, state that `\u002Fbootstrap-repo --reset-existing` (repo-maintenance pack) must archive the old implementation under `archive\u002F` before writing the fresh bootstrap docs. It must not delete the old code outright.\n   - The archive should preserve old implementation and documentation evidence without treating it as reusable foundation code or active source-of-truth docs. The fresh start should continue only from a high-level concept seed derived from the report, plus lessons captured in the report.\n\n6. **Present and route.**\n   - Show the user a terminal summary of the report.\n   - Recommend the appropriate `\u002Fbootstrap-repo` (repo-maintenance pack) command with the recommended bootstrap input from the report.\n   - Do NOT create the new repo or run `\u002Fbootstrap-repo` — the user does this.\n   - After bootstrap, route product\u002Fapp restarts into the research-first alignment workflow using the high-level concept seed as input: `\u002Fcustomer-discovery` to define who this is for, `\u002Fcompetitive-analysis` to map the market, `\u002Fjourney-map` to map lifecycle and task flow, `\u002Fpositioning` to lock the product direction, `\u002Fuser-flow-map` to map screen flow, `\u002Fux-variations [specific-user-flow]` to explore progression branches, `\u002Fui-interview [specific-ux-variation]` to render and approve\u002Freject a branch mockup, then prototype work, `\u002Fuat --variant-evaluation`, and `\u002Fconsolidate-prototypes` before `\u002Fspec-interview` or `\u002Froadmap`. Use `\u002Fui-interview --requirements-only` and `\u002Fux-variations --layout-mode` only when the user explicitly needs a fixed content contract and layout-only alternatives.\n   - If the business-discovery or customer-lifecycle packs are not enabled in the fresh repo, recommend `npx skillpacks install business-discovery` and `npx skillpacks install customer-lifecycle` before the research sequence.\n\n## Output\n\n```markdown\nDesk-flipped: \u003Cproject name>\n- Report: desk-flip-report.md written to \u003Cproject-path>\n- Specs extracted: \u003Ccount> (\u003Cvalid>\u002F\u003Cpartial>\u002F\u003Cstale>)\n- Assets found: \u003Ccount>\n- Lessons captured: \u003Ccount>\n\n**Next work:** Reset the existing repo by archiving old implementation files, or create a new repo if the user prefers a separate fresh start\n**Recommended next command:** \u002Fbootstrap-repo (repo-maintenance pack) --reset-existing \u003Ccondensed brief from report>\n```\n\n## Constraints\n\n- **Read-only during desk-flip** — no modifications to existing files, no archival, no branch creation. The only file written by this skill is `desk-flip-report.md`.\n- Do not carry forward code, dependencies, infrastructure, old research, old specs, or old task docs from the old project as active files.\n- Do not create the new repo or invoke `\u002Fbootstrap-repo` — the user handles that transition.\n- Do not commit or push (the report is informational, not a meaningful mutation to ship).\n- Do not delete, archive, or rename anything in the old repo during desk-flip. Only the downstream `\u002Fbootstrap-repo --reset-existing` step may perform archival after the user chooses that route.\n- If the project has no specs, docs, or meaningful git history, produce the report anyway but note the thin evidence in each section.\n- When recommending a skill from another pack, verify the pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If not installed, prepend `npx skillpacks install \u003Cpack-name>` to the recommendation.\n\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fdesk-flip-{topic}.html`.\n\n## Default Shipping Contract\n\n- Do NOT commit or push. The only side effect is `desk-flip-report.md` written to the project root.\n- **Default next-step routing:** when reporting completion, include the two-line pair `**Next work:** \u003Cspecific task>` and `**Recommended next command:** \u002Fbootstrap-repo (repo-maintenance pack) --reset-existing \u003Cbrief>` for in-place restarts, or `\u002Fbootstrap-repo` (repo-maintenance pack) `\u003Cbrief>` only when a separate new repo is explicitly the right path.\n- **Post-bootstrap route:** include in the report that the fresh project should proceed from the high-level concept seed to `\u002Fcustomer-discovery`, then `\u002Fcompetitive-analysis`, `\u002Fjourney-map`, `\u002Fpositioning`, `\u002Fuser-flow-map`, `\u002Fux-variations [specific-user-flow]`, `\u002Fui-interview [specific-ux-variation]`, and prototype work. Mention `npx skillpacks install business-discovery`, `npx skillpacks install customer-lifecycle`, or `npx skillpacks install product-design` first if those packs are not enabled.\n","# Desk Flip\n\nAutopsy a stuck project, extract salvageable artifacts (lessons, valid specs, non-code assets), and route the user to a fresh start either in a new repo or by resetting the existing repo with `\u002Fbootstrap-repo` (repo-maintenance pack) `--reset-existing`.\n\nAlways desk-flip. If the user invoked it, the decision to restart is already made — do not offer incremental migration or attempt to fix the old project in place.\n\n## Process\n\n1. **Identify the stuck project.**\n   - Accept an optional project path from `$ARGUMENTS`; default to the current working directory.\n   - Verify the target is a git repo with existing code (not an empty repo).\n   - If the project appears to already use the new workflow (file-backed specs, prototype-first artifacts, healthy structure), warn the user and confirm before proceeding.\n\n2. **Survey the project.**\n   - Read `CLAUDE.md`, `README.md`, `package.json` or equivalent manifest, and directory structure.\n   - Read `tasks\u002F`, `specs\u002F`, `docs\u002F` directories if they exist.\n   - Scan recent git history (last ~50 commits) for commit patterns and timeline.\n   - Read any existing `tasks\u002Flessons.md` or post-mortem docs.\n\n3. **Run the autopsy** using subagents in parallel:\n   - **Lessons extraction:** What went wrong? Look for evidence of failure modes — infrastructure before prototype, late testing, chat-driven alignment drift, scope creep, untestable architecture. Cite specific commits, files, or timeline evidence.\n   - **Spec\u002Fdesign extraction:** Identify specs, designs, research docs, interview logs, and product briefs that capture valid domain knowledge or user needs — regardless of whether the implementation matched. Mark each as `valid`, `partially valid`, or `stale` with a one-line rationale.\n   - **Asset inventory:** Find non-code assets worth preserving — icons, images, copy, API contracts, design tokens, brand assets, research documents.\n\n   Do NOT extract code, dependencies, database schemas, or infrastructure config.\n\n4. **Write the autopsy report.**\n   - Produce `desk-flip-report.md` in the project root with these sections:\n\n   ```\n   ## Project Summary\n   What the project was and what state it's in now.\n\n   ## What Went Wrong\n   Specific failure modes with evidence (commits, files, timeline).\n\n   ## Salvageable Specs & Designs\n   List with file paths, validity status, and one-line descriptions.\n\n   ## Salvageable Assets\n   Non-code assets with file paths.\n\n   ## Lessons for the Fresh Start\n   Actionable guidance for the new project to avoid the same mistakes.\n\n   ## Recommended Bootstrap Input\n   A condensed brief suitable as input to \u002Fbootstrap-repo.\n   ```\n\n5. **Choose the fresh-start path.**\n   - If the user explicitly wants a new repository, route to `\u002Fbootstrap-repo` (repo-maintenance pack) `\u003Ccondensed brief>`.\n   - If the user wants to keep the existing repository, or the current repo name, remotes, issues, deployment linkage, or local tooling are valuable, route to `\u002Fbootstrap-repo` (repo-maintenance pack) `--reset-existing \u003Ccondensed brief>`.\n   - For in-place reset, state that `\u002Fbootstrap-repo --reset-existing` (repo-maintenance pack) must archive the old implementation under `archive\u002F` before writing the fresh bootstrap docs. It must not delete the old code outright.\n   - The archive should preserve old implementation and documentation evidence without treating it as reusable foundation code or active source-of-truth docs. The fresh start should continue only from a high-level concept seed derived from the report, plus lessons captured in the report.\n\n6. **Present and route.**\n   - Show the user a terminal summary of the report.\n   - Recommend the appropriate `\u002Fbootstrap-repo` (repo-maintenance pack) command with the recommended bootstrap input from the report.\n   - Do NOT create the new repo or run `\u002Fbootstrap-repo` — the user does this.\n   - After bootstrap, route product\u002Fapp restarts into the research-first alignment workflow using the high-level concept seed as input: `\u002Fcustomer-discovery` to define who this is for, `\u002Fcompetitive-analysis` to map the market, `\u002Fjourney-map` to map lifecycle and task flow, `\u002Fpositioning` to lock the product direction, `\u002Fuser-flow-map` to map screen flow, `\u002Fux-variations [specific-user-flow]` to explore progression branches, `\u002Fui-interview [specific-ux-variation]` to render and approve\u002Freject a branch mockup, then prototype work, `\u002Fuat --variant-evaluation`, and `\u002Fconsolidate-prototypes` before `\u002Fspec-interview` or `\u002Froadmap`. Use `\u002Fui-interview --requirements-only` and `\u002Fux-variations --layout-mode` only when the user explicitly needs a fixed content contract and layout-only alternatives.\n   - If the business-discovery or customer-lifecycle packs are not enabled in the fresh repo, recommend `npx skillpacks install business-discovery` and `npx skillpacks install customer-lifecycle` before the research sequence.\n\n## Output\n\n```markdown\nDesk-flipped: \u003Cproject name>\n- Report: desk-flip-report.md written to \u003Cproject-path>\n- Specs extracted: \u003Ccount> (\u003Cvalid>\u002F\u003Cpartial>\u002F\u003Cstale>)\n- Assets found: \u003Ccount>\n- Lessons captured: \u003Ccount>\n\n**Next work:** Reset the existing repo by archiving old implementation files, or create a new repo if the user prefers a separate fresh start\n**Recommended next command:** \u002Fbootstrap-repo (repo-maintenance pack) --reset-existing \u003Ccondensed brief from report>\n```\n\n## Constraints\n\n- **Read-only during desk-flip** — no modifications to existing files, no archival, no branch creation. The only file written by this skill is `desk-flip-report.md`.\n- Do not carry forward code, dependencies, infrastructure, old research, old specs, or old task docs from the old project as active files.\n- Do not create the new repo or invoke `\u002Fbootstrap-repo` — the user handles that transition.\n- Do not commit or push (the report is informational, not a meaningful mutation to ship).\n- Do not delete, archive, or rename anything in the old repo during desk-flip. Only the downstream `\u002Fbootstrap-repo --reset-existing` step may perform archival after the user chooses that route.\n- If the project has no specs, docs, or meaningful git history, produce the report anyway but note the thin evidence in each section.\n- When recommending a skill from another pack, verify the pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If not installed, prepend `npx skillpacks install \u003Cpack-name>` to the recommendation.\n\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fdesk-flip-{topic}.html`.\n\n## Default Shipping Contract\n\n- Do NOT commit or push. The only side effect is `desk-flip-report.md` written to the project root.\n- **Default next-step routing:** when reporting completion, include the two-line pair `**Next work:** \u003Cspecific task>` and `**Recommended next command:** \u002Fbootstrap-repo (repo-maintenance pack) --reset-existing \u003Cbrief>` for in-place restarts, or `\u002Fbootstrap-repo` (repo-maintenance pack) `\u003Cbrief>` only when a separate new repo is explicitly the right path.\n- **Post-bootstrap route:** include in the report that the fresh project should proceed from the high-level concept seed to `\u002Fcustomer-discovery`, then `\u002Fcompetitive-analysis`, `\u002Fjourney-map`, `\u002Fpositioning`, `\u002Fuser-flow-map`, `\u002Fux-variations [specific-user-flow]`, `\u002Fui-interview [specific-ux-variation]`, and prototype work. Mention `npx skillpacks install business-discovery`, `npx skillpacks install customer-lifecycle`, or `npx skillpacks install product-design` first if those packs are not enabled.\n",{"name":5,"type":32,"version":41,"description":7,"argument-hint":42,"required_conventions":43},"v0.5","\u003Cproject-path>",[44],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fteardown\u002Fclaude\u002Fdesk-flip\u002Farchive\u002Fv0.5",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill desk-flip",{"tool":61,"command":62},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill desk-flip",{"tool":64,"command":65},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill desk-flip","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fteardown\u002Fclaude\u002Fdesk-flip\u002Farchive\u002Fv0.5\u002FSKILL.md",true,[],[70,82,92,104,119,130],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":36},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[77,78,79,80,20,81],"source checkout allowed","checkout","fixture","only","valid",{"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":36},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[89,90,91,81,79,20],"deck install valid","deck","install",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":36},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[99,100,101,81,102,103,79,20],"codex pack guard valid","pack","guard","codex","availability",{"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":115,"publishedAt":36},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[116,117,81,102,20,118,79],"codex missing skill valid","missing","fallback",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":36},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[125],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[81,102,118,127,128,129,20,79],"base skill","codex base skill fallback valid","base",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":36},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[81,101,100,137,103,20,79],"claude pack guard valid"]