[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZVSSFFBVM8ABW0PC5THPB":3,"skill-same:01M6FZVSSFFBVM8ABW0PC5THPB":70},{"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":69},"01M6FZVSSFFBVM8ABW0PC5THPB","youtube-description-optimizer",null,"Audit, draft, or template YouTube descriptions and metadata for promise-match, search clarity, CTA hierarchy, links, chapters, hashtags, and upload readiness","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\u002Fyoutube-ops\u002Fclaude\u002Fyoutube-description-optimizer\u002Farchive\u002Fv0.1\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"youtube description optimizer","youtube","optimizer","series","links","cta","URL","script","compare","name","readiness","id","research","upload","outline","draft","template","Video","audit","search","2026-11-10 10:12:30",false,"---\nname: youtube-description-optimizer\ndescription: Audit, draft, or template YouTube descriptions and metadata for promise-match, search clarity, CTA hierarchy, links, chapters, hashtags, and upload readiness\ntype: research\nversion: v0.1\nargument-hint: \"\u003Cvideo URL | video ID | script\u002Foutline path | channel slug> [--mode audit|draft|template] [--series \u003Cname>] [--compare-channel \u003Cslug>]\"\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 `\u002Fpack install \u003Cpack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.\n\n# YouTube Description Optimizer\n\nInvoke as `\u002Fyoutube-description-optimizer`.\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\nOptimize YouTube descriptions and adjacent metadata for existing videos, future uploads, and repeatable series templates. This is the description\u002Fmetadata lane; use `\u002Fyoutube-video-audit` for full single-video performance diagnosis and `\u002Fyoutube-title-thumbnail-audit` for title\u002Fthumbnail packaging.\n\n## Inputs\n\n- Required target: video URL, video ID, script\u002Foutline path, channel slug, or existing creator-media artifact.\n- Optional `--mode audit|draft|template`: default `audit` for video targets, `draft` for script\u002Foutline targets, and `template` for channel\u002Fseries targets.\n- Optional `--series \u003Cname>`: names the repeatable show or format for template work.\n- Optional `--compare-channel \u003Cslug>`: reuse channel evidence under `research\u002Fyoutube\u002Fdata\u002F\u003Cslug>\u002F`.\n\n## Workflow\n\n1. Resolve the target and mode. If the target is ambiguous, infer from file existence and URL\u002Fvideo-ID shape before asking the user.\n2. Prefer existing evidence:\n   - `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002Fmetadata-*.json`\n   - `research\u002Fyoutube\u002Fdata\u002F\u003Cslug>\u002Fvideos-*.jsonl`\n   - `research\u002Fyoutube\u002Fvideo-audit-*.md`\n   - `research\u002Fyoutube\u002Ftitle-thumbnail-audit-*.md`\n   - `research\u002Fyoutube\u002Fchannel-audit-*.md`\n   - `specs\u002Fyoutube\u002Fseries-*.md`\n   - script or outline files supplied by the user\n3. For existing videos, use public metadata descriptions, tags, chapters, title, URL, upload date, and available transcript\u002Fopening evidence. If public metadata is missing and the target is a video URL or ID, fetch it through `yt-dlp --dump-json \"VIDEO_URL\"` and persist it under `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002Fmetadata-YYYY-MM-DD.json`.\n4. For future drafts, use the supplied script\u002Foutline plus any creator-positioning, content-programming, series, product-led media, and search-positioning artifacts that are current.\n5. For templates, use channel\u002Fseries evidence to define reusable blocks, required links, optional links, CTA hierarchy, chapter style, hashtag policy, sponsor\u002Fdisclosure slots, and update rules.\n6. Analyze:\n   - First 2 lines and above-the-fold promise support.\n   - Search\u002Ftopic clarity, entity names, reusable keywords, and avoidable keyword stuffing.\n   - Match between title, thumbnail promise, intro\u002Fhook, chapters, and description.\n   - CTA hierarchy, link order, stale or missing links, sponsor\u002Fdisclosure language, attribution\u002Fcredits, pinned-comment fit, and hashtag discipline.\n   - Whether the description supports acquisition, trust-building, proof, education, launch support, community, or conversion.\n7. Produce practical edits: keep\u002Fchange\u002Fadd\u002Fremove notes, rewritten description blocks, pinned-comment recommendation when useful, and a future-video checklist.\n\n## Output\n\nCreate the `research\u002Fyoutube\u002F`, `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002F`, and `specs\u002Fyoutube\u002F` directories if they do not exist.\n\nWrite exactly one artifact:\n\n- Audit mode: `research\u002Fyoutube\u002Fdescription-optimizer-\u003Cvideo-id>-YYYY-MM-DD.md`\n- Draft mode: `research\u002Fyoutube\u002Fdescription-draft-\u003Cslug>-YYYY-MM-DD.md`\n- Template mode: `specs\u002Fyoutube\u002Fdescription-template-\u003Cslug>.md`\n\nUse this structure:\n\n```markdown\n# YouTube Description Optimizer - [Target]\n\n> Mode: audit \u002F draft \u002F template\n> Target: [URL, video ID, file path, channel slug, or series]\n> Date: YYYY-MM-DD\n> Evidence: [paths used]\n\n## Evidence Coverage\n\n| Evidence | Status | Path or gap |\n|---|---|---|\n| Public metadata | Available \u002F Missing \u002F Not applicable | ... |\n| Transcript or opening | Available \u002F Missing \u002F Not applicable | ... |\n| Channel evidence | Available \u002F Missing \u002F Not applicable | ... |\n| Script or outline | Available \u002F Missing \u002F Not applicable | ... |\n| Series template | Available \u002F Missing \u002F Not applicable | ... |\n\n## Description Diagnosis\n\n- **First 2 lines**: ...\n- **Promise match**: ...\n- **Search\u002Ftopic clarity**: ...\n- **CTA\u002Flink hierarchy**: ...\n- **Chapters\u002Fhashtags\u002Fdisclosures**: ...\n- **Pinned-comment fit**: ...\n\n## Recommended Description\n\n[Upload-ready description or revised description block.]\n\n## Metadata Notes\n\n- **Tags\u002Fkeywords**: ...\n- **Chapters**: ...\n- **Hashtags**: ...\n- **Links and credits**: ...\n- **Disclosure\u002Fsponsor slots**: ...\n\n## Keep \u002F Change \u002F Add \u002F Remove\n\n| Action | Item | Why | Evidence |\n|---|---|---|---|\n| Keep \u002F Change \u002F Add \u002F Remove | ... | ... | ... |\n\n## Future Checklist\n\n[Reusable checks for the next upload or this series.]\n```\n\n## Constraints\n\n- Do not invent links, product URLs, sponsors, disclosures, chapters, transcript details, comments, or owner-only metrics.\n- Mark missing evidence explicitly instead of filling gaps.\n- Do not recommend deceptive metadata, keyword stuffing, tag spam, misleading hashtags, or CTAs that conflict with the video's promise.\n- Keep description changes practical for the creator's apparent production capacity.\n- Archive existing canonical artifacts before replacing them under `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-relative-path>`.\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 following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fyoutube-description-optimizer-{topic}.html`.\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 `\u002Fpack install \u003Cpack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.\n\n# YouTube Description Optimizer\n\nInvoke as `\u002Fyoutube-description-optimizer`.\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\nOptimize YouTube descriptions and adjacent metadata for existing videos, future uploads, and repeatable series templates. This is the description\u002Fmetadata lane; use `\u002Fyoutube-video-audit` for full single-video performance diagnosis and `\u002Fyoutube-title-thumbnail-audit` for title\u002Fthumbnail packaging.\n\n## Inputs\n\n- Required target: video URL, video ID, script\u002Foutline path, channel slug, or existing creator-media artifact.\n- Optional `--mode audit|draft|template`: default `audit` for video targets, `draft` for script\u002Foutline targets, and `template` for channel\u002Fseries targets.\n- Optional `--series \u003Cname>`: names the repeatable show or format for template work.\n- Optional `--compare-channel \u003Cslug>`: reuse channel evidence under `research\u002Fyoutube\u002Fdata\u002F\u003Cslug>\u002F`.\n\n## Workflow\n\n1. Resolve the target and mode. If the target is ambiguous, infer from file existence and URL\u002Fvideo-ID shape before asking the user.\n2. Prefer existing evidence:\n   - `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002Fmetadata-*.json`\n   - `research\u002Fyoutube\u002Fdata\u002F\u003Cslug>\u002Fvideos-*.jsonl`\n   - `research\u002Fyoutube\u002Fvideo-audit-*.md`\n   - `research\u002Fyoutube\u002Ftitle-thumbnail-audit-*.md`\n   - `research\u002Fyoutube\u002Fchannel-audit-*.md`\n   - `specs\u002Fyoutube\u002Fseries-*.md`\n   - script or outline files supplied by the user\n3. For existing videos, use public metadata descriptions, tags, chapters, title, URL, upload date, and available transcript\u002Fopening evidence. If public metadata is missing and the target is a video URL or ID, fetch it through `yt-dlp --dump-json \"VIDEO_URL\"` and persist it under `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002Fmetadata-YYYY-MM-DD.json`.\n4. For future drafts, use the supplied script\u002Foutline plus any creator-positioning, content-programming, series, product-led media, and search-positioning artifacts that are current.\n5. For templates, use channel\u002Fseries evidence to define reusable blocks, required links, optional links, CTA hierarchy, chapter style, hashtag policy, sponsor\u002Fdisclosure slots, and update rules.\n6. Analyze:\n   - First 2 lines and above-the-fold promise support.\n   - Search\u002Ftopic clarity, entity names, reusable keywords, and avoidable keyword stuffing.\n   - Match between title, thumbnail promise, intro\u002Fhook, chapters, and description.\n   - CTA hierarchy, link order, stale or missing links, sponsor\u002Fdisclosure language, attribution\u002Fcredits, pinned-comment fit, and hashtag discipline.\n   - Whether the description supports acquisition, trust-building, proof, education, launch support, community, or conversion.\n7. Produce practical edits: keep\u002Fchange\u002Fadd\u002Fremove notes, rewritten description blocks, pinned-comment recommendation when useful, and a future-video checklist.\n\n## Output\n\nCreate the `research\u002Fyoutube\u002F`, `research\u002Fyoutube\u002Fdata\u002F\u003Cvideo-id>\u002F`, and `specs\u002Fyoutube\u002F` directories if they do not exist.\n\nWrite exactly one artifact:\n\n- Audit mode: `research\u002Fyoutube\u002Fdescription-optimizer-\u003Cvideo-id>-YYYY-MM-DD.md`\n- Draft mode: `research\u002Fyoutube\u002Fdescription-draft-\u003Cslug>-YYYY-MM-DD.md`\n- Template mode: `specs\u002Fyoutube\u002Fdescription-template-\u003Cslug>.md`\n\nUse this structure:\n\n```markdown\n# YouTube Description Optimizer - [Target]\n\n> Mode: audit \u002F draft \u002F template\n> Target: [URL, video ID, file path, channel slug, or series]\n> Date: YYYY-MM-DD\n> Evidence: [paths used]\n\n## Evidence Coverage\n\n| Evidence | Status | Path or gap |\n|---|---|---|\n| Public metadata | Available \u002F Missing \u002F Not applicable | ... |\n| Transcript or opening | Available \u002F Missing \u002F Not applicable | ... |\n| Channel evidence | Available \u002F Missing \u002F Not applicable | ... |\n| Script or outline | Available \u002F Missing \u002F Not applicable | ... |\n| Series template | Available \u002F Missing \u002F Not applicable | ... |\n\n## Description Diagnosis\n\n- **First 2 lines**: ...\n- **Promise match**: ...\n- **Search\u002Ftopic clarity**: ...\n- **CTA\u002Flink hierarchy**: ...\n- **Chapters\u002Fhashtags\u002Fdisclosures**: ...\n- **Pinned-comment fit**: ...\n\n## Recommended Description\n\n[Upload-ready description or revised description block.]\n\n## Metadata Notes\n\n- **Tags\u002Fkeywords**: ...\n- **Chapters**: ...\n- **Hashtags**: ...\n- **Links and credits**: ...\n- **Disclosure\u002Fsponsor slots**: ...\n\n## Keep \u002F Change \u002F Add \u002F Remove\n\n| Action | Item | Why | Evidence |\n|---|---|---|---|\n| Keep \u002F Change \u002F Add \u002F Remove | ... | ... | ... |\n\n## Future Checklist\n\n[Reusable checks for the next upload or this series.]\n```\n\n## Constraints\n\n- Do not invent links, product URLs, sponsors, disclosures, chapters, transcript details, comments, or owner-only metrics.\n- Mark missing evidence explicitly instead of filling gaps.\n- Do not recommend deceptive metadata, keyword stuffing, tag spam, misleading hashtags, or CTAs that conflict with the video's promise.\n- Keep description changes practical for the creator's apparent production capacity.\n- Archive existing canonical artifacts before replacing them under `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002F\u003Coriginal-relative-path>`.\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 following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fyoutube-description-optimizer-{topic}.html`.\n",{"name":5,"type":31,"version":44,"description":7,"argument-hint":45},"v0.1","\u003Cvideo URL | video ID | script\u002Foutline path | channel slug> [--mode audit|draft|template] [--series \u003Cname>] [--compare-channel \u003Cslug>]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fyoutube-ops\u002Fclaude\u002Fyoutube-description-optimizer\u002Farchive\u002Fv0.1",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":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill youtube-description-optimizer",{"tool":62,"command":63},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill youtube-description-optimizer",{"tool":65,"command":66},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill youtube-description-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fyoutube-ops\u002Fclaude\u002Fyoutube-description-optimizer\u002Farchive\u002Fv0.1\u002FSKILL.md",true,[],[71,84,94,106,121,132],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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",[],[78,79,80,81,82,83],"source checkout allowed","checkout","fixture","only","v0","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":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",[],[91,92,93,83,80,82],"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":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",[],[101,102,103,83,104,105,80,82],"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":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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,119,83,104,82,120,80],"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":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",[127],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[83,104,120,129,130,131,82,80],"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":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",[],[83,103,102,139,105,82,80],"claude pack guard valid"]