[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D6SVADSBHTW8B3Q8XYR98A":3,"skill-same:01M6D6SVADSBHTW8B3Q8XYR98A":67},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6D6SVADSBHTW8B3Q8XYR98A","porter-five-forces",null,"Porter's Five Forces competitive analysis - industry structure, rivalry, substitutes, entrants, buyer power, and supplier power","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-research\u002Fcodex\u002Fcompetitive-analysis\u002Fframeworks\u002Fporter-five-forces\u002Farchive\u002Fv0.8\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"porter five forces","research","analysis","page","v0","competitive analysis","power","alignment","structure","2026-11-10 10:12:30",false,"---\nname: porter-five-forces\ndescription: Porter's Five Forces competitive analysis - industry structure, rivalry, substitutes, entrants, buyer power, and supplier power\ntype: research\nversion: v0.8\nrequired_conventions: [alignment-page]\ninvocation: sub-skill\nparent: competitive-analysis\n---\n\n## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill. 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# Porter's Five Forces - Competitive Structure Analysis\n\n## Parent Orchestrator Routing\n\nRun only through the parent orchestrator `$competitive-analysis` as part of its Research Session Loop. If the user needs to continue pending framework work, tell them to start a fresh Codex session and re-invoke `$competitive-analysis` with the same product\u002Fresearch path argument when present, for example `$competitive-analysis research\u002Fafps-tracker`.\n\nDo not ask users to invoke this framework directly or with a path-shaped child framework command. Do not emit downstream routing labels, child-framework commands, execution-loop commands, or downstream skill recommendations from this framework subskill.\n\n## Terminal Handoff Contract\n\nWhen this framework is run inline and stops on its findings `review` page, the terminal response must end with:\n\n```markdown\n## Next Work\nReview the framework findings page and compile YAML. The parent will consume that YAML, write the approved intermediate, and recalculate whether another framework or synthesis is next.\n\n## Continue In A Fresh Session\n$competitive-analysis\n```\n\nUse the same product\u002Fresearch path argument when present. Do not decide from inside the framework whether the next parent run executes another framework or synthesis; the parent orchestrator recalculates that from the run manifest and canonical-intermediate files after approval.\n\nThe findings `review` page must also include `agent_routing` in bottom compiled YAML with this parent-owned shape:\n\n```yaml\nagent_routing:\n  workflow: pattern-a-research-loop\n  parent_skill: competitive-analysis\n  command: \"$competitive-analysis research\u002F{slug}\"\n  product_path: research\u002F{slug}\n  gate_owner: parent-orchestrator\n  gate_type: framework-findings\n  framework_slug: porter-five-forces\n  framework_mode: inline-subskill\n  run_manifest: research\u002F{slug}\u002F_working\u002Fcompetitive-analysis-run.yaml\n  next_resolution: parent-resolves-from-yaml-and-filesystem\n```\n\nOmit `product_path` in flat mode, keep `command` identical to the parent command shown under `## Continue In A Fresh Session`, and never replace it with a child framework path command. The parent consumes this YAML, writes the approved intermediate, archives the working packet\u002Fpage, and recalculates the next state.\n\n## Report-First Approval Gate\n\nDefault to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.\n\nDo not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.\n\nAfter approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.\n\nDo not include downstream routing language. While the framework findings page is in `review`, use only the parent-owned terminal handoff sections above. Parent synthesis owns downstream routing only after approved synthesis artifacts are written or updated.\n\n## Staged Research Workflow\n\nUse this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.\n\n1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions\u002Fconfidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.\n2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source\u002Fcode checks, and write only a non-canonical working packet: flat mode uses `research\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`; product-path mode uses `research\u002F{slug}\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`. Replace `\u003Cskill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `\u003Cpre>\u003Ccode>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions\u002Fconfidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.\n3. **Stage 3 - Finalize approved artifacts.** Consume final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths below, and convert the alignment page to `confirmed` with the approval record preserved.\n\nCanonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.\n\n## Prerequisites\n\n- **Hard**: Parent context from `research\u002F_working\u002Fpreliminary-competitive-analysis-research.md` or `research\u002F{slug}\u002F_working\u002Fpreliminary-competitive-analysis-research.md`. If absent, read `research\u002Ficp.md` or `research\u002F{slug}\u002Ficp.md` plus repo context; if neither exists, tell the user to run `$competitive-analysis` first and stop.\n- **Soft**: Existing `research\u002Fcompetitive-analysis-*.md`, `research\u002Fcustomer-feedback.md`, `research\u002Fjourney-map.md`, specs, and codebase context.\n\n## Product-Path Scope Resolution\n\nUse the parent `competitive-analysis` product-path scope when present. Otherwise resolve scope by reading `research\u002F.progress.yaml`, selecting active non-archived product paths, and writing under `research\u002F{slug}\u002F` only when that path is active or explicitly named.\n\n## Process\n\n1. Load parent context and identify the relevant category, buyer\u002Fcustomer frame, seeded competitors, and source gaps.\n2. Use web search to validate the market boundary and identify evidence for each force.\n3. Assess:\n   - competitive rivalry\n   - threat of new entrants\n   - threat of substitutes and DIY alternatives\n   - buyer\u002Fcustomer power\n   - supplier\u002Fplatform\u002Fchannel power\n4. Score each force as low, moderate, or high pressure with evidence and confidence.\n5. Identify the structural constraints, exploitable gaps, and risks that the parent synthesis should carry forward.\n6. Present findings before writing and incorporate factual corrections.\n\n## Output\n\n### `research\u002Fcompetitive-analysis-porter-five-forces.md` (or `research\u002F{slug}\u002Fcompetitive-analysis-porter-five-forces.md`)\n\n```markdown\n# Porter's Five Forces Analysis\n\n> Based on: [parent context, sources]\n> Date: [current date]\n> Methodology: Porter's Five Forces\n\n## Market Boundary\n[Category, buyer frame, and competitors included\u002Fexcluded]\n\n## Force Assessment\n| Force | Pressure | Evidence | Confidence | Implication |\n|-------|----------|----------|------------|-------------|\n| Rivalry | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [what synthesis should consider] |\n| New Entrants | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Substitutes | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Buyer Power | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Supplier Power | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n\n## Structural Opportunities\n[White-space openings created by force dynamics]\n\n## Structural Risks\n[Forces that could undermine the product or category thesis]\n\n## Evidence Matrix\n| Claim | Source | Evidence Type | Confidence |\n|-------|--------|---------------|------------|\n```\n\n## Constraints\n\n- Every competitor or market fact must be source-backed.\n- Prefer recent sources from the last 12 months and flag older evidence.\n- Do not recommend product features, positioning, architecture, or downstream skills.\n- This is a sub-skill; do not emit downstream routing labels or command recommendations.\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\u002Fporter-five-forces-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install \u003Cpack>` from the project shell, instead of the target skill. 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# Porter's Five Forces - Competitive Structure Analysis\n\n## Parent Orchestrator Routing\n\nRun only through the parent orchestrator `$competitive-analysis` as part of its Research Session Loop. If the user needs to continue pending framework work, tell them to start a fresh Codex session and re-invoke `$competitive-analysis` with the same product\u002Fresearch path argument when present, for example `$competitive-analysis research\u002Fafps-tracker`.\n\nDo not ask users to invoke this framework directly or with a path-shaped child framework command. Do not emit downstream routing labels, child-framework commands, execution-loop commands, or downstream skill recommendations from this framework subskill.\n\n## Terminal Handoff Contract\n\nWhen this framework is run inline and stops on its findings `review` page, the terminal response must end with:\n\n```markdown\n## Next Work\nReview the framework findings page and compile YAML. The parent will consume that YAML, write the approved intermediate, and recalculate whether another framework or synthesis is next.\n\n## Continue In A Fresh Session\n$competitive-analysis\n```\n\nUse the same product\u002Fresearch path argument when present. Do not decide from inside the framework whether the next parent run executes another framework or synthesis; the parent orchestrator recalculates that from the run manifest and canonical-intermediate files after approval.\n\nThe findings `review` page must also include `agent_routing` in bottom compiled YAML with this parent-owned shape:\n\n```yaml\nagent_routing:\n  workflow: pattern-a-research-loop\n  parent_skill: competitive-analysis\n  command: \"$competitive-analysis research\u002F{slug}\"\n  product_path: research\u002F{slug}\n  gate_owner: parent-orchestrator\n  gate_type: framework-findings\n  framework_slug: porter-five-forces\n  framework_mode: inline-subskill\n  run_manifest: research\u002F{slug}\u002F_working\u002Fcompetitive-analysis-run.yaml\n  next_resolution: parent-resolves-from-yaml-and-filesystem\n```\n\nOmit `product_path` in flat mode, keep `command` identical to the parent command shown under `## Continue In A Fresh Session`, and never replace it with a child framework path command. The parent consumes this YAML, writes the approved intermediate, archives the working packet\u002Fpage, and recalculates the next state.\n\n## Report-First Approval Gate\n\nDefault to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.\n\nDo not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.\n\nAfter approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.\n\nDo not include downstream routing language. While the framework findings page is in `review`, use only the parent-owned terminal handoff sections above. Parent synthesis owns downstream routing only after approved synthesis artifacts are written or updated.\n\n## Staged Research Workflow\n\nUse this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.\n\n1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions\u002Fconfidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.\n2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source\u002Fcode checks, and write only a non-canonical working packet: flat mode uses `research\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`; product-path mode uses `research\u002F{slug}\u002F_working\u002Fpreliminary-\u003Cskill>-research.md`. Replace `\u003Cskill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `\u003Cpre>\u003Ccode>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions\u002Fconfidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.\n3. **Stage 3 - Finalize approved artifacts.** Consume final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths below, and convert the alignment page to `confirmed` with the approval record preserved.\n\nCanonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.\n\n## Prerequisites\n\n- **Hard**: Parent context from `research\u002F_working\u002Fpreliminary-competitive-analysis-research.md` or `research\u002F{slug}\u002F_working\u002Fpreliminary-competitive-analysis-research.md`. If absent, read `research\u002Ficp.md` or `research\u002F{slug}\u002Ficp.md` plus repo context; if neither exists, tell the user to run `$competitive-analysis` first and stop.\n- **Soft**: Existing `research\u002Fcompetitive-analysis-*.md`, `research\u002Fcustomer-feedback.md`, `research\u002Fjourney-map.md`, specs, and codebase context.\n\n## Product-Path Scope Resolution\n\nUse the parent `competitive-analysis` product-path scope when present. Otherwise resolve scope by reading `research\u002F.progress.yaml`, selecting active non-archived product paths, and writing under `research\u002F{slug}\u002F` only when that path is active or explicitly named.\n\n## Process\n\n1. Load parent context and identify the relevant category, buyer\u002Fcustomer frame, seeded competitors, and source gaps.\n2. Use web search to validate the market boundary and identify evidence for each force.\n3. Assess:\n   - competitive rivalry\n   - threat of new entrants\n   - threat of substitutes and DIY alternatives\n   - buyer\u002Fcustomer power\n   - supplier\u002Fplatform\u002Fchannel power\n4. Score each force as low, moderate, or high pressure with evidence and confidence.\n5. Identify the structural constraints, exploitable gaps, and risks that the parent synthesis should carry forward.\n6. Present findings before writing and incorporate factual corrections.\n\n## Output\n\n### `research\u002Fcompetitive-analysis-porter-five-forces.md` (or `research\u002F{slug}\u002Fcompetitive-analysis-porter-five-forces.md`)\n\n```markdown\n# Porter's Five Forces Analysis\n\n> Based on: [parent context, sources]\n> Date: [current date]\n> Methodology: Porter's Five Forces\n\n## Market Boundary\n[Category, buyer frame, and competitors included\u002Fexcluded]\n\n## Force Assessment\n| Force | Pressure | Evidence | Confidence | Implication |\n|-------|----------|----------|------------|-------------|\n| Rivalry | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [what synthesis should consider] |\n| New Entrants | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Substitutes | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Buyer Power | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n| Supplier Power | Low\u002FModerate\u002FHigh | [sources] | High\u002FMedium\u002FLow | [implication] |\n\n## Structural Opportunities\n[White-space openings created by force dynamics]\n\n## Structural Risks\n[Forces that could undermine the product or category thesis]\n\n## Evidence Matrix\n| Claim | Source | Evidence Type | Confidence |\n|-------|--------|---------------|------------|\n```\n\n## Constraints\n\n- Every competitor or market fact must be source-backed.\n- Prefer recent sources from the last 12 months and flag older evidence.\n- Do not recommend product features, positioning, architecture, or downstream skills.\n- This is a sub-skill; do not emit downstream routing labels or command recommendations.\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\u002Fporter-five-forces-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":25,"parent":38,"version":39,"invocation":40,"description":7,"required_conventions":41},"competitive-analysis","v0.8","sub-skill",[42],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbusiness-research\u002Fcodex\u002Fcompetitive-analysis\u002Fframeworks\u002Fporter-five-forces\u002Farchive\u002Fv0.8",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill porter-five-forces",{"tool":59,"command":60},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill porter-five-forces",{"tool":62,"command":63},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill porter-five-forces","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-research\u002Fcodex\u002Fcompetitive-analysis\u002Fframeworks\u002Fporter-five-forces\u002Farchive\u002Fv0.8\u002FSKILL.md",true,[],[68,80,90,102,115,126],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":33},"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",[],[75,76,77,78,28,79],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":33},"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",[],[87,88,89,79,77,28],"deck install valid","deck","install",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":33},"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",[],[97,98,99,79,100,101,77,28],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":33},"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",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[112,113,79,100,28,114,77],"codex missing skill valid","missing","fallback",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":33},"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",[121],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},[79,100,114,123,124,125,28,77],"base skill","codex base skill fallback valid","base",{"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":132,"publishedAt":33},"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",[],[79,99,98,133,101,28,77],"claude pack guard valid"]