[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJDBK8EDRF0F3GPWY4QFPV":3,"skill-same:01M7DJDBK8EDRF0F3GPWY4QFPV":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7DJDBK8EDRF0F3GPWY4QFPV","video-shortform",null,"Short-form video generation skill — 3-10 second clips for product\nreveals, motion teasers, ambient loops. Defaults to Seedance 2 but\nworks the same with Kling 3 \u002F 4, Veo 3 or Sora 2. Output is one MP4\nsaved to the project folder. When the workspace also ships an\ninteractive-video \u002F hyperframes skill, prefer composing several short\nshots into a single timeline rather than one long monolithic clip.","andremolnar\u002Fopen-open-design","andremolnar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F919644?v=4","01M7DHE1X4QH6SJBHR92VG5N84","01M7DHE1XRHK1WQV34AM9M328E",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fvideo-shortform\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: video-shortform\ndescription: |\n  Short-form video generation skill — 3-10 second clips for product\n  reveals, motion teasers, ambient loops. Defaults to Seedance 2 but\n  works the same with Kling 3 \u002F 4, Veo 3 or Sora 2. Output is one MP4\n  saved to the project folder. When the workspace also ships an\n  interactive-video \u002F hyperframes skill, prefer composing several short\n  shots into a single timeline rather than one long monolithic clip.\ntriggers:\n  - \"video\"\n  - \"clip\"\n  - \"shortform\"\n  - \"reel\"\n  - \"短视频\"\n  - \"动效\"\nod:\n  mode: video\n  surface: video\n  scenario: marketing\n  preview:\n    type: html\n    entry: example.html\n  design_system:\n    requires: false\n  example_prompt: |\n    5-second product reveal — ceramic coffee mug rotating on a soft\n    paper backdrop, warm side-light from camera-left, micro dust motes\n    drifting through the beam. Cinematic, 16:9, slow drift on the camera.\n---\n\n# Video Shortform Skill\n\nShort-form (≤ 10s) is the sweet spot for current text-to-video models —\nthey're great at one **shot** with one **idea**, weaker at multi-cut\nnarratives. Plan one shot per call.\n\nSpecial case: `hyperframes-html` is **not** a photoreal text-to-video\nmodel. It's a local HTML-to-MP4 renderer. For that model, do not roleplay\ncinematography or \"real-world\" camera physics. Treat the brief as a motion\ndesign card \u002F title-frame \u002F product interstitial, ask at most one\nclarifying question, then dispatch immediately.\n\n## Resource map\n\n```\nvideo-shortform\u002F\n├── SKILL.md\n└── example.html\n```\n\n## Workflow\n\n### Step 0 — Read the project metadata\n\n`videoModel`, `videoLength` (seconds), `videoAspect`. These are\nhard-locks — clamp the prompt to whatever the chosen model supports\n(Seedance 2 caps at 10s; Kling 4 supports up to 10s + image-to-video;\nVeo 3 supports 8s with audio).\n\n### Step 1 — Plan the shot\n\nWrite the shotlist BEFORE calling the model:\n\n| Slot | Content |\n|---|---|\n| Subject | What's in frame? |\n| Camera | Static \u002F pan \u002F push-in \u002F orbit? |\n| Lighting | Key direction + temperature |\n| Motion | What moves, at what pace? Subject motion vs camera motion. |\n| Sound | Ambient bed? (only if the model supports audio) |\n\nNormally, show this to the user as a one-sentence plan before\ndispatching — they can redirect cheaply.\n\nFor `hyperframes-html`, skip the extra pre-dispatch narration once the\nuser has answered the discovery form. Collapse the plan into the actual\ngeneration prompt and dispatch immediately.\n\n### Step 2 — Compose the prompt\n\nUse the format the upstream model prefers (Seedance: motion + camera +\nmood; Kling: subject + camera + style; Veo: subject + cinematography +\nsound). Bind the project's `videoAspect` and `videoLength` directly to\nthe API parameters; never put them in prose.\n\nFor `hyperframes-html`, write a concise motion-design brief instead of a\ncamera-realism prompt. Focus on subject, layout, palette, motion\ncharacter, and overall tone. Do not spend turns narrating environment\nchecks, missing side files, or \"I am about to dispatch\" status updates.\n\n### Step 3 — Dispatch via the media contract\n\nUse the unified dispatcher — do **not** call provider APIs by hand:\n\n```bash\n\"$OD_NODE_BIN\" \"$OD_BIN\" media generate \\\n  --project \"$OD_PROJECT_ID\" \\\n  --surface video \\\n  --model \"\u003CvideoModel from metadata>\" \\\n  --aspect \"\u003CvideoAspect from metadata>\" \\\n  --length \u003CvideoLength seconds> \\\n  --output \"\u003Cshort-slug>-\u003Cseconds>s.mp4\" \\\n  --prompt \"\u003Cassembled shot prompt from Step 2>\"\n```\n\nThe command prints one line of JSON: `{\"file\": {\"name\": \"...\", ...}}`.\nThe bytes land in the project; the FileViewer plays it automatically.\n\n### Step 4 — Hand off\n\nReply with: shot summary, the filename returned by the dispatcher, and\none sentence on what to try if the user wants a variation.\n\nFor `hyperframes-html`, keep the reply especially short: what was\nrendered, the filename, and one concrete variation idea.\n\n## Hard rules\n\n- One shot per turn. Multi-shot timelines belong in a hyperframes \u002F\n  interactive-video skill, not here.\n- Match `videoAspect` exactly — re-renders are slow.\n- Never ship a video without saving the file — the user expects\n  something to play in the file viewer.\n- When the underlying model fails (NSFW filter, content policy,\n  timeout), keep the raw provider error in the tool trace and give the\n  user the media contract's `nextStep` sentence for that outcome. Never\n  paste upstream error text into the reply. Don't silently retry.\n- Do not claim a render has been \"sent\", \"started\", or \"is running\"\n  unless you have already called `\"$OD_NODE_BIN\" \"$OD_BIN\" media generate`.\n","# Video Shortform Skill\n\nShort-form (≤ 10s) is the sweet spot for current text-to-video models —\nthey're great at one **shot** with one **idea**, weaker at multi-cut\nnarratives. Plan one shot per call.\n\nSpecial case: `hyperframes-html` is **not** a photoreal text-to-video\nmodel. It's a local HTML-to-MP4 renderer. For that model, do not roleplay\ncinematography or \"real-world\" camera physics. Treat the brief as a motion\ndesign card \u002F title-frame \u002F product interstitial, ask at most one\nclarifying question, then dispatch immediately.\n\n## Resource map\n\n```\nvideo-shortform\u002F\n├── SKILL.md\n└── example.html\n```\n\n## Workflow\n\n### Step 0 — Read the project metadata\n\n`videoModel`, `videoLength` (seconds), `videoAspect`. These are\nhard-locks — clamp the prompt to whatever the chosen model supports\n(Seedance 2 caps at 10s; Kling 4 supports up to 10s + image-to-video;\nVeo 3 supports 8s with audio).\n\n### Step 1 — Plan the shot\n\nWrite the shotlist BEFORE calling the model:\n\n| Slot | Content |\n|---|---|\n| Subject | What's in frame? |\n| Camera | Static \u002F pan \u002F push-in \u002F orbit? |\n| Lighting | Key direction + temperature |\n| Motion | What moves, at what pace? Subject motion vs camera motion. |\n| Sound | Ambient bed? (only if the model supports audio) |\n\nNormally, show this to the user as a one-sentence plan before\ndispatching — they can redirect cheaply.\n\nFor `hyperframes-html`, skip the extra pre-dispatch narration once the\nuser has answered the discovery form. Collapse the plan into the actual\ngeneration prompt and dispatch immediately.\n\n### Step 2 — Compose the prompt\n\nUse the format the upstream model prefers (Seedance: motion + camera +\nmood; Kling: subject + camera + style; Veo: subject + cinematography +\nsound). Bind the project's `videoAspect` and `videoLength` directly to\nthe API parameters; never put them in prose.\n\nFor `hyperframes-html`, write a concise motion-design brief instead of a\ncamera-realism prompt. Focus on subject, layout, palette, motion\ncharacter, and overall tone. Do not spend turns narrating environment\nchecks, missing side files, or \"I am about to dispatch\" status updates.\n\n### Step 3 — Dispatch via the media contract\n\nUse the unified dispatcher — do **not** call provider APIs by hand:\n\n```bash\n\"$OD_NODE_BIN\" \"$OD_BIN\" media generate \\\n  --project \"$OD_PROJECT_ID\" \\\n  --surface video \\\n  --model \"\u003CvideoModel from metadata>\" \\\n  --aspect \"\u003CvideoAspect from metadata>\" \\\n  --length \u003CvideoLength seconds> \\\n  --output \"\u003Cshort-slug>-\u003Cseconds>s.mp4\" \\\n  --prompt \"\u003Cassembled shot prompt from Step 2>\"\n```\n\nThe command prints one line of JSON: `{\"file\": {\"name\": \"...\", ...}}`.\nThe bytes land in the project; the FileViewer plays it automatically.\n\n### Step 4 — Hand off\n\nReply with: shot summary, the filename returned by the dispatcher, and\none sentence on what to try if the user wants a variation.\n\nFor `hyperframes-html`, keep the reply especially short: what was\nrendered, the filename, and one concrete variation idea.\n\n## Hard rules\n\n- One shot per turn. Multi-shot timelines belong in a hyperframes \u002F\n  interactive-video skill, not here.\n- Match `videoAspect` exactly — re-renders are slow.\n- Never ship a video without saving the file — the user expects\n  something to play in the file viewer.\n- When the underlying model fails (NSFW filter, content policy,\n  timeout), keep the raw provider error in the tool trace and give the\n  user the media contract's `nextStep` sentence for that outcome. Never\n  paste upstream error text into the reply. Don't silently retry.\n- Do not claim a render has been \"sent\", \"started\", or \"is running\"\n  unless you have already called `\"$OD_NODE_BIN\" \"$OD_BIN\" media generate`.\n",{"od":23,"name":5,"triggers":31,"description":37},{"mode":24,"preview":25,"surface":24,"scenario":28,"design_system":29,"example_prompt":30},"video",{"type":26,"entry":27},"html","example.html","marketing",{"requires":19},"5-second product reveal — ceramic coffee mug rotating on a soft\npaper backdrop, warm side-light from camera-left, micro dust motes\ndrifting through the beam. Cinematic, 16:9, slow drift on the camera.",[24,32,33,34,35,36],"clip","shortform","reel","短视频","动效","Short-form video generation skill — 3-10 second clips for product\nreveals, motion teasers, ambient loops. Defaults to Seedance 2 but\nworks the same with Kling 3 \u002F 4, Veo 3 or Sora 2. Output is one MP4\nsaved to the project folder. When the workspace also ships an\ninteractive-video \u002F hyperframes skill, prefer composing several short\nshots into a single timeline rather than one long monolithic clip.\n","main","3a6721b94dec7506e324023f2855495c9c54d0d2","design-templates\u002Fvideo-shortform",0,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fandremolnar","2026-10-30 01:33:11",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add andremolnar\u002Fopen-open-design --skill video-shortform",{"tool":52,"command":53},"bunx","bunx skills add andremolnar\u002Fopen-open-design --skill video-shortform",{"tool":55,"command":56},"pnpm","pnpm dlx skills add andremolnar\u002Fopen-open-design --skill video-shortform","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fvideo-shortform\u002FSKILL.md",true,[60],{"path":27,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"REFERENCE","参考文档",3560,"https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fdesign-templates\u002Fvideo-shortform\u002Fexample.html",[66,73,80,87,94,103],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7DMPDFNBD52ZP0GNY046Z2A","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7DMPC4JJ8ENX7VWTMP38Y9C","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7DMP9J5BX307VWVD67J0BBM","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7DMP7GNYTFXGK9RDZ2X723P","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7DMP2WHMNKM0P5BXRYAG8D1","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7DMP0GVJQ37CGXYQDD20VWS","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fandremolnar\u002Fopen-open-design\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]