[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZ062ESTNC6PT6FPV2YSVX":3,"skill-same:01M6FZ062ESTNC6PT6FPV2YSVX":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6FZ062ESTNC6PT6FPV2YSVX","video-build",null,"Transform an approved video script into a Remotion build specification with scaffolded project directory, compositions, scene components, and render config","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\u002Fremotion\u002Fcodex\u002Fvideo-build\u002Farchive\u002Fv0.1\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"build","video build","Video","project","components","script","with","render","transform","style","video script","resolution","planning","directory","specification","motion","minimal","text","Remotion","config","2026-11-10 10:12:30",false,"---\nname: video-build\ndescription: Transform an approved video script into a Remotion build specification with scaffolded project directory, compositions, scene components, and render config\ntype: planning\nversion: v0.1\nargument-hint: \"\u003Cscript-path-or-slug> [--style minimal|motion-heavy|kinetic-text] [--fps 30|60] [--resolution 1080p|4k]\"\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 `$pack 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# Video Build\n\nInvoke as `$video-build`.\n\nTake an approved video script and produce a build specification document and a scaffolded Remotion project directory with compositions, scene components, asset manifest, and render config.\n\n## Prerequisites\n\n- `specs\u002Fyoutube\u002Fvideo-script-\u003Cslug>.md` must exist.\n- Remotion availability is checked (`npx remotion --help`). If not installed, produce the spec and scaffold but defer render commands to `tasks\u002Fmanual-todo.md`.\n\n## Inputs\n\n- `specs\u002Fyoutube\u002Fvideo-script-\u003Cslug>.md`\n- `specs\u002Fyoutube\u002Fseries-\u003Cslug>.md` (visual identity)\n- `research\u002Fyoutube\u002Fproduct-led-media-map-\u003Cslug>.md` (proof assets)\n- Codebase scan for design tokens, logos, and fonts.\n\n## Process\n\n0. Resolve arguments: script path or slug, style (`minimal`, `motion-heavy`, `kinetic-text`), fps (`30`, `60`), resolution (`1080p`, `4k`).\n1. Load script, series spec (visual identity), product-led-media-map (proof assets), and scan codebase for design tokens, logos, and fonts.\n2. Text-based checkpoint: confirm visual identity (colors, fonts, logo), asset sourcing per asset requirement, technical config (platform, fps, resolution, existing Remotion project?) with the user before proceeding.\n3. Design component tree: map script scenes to Remotion components with durations in frames, visual elements, animation timing, and audio references.\n4. Text-based checkpoint: present build specification — component tree diagram, per-scene build plan, asset manifest, render config. Validate with user.\n5. Write output only after user confirmation.\n\n## Output\n\nCreate the `specs\u002Fyoutube\u002F` and `src\u002Fvideos\u002F\u003Cslug>\u002F` directories if they do not exist.\n\nWrite `specs\u002Fyoutube\u002Fvideo-build-\u003Cslug>.md` with:\n\n- **Build Brief:** script reference, style, fps, resolution, target platform.\n- **Component Tree:** diagram and component descriptions.\n- **Scene-by-Scene Build Plan:** table — component, duration (frames\u002Fseconds), visual elements, animation type, assets.\n- **Asset Manifest:** table — name, type, status (`available`\u002F`placeholder`\u002F`needs-creation`), path, notes.\n- **Audio Plan:** narration, music, SFX, sync points.\n- **Render Configuration:** composition ID, fps, width, height, codec, output format.\n- **Typography & Color Tokens:** fonts, sizes, colors from brand\u002Fseries.\n- **Transition Library:** which transitions between which scenes.\n- **Next Steps.**\n\nWrite `specs\u002Fyoutube\u002Fvideo-build-\u003Cslug>-interview.md` with the interview log.\n\nScaffold `src\u002Fvideos\u002F\u003Cslug>\u002F`:\n\n```\ncomposition.tsx        \u002F\u002F Root composition with Sequence timing\nscenes\u002F               \u002F\u002F One component per script scene\ntransitions\u002F          \u002F\u002F Reusable transition components\ncomponents\u002F           \u002F\u002F Shared UI (LowerThird, BrowserFrame, etc.)\nassets\u002F\n  manifest.json       \u002F\u002F Asset paths and statuses\nconfig\u002F\n  render.ts           \u002F\u002F Render configuration\n  theme.ts            \u002F\u002F Colors, fonts, spacing tokens\n```\n\n### Task Classification\n\nAfter writing output:\n\n- `tasks\u002Ftodo.md`: render commands, asset sourcing automation, subtitle generation.\n- `tasks\u002Fmanual-todo.md`: record footage, source music, record voiceover, YouTube upload, metadata, thumbnail, scheduling.\n- `tasks\u002Frecurring-todo.md`: review performance at 7-day and 30-day marks.\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\u002Fvideo-build-{topic}.html`.\n\n## Constraints\n\n- Every scene component must match the approved script timing — do not add or remove scenes.\n- Do not generate AI voiceover without explicit user approval.\n- Do not embed copyrighted assets without the user confirming licensing.\n- Asset manifest must clearly distinguish `available` vs `placeholder` vs `needs-creation`.\n- Respect series visual identity when a series spec exists.\n- Present the build specification before writing — never write until the user confirms.\n- Keep components composable — series should reuse intro\u002Foutro\u002Ftransition\u002Flower-third across episodes.\n- Do not expose secrets, private customer data, or unreleased commitments.\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 `$pack 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# Video Build\n\nInvoke as `$video-build`.\n\nTake an approved video script and produce a build specification document and a scaffolded Remotion project directory with compositions, scene components, asset manifest, and render config.\n\n## Prerequisites\n\n- `specs\u002Fyoutube\u002Fvideo-script-\u003Cslug>.md` must exist.\n- Remotion availability is checked (`npx remotion --help`). If not installed, produce the spec and scaffold but defer render commands to `tasks\u002Fmanual-todo.md`.\n\n## Inputs\n\n- `specs\u002Fyoutube\u002Fvideo-script-\u003Cslug>.md`\n- `specs\u002Fyoutube\u002Fseries-\u003Cslug>.md` (visual identity)\n- `research\u002Fyoutube\u002Fproduct-led-media-map-\u003Cslug>.md` (proof assets)\n- Codebase scan for design tokens, logos, and fonts.\n\n## Process\n\n0. Resolve arguments: script path or slug, style (`minimal`, `motion-heavy`, `kinetic-text`), fps (`30`, `60`), resolution (`1080p`, `4k`).\n1. Load script, series spec (visual identity), product-led-media-map (proof assets), and scan codebase for design tokens, logos, and fonts.\n2. Text-based checkpoint: confirm visual identity (colors, fonts, logo), asset sourcing per asset requirement, technical config (platform, fps, resolution, existing Remotion project?) with the user before proceeding.\n3. Design component tree: map script scenes to Remotion components with durations in frames, visual elements, animation timing, and audio references.\n4. Text-based checkpoint: present build specification — component tree diagram, per-scene build plan, asset manifest, render config. Validate with user.\n5. Write output only after user confirmation.\n\n## Output\n\nCreate the `specs\u002Fyoutube\u002F` and `src\u002Fvideos\u002F\u003Cslug>\u002F` directories if they do not exist.\n\nWrite `specs\u002Fyoutube\u002Fvideo-build-\u003Cslug>.md` with:\n\n- **Build Brief:** script reference, style, fps, resolution, target platform.\n- **Component Tree:** diagram and component descriptions.\n- **Scene-by-Scene Build Plan:** table — component, duration (frames\u002Fseconds), visual elements, animation type, assets.\n- **Asset Manifest:** table — name, type, status (`available`\u002F`placeholder`\u002F`needs-creation`), path, notes.\n- **Audio Plan:** narration, music, SFX, sync points.\n- **Render Configuration:** composition ID, fps, width, height, codec, output format.\n- **Typography & Color Tokens:** fonts, sizes, colors from brand\u002Fseries.\n- **Transition Library:** which transitions between which scenes.\n- **Next Steps.**\n\nWrite `specs\u002Fyoutube\u002Fvideo-build-\u003Cslug>-interview.md` with the interview log.\n\nScaffold `src\u002Fvideos\u002F\u003Cslug>\u002F`:\n\n```\ncomposition.tsx        \u002F\u002F Root composition with Sequence timing\nscenes\u002F               \u002F\u002F One component per script scene\ntransitions\u002F          \u002F\u002F Reusable transition components\ncomponents\u002F           \u002F\u002F Shared UI (LowerThird, BrowserFrame, etc.)\nassets\u002F\n  manifest.json       \u002F\u002F Asset paths and statuses\nconfig\u002F\n  render.ts           \u002F\u002F Render configuration\n  theme.ts            \u002F\u002F Colors, fonts, spacing tokens\n```\n\n### Task Classification\n\nAfter writing output:\n\n- `tasks\u002Ftodo.md`: render commands, asset sourcing automation, subtitle generation.\n- `tasks\u002Fmanual-todo.md`: record footage, source music, record voiceover, YouTube upload, metadata, thumbnail, scheduling.\n- `tasks\u002Frecurring-todo.md`: review performance at 7-day and 30-day marks.\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\u002Fvideo-build-{topic}.html`.\n\n## Constraints\n\n- Every scene component must match the approved script timing — do not add or remove scenes.\n- Do not generate AI voiceover without explicit user approval.\n- Do not embed copyrighted assets without the user confirming licensing.\n- Asset manifest must clearly distinguish `available` vs `placeholder` vs `needs-creation`.\n- Respect series visual identity when a series spec exists.\n- Present the build specification before writing — never write until the user confirms.\n- Keep components composable — series should reuse intro\u002Foutro\u002Ftransition\u002Flower-third across episodes.\n- Do not expose secrets, private customer data, or unreleased commitments.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":36,"version":49,"description":7,"argument-hint":50},"v0.1","\u003Cscript-path-or-slug> [--style minimal|motion-heavy|kinetic-text] [--fps 30|60] [--resolution 1080p|4k]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fremotion\u002Fcodex\u002Fvideo-build\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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill video-build",{"tool":67,"command":68},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill video-build",{"tool":70,"command":71},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill video-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fremotion\u002Fcodex\u002Fvideo-build\u002Farchive\u002Fv0.1\u002FSKILL.md",true,[],[76,89,99,111,124,135],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[83,84,85,86,87,88],"source checkout allowed","checkout","fixture","only","v0","valid",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":44},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[96,97,98,88,85,87],"deck install valid","deck","install",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":44},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[106,107,108,88,109,110,85,87],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":44},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[121,122,88,109,87,123,85],"codex missing skill valid","missing","fallback",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":44},"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",[130],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},[88,109,123,132,133,134,87,85],"base skill","codex base skill fallback valid","base",{"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":141,"publishedAt":44},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[88,108,107,142,110,87,85],"claude pack guard valid"]