[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D7ZP9W1XXJQ4KV67CMFFJB":3,"skill-same:01M6D7ZP9W1XXJQ4KV67CMFFJB":71},{"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":26,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6D7ZP9W1XXJQ4KV67CMFFJB","content-programming",null,"Design an evidence-backed channel programming plan across pillars, formats, cadence, roles, and measurement without writing scripts","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\u002Fcreator-foundation\u002Fcodex\u002Fcontent-programming\u002Farchive\u002Fv0.0\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[27,28,29,30,31,32,33,34,35,36,37,38,39],"content","programming","content programming","design","writing","research","plan","v0","channel","evidence","positioning","across","roles","2026-11-10 10:12:30",false,"---\nname: content-programming\ndescription: Design an evidence-backed channel programming plan across pillars, formats, cadence, roles, and measurement without writing scripts\ntype: research\nversion: v0.0\nargument-hint: \"[channel slug or positioning path]\"\n---\n\n# Content Programming\n\nInvoke as `$content-programming`.\n\n## Report-First Approval Gate\n\nDefault to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.\n\nDo not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write\u002Fupdate\u002Ffix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research\u002Freport writes.\n\nWhen stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.\n\nCreate a programming strategy for a creator-media channel. This is the channel architecture step, not a script-writing step.\n\n## Inputs\n\n- Prefer `research\u002Fcreator-presence\u002F\u003Cslug>.md` when present for cross-platform themes, signature formats, cadence constraints, and proof assets.\n- `research\u002Fyoutube\u002Fcreator-positioning-\u003Cslug>.md`\n- `research\u002Fyoutube\u002Fportfolio-\u003Cslug>.md`\n- Optional peer benchmark and product-led media map.\n\n## Output\n\nWrite `research\u002Fyoutube\u002Fcontent-programming-\u003Cslug>.md` with:\n\n- Programming thesis: what the channel repeatedly earns attention for.\n- Pillars: 3-5 durable topic lanes with audience jobs.\n- Formats: recurring formats mapped to archetypes and roles.\n- Cadence: publishing rhythm, minimum viable cadence, and seasonal constraints.\n- Portfolio balance: acquisition vs trust vs proof vs education vs retention.\n- Measurement plan: primary metrics, secondary metrics, and warning signs.\n- Cleanup\u002Frefactor plan for existing videos.\n- Next series candidates to specify with `$series-spec`.\n\n## Approved Artifact Handoff\n\nAfter an approved synthesized write, explicit write\u002Fupdate mode, or any direct artifact mutation:\n\n- List every created or updated synthesized artifact path in the final response.\n- State the verification performed, such as readback, schema\u002Fcheck command, or why no executable verification applies for a Markdown-only strategy artifact.\n- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.\n- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.\n- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.\n\n## Intent-Aware Routing\n\nBefore applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:\n\n- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.\n- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.\n- Upload prep: recommend packaging, title\u002Fthumbnail, description, chapters, or final metadata work before broader strategy work.\n- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.\n- Owner analytics or private\u002Fmanual platform evidence: route to an explicit manual\u002Fguide handoff instead of inventing unavailable metrics.\n- Dirty intended artifacts: route to shipping\u002Fcommit\u002Fhandoff first, not another creator strategy skill.\n\nUse the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.\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 at `alignment\u002Fcontent-programming-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.\n\n**Full content requirement.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item. It is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research\u002Fassumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.\n\n**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, nav, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.\n\n**Alignment gates.** Treat gates as explicit review sections inside the HTML page. A gate blocks finalization until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions\u002Fconfidence, scope\u002Fnon-goals, candidate\u002Fverdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route.\n\n**Report-only research gates.** For report-only or pre-approval research skills, the alignment page must explicitly contain evidence coverage, assumptions\u002Fconfidence, recommended path, proposed file changes, and approval gates before any canonical research, spec, or task file is created or updated.\n\n\n**Required inline questions.** Each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: \"Other \u002F None of the above\" backed by a multi-line text box for free-form input, and \"Need clarification\" backed by an optional notes box where the user can explain what is unclear. When any radio option other than \"Other\" or \"Need clarification\" is selected, show an optional \"Additional notes\" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom \"Decisions & Clarifications\" section.\n\n**Gate YAML contract.** At the bottom of the page, include a \"Compile Answers\" button that aggregates answers from all inline gate questions throughout the page, including free-text notes. The button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit \"Copy YAML\" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.\n\n**Pre-approval stop.** Before user approval, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide the compiled YAML answers. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after compiled YAML has been provided and the approved artifacts have been written or updated.\n\n**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving compiled answers, highlight what changed since the previous version. The agent chooses inline annotation or side-by-side layout per situation.\n\n**Archiving.** Before replacing an existing alignment page, archive it to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002Falignment\u002Fcontent-programming-{topic}.html`.\n\n**Browser open.** Attempt to open the resulting HTML page in the browser and report whether the open succeeded or was blocked. A blocked browser-open attempt does not make the skill fail when the files were written correctly.\n\n## Next-Skill Routing\n\nAfter writing the artifact, recommend the next contextual creator-media skill in the final response as `Recommended next skill: \u003Ccommand>`.\n\nDefault recommendation: `$series-spec`.\n\nIf the default successor already exists and is current, recommend the first missing or stale downstream creator-media artifact in this order:\n\n`$creator-presence-dossier` -> `$youtube-channel-audit` -> `$youtube-video-audit` -> `$youtube-vid-research` -> `$youtube-concept-research` -> `$youtube-competitive-research` -> `$youtube-title-thumbnail-audit` -> `$youtube-description-optimizer` -> `$youtube-portfolio` -> `$youtube-peer-benchmark` -> `$youtube-search-positioning` -> `$youtube-cadence-diagnosis` -> `$creator-positioning` -> `$content-programming` -> `$series-spec` -> `$product-led-media-map` -> `$creator-metrics-review`\n\nIf the sequence is ambiguous, multiple upstream artifacts are stale, or the recommendation depends on channel-level strategy vs programming-level changes, recommend `$creator-metrics-review` when metrics evidence exists, otherwise recommend the default successor and explain the missing artifact.\n\n## Constraints\n\n- Do not generate full scripts or a calendar unless explicitly asked.\n- Every proposed pillar must connect to audit, positioning, product, or benchmark evidence.\n- Use the dossier when present as preferred creator context, while preserving channel audit and portfolio evidence for YouTube-only programming.\n- Keep programming realistic for the apparent production capacity.\n","# Content Programming\n\nInvoke as `$content-programming`.\n\n## Report-First Approval Gate\n\nDefault to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.\n\nDo not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write\u002Fupdate\u002Ffix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research\u002Freport writes.\n\nWhen stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.\n\nCreate a programming strategy for a creator-media channel. This is the channel architecture step, not a script-writing step.\n\n## Inputs\n\n- Prefer `research\u002Fcreator-presence\u002F\u003Cslug>.md` when present for cross-platform themes, signature formats, cadence constraints, and proof assets.\n- `research\u002Fyoutube\u002Fcreator-positioning-\u003Cslug>.md`\n- `research\u002Fyoutube\u002Fportfolio-\u003Cslug>.md`\n- Optional peer benchmark and product-led media map.\n\n## Output\n\nWrite `research\u002Fyoutube\u002Fcontent-programming-\u003Cslug>.md` with:\n\n- Programming thesis: what the channel repeatedly earns attention for.\n- Pillars: 3-5 durable topic lanes with audience jobs.\n- Formats: recurring formats mapped to archetypes and roles.\n- Cadence: publishing rhythm, minimum viable cadence, and seasonal constraints.\n- Portfolio balance: acquisition vs trust vs proof vs education vs retention.\n- Measurement plan: primary metrics, secondary metrics, and warning signs.\n- Cleanup\u002Frefactor plan for existing videos.\n- Next series candidates to specify with `$series-spec`.\n\n## Approved Artifact Handoff\n\nAfter an approved synthesized write, explicit write\u002Fupdate mode, or any direct artifact mutation:\n\n- List every created or updated synthesized artifact path in the final response.\n- State the verification performed, such as readback, schema\u002Fcheck command, or why no executable verification applies for a Markdown-only strategy artifact.\n- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.\n- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.\n- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.\n\n## Intent-Aware Routing\n\nBefore applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:\n\n- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.\n- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.\n- Upload prep: recommend packaging, title\u002Fthumbnail, description, chapters, or final metadata work before broader strategy work.\n- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.\n- Owner analytics or private\u002Fmanual platform evidence: route to an explicit manual\u002Fguide handoff instead of inventing unavailable metrics.\n- Dirty intended artifacts: route to shipping\u002Fcommit\u002Fhandoff first, not another creator strategy skill.\n\nUse the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.\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 at `alignment\u002Fcontent-programming-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.\n\n**Full content requirement.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item. It is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research\u002Fassumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.\n\n**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, nav, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.\n\n**Alignment gates.** Treat gates as explicit review sections inside the HTML page. A gate blocks finalization until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions\u002Fconfidence, scope\u002Fnon-goals, candidate\u002Fverdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route.\n\n**Report-only research gates.** For report-only or pre-approval research skills, the alignment page must explicitly contain evidence coverage, assumptions\u002Fconfidence, recommended path, proposed file changes, and approval gates before any canonical research, spec, or task file is created or updated.\n\n\n**Required inline questions.** Each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: \"Other \u002F None of the above\" backed by a multi-line text box for free-form input, and \"Need clarification\" backed by an optional notes box where the user can explain what is unclear. When any radio option other than \"Other\" or \"Need clarification\" is selected, show an optional \"Additional notes\" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom \"Decisions & Clarifications\" section.\n\n**Gate YAML contract.** At the bottom of the page, include a \"Compile Answers\" button that aggregates answers from all inline gate questions throughout the page, including free-text notes. The button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit \"Copy YAML\" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.\n\n**Pre-approval stop.** Before user approval, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide the compiled YAML answers. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after compiled YAML has been provided and the approved artifacts have been written or updated.\n\n**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving compiled answers, highlight what changed since the previous version. The agent chooses inline annotation or side-by-side layout per situation.\n\n**Archiving.** Before replacing an existing alignment page, archive it to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002Falignment\u002Fcontent-programming-{topic}.html`.\n\n**Browser open.** Attempt to open the resulting HTML page in the browser and report whether the open succeeded or was blocked. A blocked browser-open attempt does not make the skill fail when the files were written correctly.\n\n## Next-Skill Routing\n\nAfter writing the artifact, recommend the next contextual creator-media skill in the final response as `Recommended next skill: \u003Ccommand>`.\n\nDefault recommendation: `$series-spec`.\n\nIf the default successor already exists and is current, recommend the first missing or stale downstream creator-media artifact in this order:\n\n`$creator-presence-dossier` -> `$youtube-channel-audit` -> `$youtube-video-audit` -> `$youtube-vid-research` -> `$youtube-concept-research` -> `$youtube-competitive-research` -> `$youtube-title-thumbnail-audit` -> `$youtube-description-optimizer` -> `$youtube-portfolio` -> `$youtube-peer-benchmark` -> `$youtube-search-positioning` -> `$youtube-cadence-diagnosis` -> `$creator-positioning` -> `$content-programming` -> `$series-spec` -> `$product-led-media-map` -> `$creator-metrics-review`\n\nIf the sequence is ambiguous, multiple upstream artifacts are stale, or the recommendation depends on channel-level strategy vs programming-level changes, recommend `$creator-metrics-review` when metrics evidence exists, otherwise recommend the default successor and explain the missing artifact.\n\n## Constraints\n\n- Do not generate full scripts or a calendar unless explicitly asked.\n- Every proposed pillar must connect to audit, positioning, product, or benchmark evidence.\n- Use the dossier when present as preferred creator context, while preserving channel audit and portfolio evidence for YouTube-only programming.\n- Keep programming realistic for the apparent production capacity.\n",{"name":5,"type":32,"version":45,"description":7,"argument-hint":46},"v0.0","[channel slug or positioning path]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fcreator-foundation\u002Fcodex\u002Fcontent-programming\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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill content-programming",{"tool":63,"command":64},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill content-programming",{"tool":66,"command":67},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill content-programming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fcreator-foundation\u002Fcodex\u002Fcontent-programming\u002Farchive\u002Fv0.0\u002FSKILL.md",true,[],[72,84,94,106,121,132],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":40},"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",[],[79,80,81,82,34,83],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":40},"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",[],[91,92,93,83,81,34],"deck install valid","deck","install",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":40},"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",[],[101,102,103,83,104,105,81,34],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":40},"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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,119,83,104,34,120,81],"codex missing skill valid","missing","fallback",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":40},"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",[127],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[83,104,120,129,130,131,34,81],"base skill","codex base skill fallback valid","base",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":40},"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",[],[83,103,102,139,105,34,81],"claude pack guard valid"]