[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZ1J29P01N86RKSFEKG5SC":3,"skill-same:01M6FZ1J29P01N86RKSFEKG5SC":66},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6FZ1J29P01N86RKSFEKG5SC","bootstrap-repo",null,"Initialize or reset a repository README and agent workflow docs from a short project brief","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\u002Frepo-maintenance\u002Fclaude\u002Fbootstrap-repo\u002Farchive\u002Fv0.0\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"bootstrap","repo","bootstrap repo","docs","workflow","repository","brief","execution","short","README","initialize","v0","agent workflow","project","reset","project brief","2026-11-10 10:12:30",false,"---\nname: bootstrap-repo\ndescription: Initialize or reset a repository README and agent workflow docs from a short project brief\ntype: execution\nversion: v0.0\nargument-hint: \"\u003Cproject brief>\"\n---\n\n# Bootstrap Repo\n\nInitialize a repository with a useful `README.md` and the standard agent workflow docs. When invoked with `--reset-existing`, first archive stale implementation and documentation files from a non-empty stuck repo so the fresh start is not built on old code or old assumptions by accident.\n\n## Process\n\n1. **Parse the project brief and mode** from `$ARGUMENTS`:\n   - Detect `--reset-existing`, `--in-place-reset`, or an explicit request to archive\u002Freset the current codebase before bootstrap.\n   - Extract the project name, purpose, setup instructions, run\u002Ftest commands, and any constraints.\n   - If the brief is missing or too thin to write a useful README, ask for the project name and one-sentence purpose. Ask for setup or run instructions only when the repository does not make them discoverable.\n\n2. **Inspect the target repository:**\n   - Read existing `README.md`, `CLAUDE.md`, `AGENTS.md`, package manifests, obvious build files, and directory names.\n   - Preserve discovered commands and facts. Do not invent dependency managers, deployment targets, or product claims.\n\n3. **Reset existing stale repo when explicitly requested:**\n   - Only perform this step when reset mode is explicit. Never archive or move files during ordinary bootstrap.\n   - Confirm the repo is non-empty and contains stale implementation, docs, research, specs, task files, design notes, or generated app structure. If it is already empty or freshly initialized, skip archival and note why.\n   - Create `archive\u002FYYYY-MM-DD-HHMMSS\u002F` and move stale implementation and documentation files\u002Fdirectories there before writing fresh bootstrap docs.\n   - Archive old docs by default, including `docs\u002F`, `alignment\u002F`, `research\u002F`, `specs\u002F`, `tasks\u002F`, planning reports, implementation notes, design docs, old README content, and prior roadmap\u002Ftodo\u002Fhistory files. These may remain useful as historical evidence in the archive, but they must not stay active as source-of-truth inputs.\n   - Do not archive `.git\u002F`, `.agents\u002F`, `archive\u002F`, `desk-flip-report.md`, root agent config files needed for the current session, or the newly written high-level concept artifact.\n   - Preserve exactly one active concept seed, such as `concept.md` or `README.md` `## Concept`, derived from the bootstrap brief or `desk-flip-report.md`. Keep it high level: product name, target user, core problem, value proposition, non-goals, and open questions. Do not preserve old research\u002Fspec detail as active files.\n   - Preserve a manifest at `archive\u002FYYYY-MM-DD-HHMMSS\u002FMANIFEST.md` listing every moved path, every intentionally preserved path, and the high-level concept source that justified the reset.\n   - Prefer `git mv` for tracked paths so history remains understandable. Use ordinary moves only for untracked paths.\n   - Do not delete old files outright. If a path cannot be moved safely, stop and report the blocker instead of partially resetting further.\n   - After archival, the root should contain only the fresh-start sources of truth: git metadata, agent config, the archive directory, `desk-flip-report.md`, the high-level concept artifact, and any newly written bootstrap docs. Old docs\u002Fresearch\u002Fspecs belong in the archive.\n\n4. **Create or update `README.md`:**\n   - If `README.md` is absent, empty, or placeholder-like, write a concise README with:\n     - `# \u003CProject Name>`\n     - A short purpose summary.\n     - `## Getting Started`\n     - `## Development`\n     - `## Notes`\n   - If `README.md` already has substantial content, preserve it. Ask before replacing it; otherwise add a small bootstrap section only when it improves the file.\n   - Use the project brief as the primary source and repository inspection as supporting evidence.\n\n5. **Provision agent workflow docs:**\n   - Run `\u002Fprovision-agentic-config` for the same repository.\n   - Confirm `CLAUDE.md` and `AGENTS.md` exist after provisioning.\n   - Preserve unrelated existing content in both files.\n\n6. **Verify the result:**\n   - Check that `README.md`, `CLAUDE.md`, and `AGENTS.md` exist.\n   - Confirm the corresponding workflow orchestration block appears exactly once in each of `CLAUDE.md` and `AGENTS.md`.\n   - Report whether the monorepo safety block was included or skipped by `\u002Fprovision-agentic-config`.\n   - In reset mode, check that `archive\u002FYYYY-MM-DD-HHMMSS\u002FMANIFEST.md` exists and lists moved and preserved paths, and verify old docs\u002Fresearch\u002Fspecs\u002Ftasks were archived rather than left active.\n\n7. **Route research-first after product bootstrap:**\n   - If this is a product, app, SaaS, dashboard, internal tool, marketplace, website, or other user-facing restart, rebuild market and lifecycle alignment from the high-level concept before UI requirements or prototypes.\n   - Check `.agents\u002Fproject.json.enabled_packs` when present. If `business-discovery` is not enabled, recommend `\u002Fpack install business-discovery` before `\u002Ficp`. If `customer-lifecycle` is not enabled, include `\u002Fpack install customer-lifecycle` before `\u002Fjourney-map`.\n   - When required packs are available, recommend `\u002Ficp \u003Cconcept>` as the next command. After `\u002Ficp`, the intended sequence is `\u002Fcompetitive-analysis` -> `\u002Fjourney-map` -> `\u002Fux-variations` -> `\u002Fui-interview` -> prototype work.\n   - If current, accepted `research\u002Ficp.md`, `research\u002Fcompetitive-analysis.md`, and `research\u002Fjourney-map.md` already exist from the fresh reset, then recommend `\u002Fux-variations \u003Ctopic>`.\n   - If UX variations already exist but interface details are missing, recommend `\u002Fui-interview \u003Ctopic>`.\n   - Only route directly to `\u002Froadmap` or `\u002Fexec` when the project is non-UI\u002Fnon-product work or already has accepted alignment artifacts and a consolidated prototype.\n   - The intended product sequence after reset is: `\u002Ficp` -> `\u002Fcompetitive-analysis` -> `\u002Fjourney-map` -> `\u002Fux-variations` -> `\u002Fui-interview` -> build variants\u002Fprototypes via `\u002Fexec` or the applicable prototype-building route -> `\u002Fuat --variant-evaluation` -> `\u002Fconsolidate-variations` -> `\u002Fresearch-roadmap --post-prototype` -> `\u002Fspec-interview` or `\u002Froadmap`.\n\n## Output\n\n```markdown\nBootstrapped repository\n- README.md: [created | updated | preserved], source: [arguments | prompts | existing content]\n- Reset archive: [created archive\u002FYYYY-MM-DD-HHMMSS | skipped (\u003Creason>)]\n- Active concept seed: [concept.md | README.md ## Concept | other]\n- CLAUDE.md: [created | updated | unchanged], corresponding workflow block appears once\n- AGENTS.md: [created | updated | unchanged], corresponding workflow block appears once\n- Monorepo safety block: [included (\u003Cheuristic>) | skipped]\n- Verification: [commands\u002Fchecks run]\n- Recommended next command: [\u002Fpack install business-discovery | \u002Fpack install customer-lifecycle | \u002Ficp \u003Cconcept> | \u002Fux-variations \u003Ctopic> | \u002Fui-interview \u003Ctopic> | \u002Froadmap | \u002Fexec]\n```\n\n## Constraints\n\n- Do not overwrite substantial existing `README.md` content without explicit user confirmation.\n- Do not invent setup, test, deploy, or architecture details that are not in the brief or repository.\n- Keep the README concise and useful for a new contributor.\n- Do not modify files other than `README.md`, `CLAUDE.md`, and `AGENTS.md` unless the user explicitly asks or invokes reset mode.\n- Reset mode may move stale files, including old docs\u002Fresearch\u002Fspecs\u002Ftasks, into `archive\u002FYYYY-MM-DD-HHMMSS\u002F` and write that archive's `MANIFEST.md`; it may not delete files outright.\n- In reset mode, do not preserve old docs as active files just because they were marked salvageable. Use them only as archived historical evidence; active research and requirements restart from the high-level concept.\n- Do not create, modify, or suggest GitHub Actions workflows.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Bootstrap Repo\n\nInitialize a repository with a useful `README.md` and the standard agent workflow docs. When invoked with `--reset-existing`, first archive stale implementation and documentation files from a non-empty stuck repo so the fresh start is not built on old code or old assumptions by accident.\n\n## Process\n\n1. **Parse the project brief and mode** from `$ARGUMENTS`:\n   - Detect `--reset-existing`, `--in-place-reset`, or an explicit request to archive\u002Freset the current codebase before bootstrap.\n   - Extract the project name, purpose, setup instructions, run\u002Ftest commands, and any constraints.\n   - If the brief is missing or too thin to write a useful README, ask for the project name and one-sentence purpose. Ask for setup or run instructions only when the repository does not make them discoverable.\n\n2. **Inspect the target repository:**\n   - Read existing `README.md`, `CLAUDE.md`, `AGENTS.md`, package manifests, obvious build files, and directory names.\n   - Preserve discovered commands and facts. Do not invent dependency managers, deployment targets, or product claims.\n\n3. **Reset existing stale repo when explicitly requested:**\n   - Only perform this step when reset mode is explicit. Never archive or move files during ordinary bootstrap.\n   - Confirm the repo is non-empty and contains stale implementation, docs, research, specs, task files, design notes, or generated app structure. If it is already empty or freshly initialized, skip archival and note why.\n   - Create `archive\u002FYYYY-MM-DD-HHMMSS\u002F` and move stale implementation and documentation files\u002Fdirectories there before writing fresh bootstrap docs.\n   - Archive old docs by default, including `docs\u002F`, `alignment\u002F`, `research\u002F`, `specs\u002F`, `tasks\u002F`, planning reports, implementation notes, design docs, old README content, and prior roadmap\u002Ftodo\u002Fhistory files. These may remain useful as historical evidence in the archive, but they must not stay active as source-of-truth inputs.\n   - Do not archive `.git\u002F`, `.agents\u002F`, `archive\u002F`, `desk-flip-report.md`, root agent config files needed for the current session, or the newly written high-level concept artifact.\n   - Preserve exactly one active concept seed, such as `concept.md` or `README.md` `## Concept`, derived from the bootstrap brief or `desk-flip-report.md`. Keep it high level: product name, target user, core problem, value proposition, non-goals, and open questions. Do not preserve old research\u002Fspec detail as active files.\n   - Preserve a manifest at `archive\u002FYYYY-MM-DD-HHMMSS\u002FMANIFEST.md` listing every moved path, every intentionally preserved path, and the high-level concept source that justified the reset.\n   - Prefer `git mv` for tracked paths so history remains understandable. Use ordinary moves only for untracked paths.\n   - Do not delete old files outright. If a path cannot be moved safely, stop and report the blocker instead of partially resetting further.\n   - After archival, the root should contain only the fresh-start sources of truth: git metadata, agent config, the archive directory, `desk-flip-report.md`, the high-level concept artifact, and any newly written bootstrap docs. Old docs\u002Fresearch\u002Fspecs belong in the archive.\n\n4. **Create or update `README.md`:**\n   - If `README.md` is absent, empty, or placeholder-like, write a concise README with:\n     - `# \u003CProject Name>`\n     - A short purpose summary.\n     - `## Getting Started`\n     - `## Development`\n     - `## Notes`\n   - If `README.md` already has substantial content, preserve it. Ask before replacing it; otherwise add a small bootstrap section only when it improves the file.\n   - Use the project brief as the primary source and repository inspection as supporting evidence.\n\n5. **Provision agent workflow docs:**\n   - Run `\u002Fprovision-agentic-config` for the same repository.\n   - Confirm `CLAUDE.md` and `AGENTS.md` exist after provisioning.\n   - Preserve unrelated existing content in both files.\n\n6. **Verify the result:**\n   - Check that `README.md`, `CLAUDE.md`, and `AGENTS.md` exist.\n   - Confirm the corresponding workflow orchestration block appears exactly once in each of `CLAUDE.md` and `AGENTS.md`.\n   - Report whether the monorepo safety block was included or skipped by `\u002Fprovision-agentic-config`.\n   - In reset mode, check that `archive\u002FYYYY-MM-DD-HHMMSS\u002FMANIFEST.md` exists and lists moved and preserved paths, and verify old docs\u002Fresearch\u002Fspecs\u002Ftasks were archived rather than left active.\n\n7. **Route research-first after product bootstrap:**\n   - If this is a product, app, SaaS, dashboard, internal tool, marketplace, website, or other user-facing restart, rebuild market and lifecycle alignment from the high-level concept before UI requirements or prototypes.\n   - Check `.agents\u002Fproject.json.enabled_packs` when present. If `business-discovery` is not enabled, recommend `\u002Fpack install business-discovery` before `\u002Ficp`. If `customer-lifecycle` is not enabled, include `\u002Fpack install customer-lifecycle` before `\u002Fjourney-map`.\n   - When required packs are available, recommend `\u002Ficp \u003Cconcept>` as the next command. After `\u002Ficp`, the intended sequence is `\u002Fcompetitive-analysis` -> `\u002Fjourney-map` -> `\u002Fux-variations` -> `\u002Fui-interview` -> prototype work.\n   - If current, accepted `research\u002Ficp.md`, `research\u002Fcompetitive-analysis.md`, and `research\u002Fjourney-map.md` already exist from the fresh reset, then recommend `\u002Fux-variations \u003Ctopic>`.\n   - If UX variations already exist but interface details are missing, recommend `\u002Fui-interview \u003Ctopic>`.\n   - Only route directly to `\u002Froadmap` or `\u002Fexec` when the project is non-UI\u002Fnon-product work or already has accepted alignment artifacts and a consolidated prototype.\n   - The intended product sequence after reset is: `\u002Ficp` -> `\u002Fcompetitive-analysis` -> `\u002Fjourney-map` -> `\u002Fux-variations` -> `\u002Fui-interview` -> build variants\u002Fprototypes via `\u002Fexec` or the applicable prototype-building route -> `\u002Fuat --variant-evaluation` -> `\u002Fconsolidate-variations` -> `\u002Fresearch-roadmap --post-prototype` -> `\u002Fspec-interview` or `\u002Froadmap`.\n\n## Output\n\n```markdown\nBootstrapped repository\n- README.md: [created | updated | preserved], source: [arguments | prompts | existing content]\n- Reset archive: [created archive\u002FYYYY-MM-DD-HHMMSS | skipped (\u003Creason>)]\n- Active concept seed: [concept.md | README.md ## Concept | other]\n- CLAUDE.md: [created | updated | unchanged], corresponding workflow block appears once\n- AGENTS.md: [created | updated | unchanged], corresponding workflow block appears once\n- Monorepo safety block: [included (\u003Cheuristic>) | skipped]\n- Verification: [commands\u002Fchecks run]\n- Recommended next command: [\u002Fpack install business-discovery | \u002Fpack install customer-lifecycle | \u002Ficp \u003Cconcept> | \u002Fux-variations \u003Ctopic> | \u002Fui-interview \u003Ctopic> | \u002Froadmap | \u002Fexec]\n```\n\n## Constraints\n\n- Do not overwrite substantial existing `README.md` content without explicit user confirmation.\n- Do not invent setup, test, deploy, or architecture details that are not in the brief or repository.\n- Keep the README concise and useful for a new contributor.\n- Do not modify files other than `README.md`, `CLAUDE.md`, and `AGENTS.md` unless the user explicitly asks or invokes reset mode.\n- Reset mode may move stale files, including old docs\u002Fresearch\u002Fspecs\u002Ftasks, into `archive\u002FYYYY-MM-DD-HHMMSS\u002F` and write that archive's `MANIFEST.md`; it may not delete files outright.\n- In reset mode, do not preserve old docs as active files just because they were marked salvageable. Use them only as archived historical evidence; active research and requirements restart from the high-level concept.\n- Do not create, modify, or suggest GitHub Actions workflows.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":26,"version":40,"description":7,"argument-hint":41},"v0.0","\u003Cproject brief>","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Frepo-maintenance\u002Fclaude\u002Fbootstrap-repo\u002Farchive\u002Fv0.0",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill bootstrap-repo",{"tool":58,"command":59},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill bootstrap-repo",{"tool":61,"command":62},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill bootstrap-repo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Frepo-maintenance\u002Fclaude\u002Fbootstrap-repo\u002Farchive\u002Fv0.0\u002FSKILL.md",true,[],[67,79,89,101,116,127],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":35},"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",[],[74,75,76,77,30,78],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":35},"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",[],[86,87,88,78,76,30],"deck install valid","deck","install",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":35},"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",[],[96,97,98,78,99,100,76,30],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":35},"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",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[113,114,78,99,30,115,76],"codex missing skill valid","missing","fallback",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":35},"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",[122],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},[78,99,115,124,125,126,30,76],"base skill","codex base skill fallback valid","base",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":35},"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",[],[78,98,97,134,100,30,76],"claude pack guard valid"]