[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D5DMA0ZHCVJM8WF5SE4FSV":3,"skill-same:01M6D5DMA0ZHCVJM8WF5SE4FSV":86},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6D5DMA0ZHCVJM8WF5SE4FSV","scale-audit",null,"Evaluate codebase against enterprise ICP for production readiness, compliance, and multi-stakeholder journey coverage","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\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"audit","scale audit","compliance","Enterprise","Production","analysis","page","coverage","v0","only","alignment","journey","production readiness","artifact","visual","2026-11-10 10:12:30",false,"---\nname: scale-audit\ndescription: Evaluate codebase against enterprise ICP for production readiness, compliance, and multi-stakeholder journey coverage\ntype: analysis\nversion: v0.5\nrequired_conventions: [alignment-page]\ncontext_intake: artifact_only\nvisual_tier: visual\n---\n\n## Pack Availability Guard\n\nWhen recommending a skill from another pack, verify the target pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If it is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Only the currently running skill and skills verified available in the active session or project-local install state are directly recommendable. For unavailable pack skills, recommend `npx skillpacks install \u003Cpack-or-skill>`; for unavailable base skills, recommend `npx skillpacks init` before the skill.\n\n# Scale Audit — Enterprise Production Readiness\n\nInvoke as `$scale-audit`.\n\nAutomated analysis that evaluates the codebase against `research\u002Fenterprise-icp.md`. Identifies gaps for enterprise deals — stakeholder journey coverage, compliance, infrastructure, and operations.\n\n## Prerequisites\n\n`research\u002Fenterprise-icp.md` (or `research\u002F{slug}\u002Fenterprise-icp.md`) must exist. If not, tell the user to run `$enterprise-icp` first.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Load Context & Evaluate\n\n1. Read `research\u002Fenterprise-icp.md` (or `research\u002F{slug}\u002Fenterprise-icp.md`), `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`), `research\u002Fmvp-gap.md` (or `research\u002F{slug}\u002Fmvp-gap.md`) (if they exist), codebase, and in-progress\u002Fadvisory work from `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, and `tasks\u002Frecurring-todo.md` (if they exist).\n2. Evaluate the codebase across:\n   - **Per-Persona Journey Coverage** — Can each stakeholder complete their workflow?\n   - **Onboarding Gaps** — Self-serve, team, SSO-provisioned, migration, training\n   - **Compliance Readiness** — SOC 2, GDPR, HIPAA, encryption, secrets management\n   - **Infrastructure Readiness** — Multi-tenancy, scaling, DR, observability, CI\u002FCD\n   - **Operational Readiness** — Incident response, SLA monitoring, support, customer success\n   - **Escalated Startup Gaps** — Unresolved MVP gaps now critical at enterprise scale\n3. Tag gaps: `hard-blocker`, `soft-blocker`, or `differentiator`. Estimate effort (S\u002FM\u002FL\u002FXL).\n\n## Deliverables\n\n- `specs\u002Fscale-audit.md` (or `specs\u002F{slug}\u002Fscale-audit.md`) — Gap analysis with stakeholder coverage matrix, compliance matrix, priority tags, and `$user-flow-map` prompts for each unspecced flow\u002Fdesign-shape gap\n\nThe output file must end with a `## Next Steps` section containing a **Recommended** item and 2–4 other contextual options. Choose the recommendation by the first matching condition:\n\n1. IF any `hard-blocker` lacks flow\u002Fdesign shape or a full implementation spec: `$user-flow-map [top blocker]` — map the highest-priority enterprise blocker into concrete screen flow, decisions, branches, states, and recovery paths before UI\u002Flayout planning.\n2. IF enterprise stakeholder journey context is missing: `$journey-map enterprise` — map enterprise stakeholder journeys before sequencing build work.\n3. IF startup gaps escalated and `research\u002Fmvp-gap.md` is missing or stale: `$mvp-gap` — re-evaluate startup readiness first.\n4. IF enterprise SLA or compliance gaps lack closure metrics: `$metrics` — define metrics covering enterprise SLAs.\n5. OTHERWISE: `$roadmap` — sequence the already-specced enterprise work into implementation phases.\n\nOnly recommend `$roadmap` as the primary next step when every hard-blocker already has a full spec or is already tracked in `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, or `tasks\u002Frecurring-todo.md`.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- Analysis only — do not make code changes.\n- Every gap must cite specific evidence.\n- Distinguish \"first enterprise deal\" from \"100th enterprise deal.\"\n- Include `$user-flow-map \u003Ctopic>` prompts for gaps lacking flow\u002Fdesign shape or full specs. Use `$ux-variations --layout-mode \u003Ctopic>` only when flow and UI requirements already exist but layout alternatives are missing.\n- `## Next Steps` must be the final section in the output file, with a recommended next step and 2–4 other contextual options.\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fscale-audit-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","## Pack Availability Guard\n\nWhen recommending a skill from another pack, verify the target pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If it is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Only the currently running skill and skills verified available in the active session or project-local install state are directly recommendable. For unavailable pack skills, recommend `npx skillpacks install \u003Cpack-or-skill>`; for unavailable base skills, recommend `npx skillpacks init` before the skill.\n\n# Scale Audit — Enterprise Production Readiness\n\nInvoke as `$scale-audit`.\n\nAutomated analysis that evaluates the codebase against `research\u002Fenterprise-icp.md`. Identifies gaps for enterprise deals — stakeholder journey coverage, compliance, infrastructure, and operations.\n\n## Prerequisites\n\n`research\u002Fenterprise-icp.md` (or `research\u002F{slug}\u002Fenterprise-icp.md`) must exist. If not, tell the user to run `$enterprise-icp` first.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Load Context & Evaluate\n\n1. Read `research\u002Fenterprise-icp.md` (or `research\u002F{slug}\u002Fenterprise-icp.md`), `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`), `research\u002Fmvp-gap.md` (or `research\u002F{slug}\u002Fmvp-gap.md`) (if they exist), codebase, and in-progress\u002Fadvisory work from `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, and `tasks\u002Frecurring-todo.md` (if they exist).\n2. Evaluate the codebase across:\n   - **Per-Persona Journey Coverage** — Can each stakeholder complete their workflow?\n   - **Onboarding Gaps** — Self-serve, team, SSO-provisioned, migration, training\n   - **Compliance Readiness** — SOC 2, GDPR, HIPAA, encryption, secrets management\n   - **Infrastructure Readiness** — Multi-tenancy, scaling, DR, observability, CI\u002FCD\n   - **Operational Readiness** — Incident response, SLA monitoring, support, customer success\n   - **Escalated Startup Gaps** — Unresolved MVP gaps now critical at enterprise scale\n3. Tag gaps: `hard-blocker`, `soft-blocker`, or `differentiator`. Estimate effort (S\u002FM\u002FL\u002FXL).\n\n## Deliverables\n\n- `specs\u002Fscale-audit.md` (or `specs\u002F{slug}\u002Fscale-audit.md`) — Gap analysis with stakeholder coverage matrix, compliance matrix, priority tags, and `$user-flow-map` prompts for each unspecced flow\u002Fdesign-shape gap\n\nThe output file must end with a `## Next Steps` section containing a **Recommended** item and 2–4 other contextual options. Choose the recommendation by the first matching condition:\n\n1. IF any `hard-blocker` lacks flow\u002Fdesign shape or a full implementation spec: `$user-flow-map [top blocker]` — map the highest-priority enterprise blocker into concrete screen flow, decisions, branches, states, and recovery paths before UI\u002Flayout planning.\n2. IF enterprise stakeholder journey context is missing: `$journey-map enterprise` — map enterprise stakeholder journeys before sequencing build work.\n3. IF startup gaps escalated and `research\u002Fmvp-gap.md` is missing or stale: `$mvp-gap` — re-evaluate startup readiness first.\n4. IF enterprise SLA or compliance gaps lack closure metrics: `$metrics` — define metrics covering enterprise SLAs.\n5. OTHERWISE: `$roadmap` — sequence the already-specced enterprise work into implementation phases.\n\nOnly recommend `$roadmap` as the primary next step when every hard-blocker already has a full spec or is already tracked in `tasks\u002Froadmap.md`, `tasks\u002Ftodo.md`, `tasks\u002Fmanual-todo.md`, `tasks\u002Frecord-todo.md`, or `tasks\u002Frecurring-todo.md`.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- Analysis only — do not make code changes.\n- Every gap must cite specific evidence.\n- Distinguish \"first enterprise deal\" from \"100th enterprise deal.\"\n- Include `$user-flow-map \u003Ctopic>` prompts for gaps lacking flow\u002Fdesign shape or full specs. Use `$ux-variations --layout-mode \u003Ctopic>` only when flow and UI requirements already exist but layout alternatives are missing.\n- `## Next Steps` must be the final section in the output file, with a recommended next step and 2–4 other contextual options.\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fscale-audit-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":29,"version":44,"description":7,"visual_tier":38,"context_intake":45,"required_conventions":46},"v0.5","artifact_only",[47],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill scale-audit",{"tool":64,"command":65},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill scale-audit",{"tool":67,"command":68},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill scale-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit\u002FSKILL.md",true,[72,78,82],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",250,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit\u002Fagents\u002Fopenai.yaml",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"ALIGNMENT-PAGE.md",54067,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit\u002FALIGNMENT-PAGE.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"CHANGELOG.md",1413,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fcodex\u002Fscale-audit\u002FCHANGELOG.md",[87,98,108,120,135,146],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[94,95,96,33,32,97],"source checkout allowed","checkout","fixture","valid",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[105,106,107,97,96,32],"deck install valid","deck","install",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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",[],[115,116,117,97,118,119,96,32],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"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",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[132,133,97,118,32,134,96],"codex missing skill valid","missing","fallback",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"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",[141],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[97,118,134,143,144,145,32,96],"base skill","codex base skill fallback valid","base",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"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",[],[97,117,116,153,119,32,96],"claude pack guard valid"]