[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D3FBKZWA4DZ3PC5PZYFTJM":3,"skill-same:01M6D3FBKZWA4DZ3PC5PZYFTJM":75},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":68},"01M6D3FBKZWA4DZ3PC5PZYFTJM","init-agentic-skills",null,"Make the base agentic-skills available in a project by installing them project-local with npx skillpacks init, report and fix skill-install drift, clean up legacy user-home installs, and run guided setup for project-local domain packs. Use when Claude needs to enable base skills for a project, repair stale installs, confirm initialization status, remove old global installs, or set up and route domain packs.","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\u002Fbase\u002Fclaude\u002Finit-agentic-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"agentic","init agentic skills","init","clean","uninstall","project","local","repair","domain","drift","route","npx","Legacy","up","use","remove","ops","fix","SET","doctor","2026-11-10 10:12:30",false,"---\nname: init-agentic-skills\ndescription: Make the base agentic-skills available in a project by installing them project-local with npx skillpacks init, report and fix skill-install drift, clean up legacy user-home installs, and run guided setup for project-local domain packs. Use when Claude needs to enable base skills for a project, repair stale installs, confirm initialization status, remove old global installs, or set up and route domain packs.\ntype: ops\nversion: v0.12\nargument-hint: \"[init|status|doctor|refresh|uninstall-global]\"\n---\n\n# Init Agentic Skills\n\nMake the base agentic-skills available by installing them **project-local** into the current project's `.claude\u002Fskills` and `.codex\u002Fskills`. Installation is distributed through the npm `skillpacks` package — there is no user-home (global) install path. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive\u002F`; pinned installs intentionally point at `archive\u002F\u003Cversion>`. Keep domain packs project-local too; use the **Guided Pack Setup** below, or `npx skillpacks install \u003Cpack-or-skill>` when packs are needed.\n\n## Process\n\n1. Parse `$ARGUMENTS`:\n   - No args, `init`, or `refresh`: run `npx skillpacks init` from the project root to install the base skills project-local (`.claude\u002Fskills` + `.codex\u002Fskills`) and enable `base_skills` in `.agents\u002Fproject.json`. Use `npx skillpacks refresh` instead when the project is already initialized and you only need to recreate roots from `.agents\u002Fproject.json`.\n   - `status`: run `npx skillpacks status` to report the project designation, enabled packs, and installed skills.\n   - `doctor`: run `npx skillpacks doctor` to report project skill-install drift (read-only). It compares installed `.claude\u002Fskills` and `.codex\u002Fskills` copies against their canonical sources via the `.agentic-skills-managed` marker's `source_sha`. Report `STALE` skills with the printed fix command, `unknown` skills as needing a refresh to enable tracking, `missing` skills whose source is gone, and `pinned` skills as frozen. Run `npx skillpacks doctor --fix` to clean generated skill-root drift.\n   - `uninstall-global`: run `npx skillpacks uninstall-global` only after confirming the user wants legacy repo-managed base installs removed from `~\u002F.claude\u002Fskills` and `~\u002F.codex\u002Fskills`. This cleans up installs created by the retired user-home init path; it removes only skillpacks-owned installs and leaves unmanaged directories untouched.\n   - `help`, `--help`, or `-h`: run `npx skillpacks --help`.\n2. Report the command run, the project skill directories, installed counts, and any warnings about non-repo-managed collisions.\n3. Explain pack access separately:\n   - Do not install `packs\u002F*` as base skills.\n   - In the project that needs domain workflows, run the **Guided Pack Setup** below, or `npx skillpacks install \u003Cpack-or-skill>` from the project shell for an explicit pack or individual pack skill.\n   - If a project already has `.agents\u002Fproject.json`, run `scripts\u002Fpack.sh refresh` (or `npx skillpacks refresh`) after this base initialization to recreate local pack skill roots.\n4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:\n   - Claude Code: run `\u002Freload-skills` first; `\u002Fclear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude\u002Fskills` directory did not exist at session start or the skill is still invisible.\n   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.\n\n## Guided Pack Setup\n\nRun this when the user wants to enable domain packs in a project and has not named an explicit pack list.\n\n1. If `.agents\u002Fproject.json` exists, run `scripts\u002Fpack.sh refresh` to recreate local pack skill roots from committed project state, then report the project type, enabled packs, and installed skills.\n2. If `.agents\u002Fproject.json` is missing, inspect the repository before asking the user:\n   - Run `scripts\u002Fpack.sh recommend`.\n   - Check top-level files and directories, package manifests, app\u002Fframework configs, source layout, docs, existing `research\u002F`, `specs\u002F`, and `tasks\u002F` files.\n   - Classify likely packs using the Pack Selection rules below.\n   - Present a concise recommendation with evidence.\n   - Use `AskUserQuestion` to ask which pack or packs to install. Include the recommended pack first. Include kanban only as an explicit opt-in when there is evidence of PoketoWork usage or the user asked for kanban.\n   - After the user confirms, run the source-checkout helper `scripts\u002Fpack.sh install \u003Cpack...>`. For package consumers outside this checkout, the equivalent project-shell route is `npx skillpacks install \u003Cpack...>`.\n   - If the user cancels or asks for more detail, do not install anything.\n3. For `install`, `refresh`, and guided setup installs, report:\n   - `.agents\u002Fproject.json` project type and enabled packs\n   - any `enabled_skills` entries when present, including the skill name and source pack\n   - any `project_scopes` entries when present, including the path, `project_type`, packs, and purpose\n   - local skill roots created or removed under `.claude\u002Fskills` and `.codex\u002Fskills`\n   - any skipped roots caused by non-repo-managed targets\n   - shipping guidance: `.agents\u002Fproject.json` is the committed project designation and should be committed when pack configuration changed; `.claude\u002Fskills\u002F**` and `.codex\u002Fskills\u002F**` are generated local skill roots recreated by `scripts\u002Fpack.sh refresh`, and generated skill roots must not be staged or committed\n\nDo not create `.agents\u002Fproject.json` without user confirmation during guided setup.\n\n## Pack Selection\n\n- Use `business-discovery`, `customer-lifecycle`, `business-growth`, or `business-ops` for SaaS, marketplaces, productivity apps, internal\u002Fadmin tools, business workflows, and enterprise applications. `business-app` is a compatibility alias for all four.\n- Use `creator-foundation`, `youtube-ops`, and `remotion` separately for creator-media work; `creator-media` is a compatibility alias for foundation plus YouTube operations.\n- Use `project-fleet` for control repositories that manage downstream repos, spec-store portfolios, or spin-offs.\n- Use `code-quality` as an additive pack for behavior-preserving refactors, type hygiene, import honesty, dependency-boundary cleanup, and module organization.\n- Use `alignment-loop` for lightweight operator-agent calibration before committing to a full spec-interview pipeline.\n- Use `game` for video games, prototypes, playable entertainment, game engines, store pages, playtest loops, and game assets.\n- Use `devtool` for SDKs, CLIs, APIs, libraries, infrastructure products, developer platforms, and documentation-first developer workflows.\n- PoketoWork kanban packs (`business-app-kanban`, `devtool-kanban`, `game-kanban`, and `poketowork-kanban`) are hibernated while Poketo.work is being rebuilt. Do not recommend or install kanban packs until they are reactivated.\n- Use `exec-loop` for the plan-exec-ship execution workflow (ship, run, ship-end).\n- Use `agent-work-admin` for roadmap management, phase planning, and spec-drift auditing.\n- Use `product-design` for UX exploration, prototyping, feature\u002Fspec\u002FUI interviews, brainstorming, and design systems.\n- Use `code-review` for expert reviews, slim audits, dead-code scans, and regression checks.\n- Use `code-debug` for investigation, debugging, and request tracing.\n- Use `release-ops` for branch lifecycle management, deployment, and releases.\n- Use `product-testing` for UAT journeys and dogfooding.\n- Use `docs-health` for project hygiene auditing and dev-docs reconciliation.\n- Use `research-admin` for research and documentation queue management.\n- Use `skill-dev` for building, interviewing, and creating agentic skills.\n- Use `guided-walkthrough` for step-by-step guides and UAT walkthroughs.\n- Use `session-analytics` for session history analysis and incident triage.\n- Use `teardown` for project teardowns and decommissioning.\n- Use `code-maintenance` for migrations and package updates.\n- Use `gitops` for git sync and feature-based commit workflows.\n- Use `context-transfer` for session handoffs.\n- Use `agent-bridge` for delegating work to other agents.\n- Use `repo-maintenance` for bootstrapping new repos.\n- Use `website-polish` for icon and web asset handling.\n- Use `report-gen` for generating HTML report websites.\n- Use `knowledge-check` for quiz-style knowledge reviews.\n- Use `exec-profile` for execution profile patching.\n- Use `alignment-page-admin` for compiling central alignment pages.\n- Treat `monorepo` and `code-quality` as overlays. Pair overlays with a domain pack unless the user explicitly wants only the overlay behavior.\n- For workflow ordering, lead-in recommendations, and overlay dependencies, read `docs\u002Fpack-workflow-matrix.md`.\n\n## Mixed Monorepos\n\nUse one repo-level `.agents\u002Fproject.json` with a primary default plus scoped overrides:\n\n```json\n{\n  \"project_type\": \"devtool\",\n  \"enabled_packs\": [\"devtool\", \"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n  \"skill_pack_version\": 1,\n  \"project_scopes\": [\n    {\n      \"path\": \"apps\u002Fpitwall-local\",\n      \"project_type\": \"devtool\",\n      \"packs\": [\"devtool\"],\n      \"purpose\": \"Pitwall Local \u002F OSS developer utility work.\"\n    },\n    {\n      \"path\": \"apps\u002Fpitwall-calcllm\",\n      \"project_type\": \"business-app\",\n      \"packs\": [\"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n      \"purpose\": \"CalcLLM-powered connected edition research, GTM, monetization, and SaaS product work.\"\n    },\n    {\n      \"path\": \"packages\u002Fcalcllm-sync\",\n      \"project_type\": \"business-app\",\n      \"packs\": [\"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n      \"purpose\": \"Connected-edition sync and SaaS integration work.\"\n    }\n  ]\n}\n```\n\nWhen a task clearly names a scoped path, route to that scope's `project_type` and packs. When no scope matches, use the top-level `project_type` as the default.\n\n## Constraints\n\n- Drive installation through `npx skillpacks` (the npm `skillpacks` CLI); do not recreate install logic by hand or reintroduce a user-home\u002Fglobal install path.\n- Base skills are project-local: they install into the current project's `.claude\u002Fskills` and `.codex\u002Fskills`, not into `~\u002F.claude\u002Fskills` or `~\u002F.codex\u002Fskills`.\n- Do not overwrite real directories or files under `.claude\u002Fskills` or `.codex\u002Fskills` that are not repo-managed.\n- Treat packs as project-local capabilities managed through the Guided Pack Setup above or `scripts\u002Fpack.sh` (`npx skillpacks` under the hood).\n- Stop and report exact errors if `npx skillpacks` fails.\n- Do not install `packs\u002F*` as base skills in any mode.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Init Agentic Skills\n\nMake the base agentic-skills available by installing them **project-local** into the current project's `.claude\u002Fskills` and `.codex\u002Fskills`. Installation is distributed through the npm `skillpacks` package — there is no user-home (global) install path. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive\u002F`; pinned installs intentionally point at `archive\u002F\u003Cversion>`. Keep domain packs project-local too; use the **Guided Pack Setup** below, or `npx skillpacks install \u003Cpack-or-skill>` when packs are needed.\n\n## Process\n\n1. Parse `$ARGUMENTS`:\n   - No args, `init`, or `refresh`: run `npx skillpacks init` from the project root to install the base skills project-local (`.claude\u002Fskills` + `.codex\u002Fskills`) and enable `base_skills` in `.agents\u002Fproject.json`. Use `npx skillpacks refresh` instead when the project is already initialized and you only need to recreate roots from `.agents\u002Fproject.json`.\n   - `status`: run `npx skillpacks status` to report the project designation, enabled packs, and installed skills.\n   - `doctor`: run `npx skillpacks doctor` to report project skill-install drift (read-only). It compares installed `.claude\u002Fskills` and `.codex\u002Fskills` copies against their canonical sources via the `.agentic-skills-managed` marker's `source_sha`. Report `STALE` skills with the printed fix command, `unknown` skills as needing a refresh to enable tracking, `missing` skills whose source is gone, and `pinned` skills as frozen. Run `npx skillpacks doctor --fix` to clean generated skill-root drift.\n   - `uninstall-global`: run `npx skillpacks uninstall-global` only after confirming the user wants legacy repo-managed base installs removed from `~\u002F.claude\u002Fskills` and `~\u002F.codex\u002Fskills`. This cleans up installs created by the retired user-home init path; it removes only skillpacks-owned installs and leaves unmanaged directories untouched.\n   - `help`, `--help`, or `-h`: run `npx skillpacks --help`.\n2. Report the command run, the project skill directories, installed counts, and any warnings about non-repo-managed collisions.\n3. Explain pack access separately:\n   - Do not install `packs\u002F*` as base skills.\n   - In the project that needs domain workflows, run the **Guided Pack Setup** below, or `npx skillpacks install \u003Cpack-or-skill>` from the project shell for an explicit pack or individual pack skill.\n   - If a project already has `.agents\u002Fproject.json`, run `scripts\u002Fpack.sh refresh` (or `npx skillpacks refresh`) after this base initialization to recreate local pack skill roots.\n4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:\n   - Claude Code: run `\u002Freload-skills` first; `\u002Fclear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude\u002Fskills` directory did not exist at session start or the skill is still invisible.\n   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.\n\n## Guided Pack Setup\n\nRun this when the user wants to enable domain packs in a project and has not named an explicit pack list.\n\n1. If `.agents\u002Fproject.json` exists, run `scripts\u002Fpack.sh refresh` to recreate local pack skill roots from committed project state, then report the project type, enabled packs, and installed skills.\n2. If `.agents\u002Fproject.json` is missing, inspect the repository before asking the user:\n   - Run `scripts\u002Fpack.sh recommend`.\n   - Check top-level files and directories, package manifests, app\u002Fframework configs, source layout, docs, existing `research\u002F`, `specs\u002F`, and `tasks\u002F` files.\n   - Classify likely packs using the Pack Selection rules below.\n   - Present a concise recommendation with evidence.\n   - Use `AskUserQuestion` to ask which pack or packs to install. Include the recommended pack first. Include kanban only as an explicit opt-in when there is evidence of PoketoWork usage or the user asked for kanban.\n   - After the user confirms, run the source-checkout helper `scripts\u002Fpack.sh install \u003Cpack...>`. For package consumers outside this checkout, the equivalent project-shell route is `npx skillpacks install \u003Cpack...>`.\n   - If the user cancels or asks for more detail, do not install anything.\n3. For `install`, `refresh`, and guided setup installs, report:\n   - `.agents\u002Fproject.json` project type and enabled packs\n   - any `enabled_skills` entries when present, including the skill name and source pack\n   - any `project_scopes` entries when present, including the path, `project_type`, packs, and purpose\n   - local skill roots created or removed under `.claude\u002Fskills` and `.codex\u002Fskills`\n   - any skipped roots caused by non-repo-managed targets\n   - shipping guidance: `.agents\u002Fproject.json` is the committed project designation and should be committed when pack configuration changed; `.claude\u002Fskills\u002F**` and `.codex\u002Fskills\u002F**` are generated local skill roots recreated by `scripts\u002Fpack.sh refresh`, and generated skill roots must not be staged or committed\n\nDo not create `.agents\u002Fproject.json` without user confirmation during guided setup.\n\n## Pack Selection\n\n- Use `business-discovery`, `customer-lifecycle`, `business-growth`, or `business-ops` for SaaS, marketplaces, productivity apps, internal\u002Fadmin tools, business workflows, and enterprise applications. `business-app` is a compatibility alias for all four.\n- Use `creator-foundation`, `youtube-ops`, and `remotion` separately for creator-media work; `creator-media` is a compatibility alias for foundation plus YouTube operations.\n- Use `project-fleet` for control repositories that manage downstream repos, spec-store portfolios, or spin-offs.\n- Use `code-quality` as an additive pack for behavior-preserving refactors, type hygiene, import honesty, dependency-boundary cleanup, and module organization.\n- Use `alignment-loop` for lightweight operator-agent calibration before committing to a full spec-interview pipeline.\n- Use `game` for video games, prototypes, playable entertainment, game engines, store pages, playtest loops, and game assets.\n- Use `devtool` for SDKs, CLIs, APIs, libraries, infrastructure products, developer platforms, and documentation-first developer workflows.\n- PoketoWork kanban packs (`business-app-kanban`, `devtool-kanban`, `game-kanban`, and `poketowork-kanban`) are hibernated while Poketo.work is being rebuilt. Do not recommend or install kanban packs until they are reactivated.\n- Use `exec-loop` for the plan-exec-ship execution workflow (ship, run, ship-end).\n- Use `agent-work-admin` for roadmap management, phase planning, and spec-drift auditing.\n- Use `product-design` for UX exploration, prototyping, feature\u002Fspec\u002FUI interviews, brainstorming, and design systems.\n- Use `code-review` for expert reviews, slim audits, dead-code scans, and regression checks.\n- Use `code-debug` for investigation, debugging, and request tracing.\n- Use `release-ops` for branch lifecycle management, deployment, and releases.\n- Use `product-testing` for UAT journeys and dogfooding.\n- Use `docs-health` for project hygiene auditing and dev-docs reconciliation.\n- Use `research-admin` for research and documentation queue management.\n- Use `skill-dev` for building, interviewing, and creating agentic skills.\n- Use `guided-walkthrough` for step-by-step guides and UAT walkthroughs.\n- Use `session-analytics` for session history analysis and incident triage.\n- Use `teardown` for project teardowns and decommissioning.\n- Use `code-maintenance` for migrations and package updates.\n- Use `gitops` for git sync and feature-based commit workflows.\n- Use `context-transfer` for session handoffs.\n- Use `agent-bridge` for delegating work to other agents.\n- Use `repo-maintenance` for bootstrapping new repos.\n- Use `website-polish` for icon and web asset handling.\n- Use `report-gen` for generating HTML report websites.\n- Use `knowledge-check` for quiz-style knowledge reviews.\n- Use `exec-profile` for execution profile patching.\n- Use `alignment-page-admin` for compiling central alignment pages.\n- Treat `monorepo` and `code-quality` as overlays. Pair overlays with a domain pack unless the user explicitly wants only the overlay behavior.\n- For workflow ordering, lead-in recommendations, and overlay dependencies, read `docs\u002Fpack-workflow-matrix.md`.\n\n## Mixed Monorepos\n\nUse one repo-level `.agents\u002Fproject.json` with a primary default plus scoped overrides:\n\n```json\n{\n  \"project_type\": \"devtool\",\n  \"enabled_packs\": [\"devtool\", \"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n  \"skill_pack_version\": 1,\n  \"project_scopes\": [\n    {\n      \"path\": \"apps\u002Fpitwall-local\",\n      \"project_type\": \"devtool\",\n      \"packs\": [\"devtool\"],\n      \"purpose\": \"Pitwall Local \u002F OSS developer utility work.\"\n    },\n    {\n      \"path\": \"apps\u002Fpitwall-calcllm\",\n      \"project_type\": \"business-app\",\n      \"packs\": [\"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n      \"purpose\": \"CalcLLM-powered connected edition research, GTM, monetization, and SaaS product work.\"\n    },\n    {\n      \"path\": \"packages\u002Fcalcllm-sync\",\n      \"project_type\": \"business-app\",\n      \"packs\": [\"business-discovery\", \"customer-lifecycle\", \"business-growth\"],\n      \"purpose\": \"Connected-edition sync and SaaS integration work.\"\n    }\n  ]\n}\n```\n\nWhen a task clearly names a scoped path, route to that scope's `project_type` and packs. When no scope matches, use the top-level `project_type` as the default.\n\n## Constraints\n\n- Drive installation through `npx skillpacks` (the npm `skillpacks` CLI); do not recreate install logic by hand or reintroduce a user-home\u002Fglobal install path.\n- Base skills are project-local: they install into the current project's `.claude\u002Fskills` and `.codex\u002Fskills`, not into `~\u002F.claude\u002Fskills` or `~\u002F.codex\u002Fskills`.\n- Do not overwrite real directories or files under `.claude\u002Fskills` or `.codex\u002Fskills` that are not repo-managed.\n- Treat packs as project-local capabilities managed through the Guided Pack Setup above or `scripts\u002Fpack.sh` (`npx skillpacks` under the hood).\n- Stop and report exact errors if `npx skillpacks` fails.\n- Do not install `packs\u002F*` as base skills in any mode.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":35,"version":44,"description":7,"argument-hint":45},"v0.12","[init|status|doctor|refresh|uninstall-global]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbase\u002Fclaude\u002Finit-agentic-skills",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":57,"prompt":66,"zipAvailable":67},[58,60,63],{"tool":30,"command":59},"npx skills add GeorgeQLe\u002Fagentic-skills --skill init-agentic-skills",{"tool":61,"command":62},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill init-agentic-skills",{"tool":64,"command":65},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill init-agentic-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbase\u002Fclaude\u002Finit-agentic-skills\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"CHANGELOG.md","REFERENCE","参考文档",3650,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbase\u002Fclaude\u002Finit-agentic-skills\u002FCHANGELOG.md",[76,89,99,111,126,137],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":39},"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",[],[83,84,85,86,87,88],"source checkout allowed","checkout","fixture","only","v0","valid",{"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":39},"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",[],[96,97,98,88,85,87],"deck install valid","deck","install",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":39},"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",[],[106,107,108,88,109,110,85,87],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":39},"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",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[123,124,88,109,87,125,85],"codex missing skill valid","missing","fallback",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":133,"publishedAt":39},"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",[132],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[88,109,125,134,135,136,87,85],"base skill","codex base skill fallback valid","base",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":39},"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",[],[88,108,107,144,110,87,85],"claude pack guard valid"]