Video Shortform
Short-form video generation skill — 3-10 second clips for product reveals, motion teasers, ambient loops. Defaults to Seedance 2 but works the same with Kling 3 / 4, Veo 3 or Sora 2. Output is one MP4 saved to the project folder. When the workspace also ships an interactive-video / hyperframes skill, prefer composing several short shots into a single timeline rather than one long monolithic clip.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Video Shortform when an AI agent needs a reusable SKILL.md workflow for this job: Short-form video generation skill — 3-10 second clips for product reveals, motion teasers, ambient loops. Defaults to Seedance 2 but works the same with Kling 3 / 4, Veo 3 or Sora 2. Output is one MP4 saved to the project folder. When the workspace also ships an interactive-video / hyperframes skill, prefer composing several short shots into a single timeline rather than one long monolithic clip.
When not to use it
Skip Video Shortform when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/video-shortform # Save SKILL.md to ~/.claude/skills/video-shortform/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/video-shortform/SKILL.md. For a shared project, commit the folder at .claude/skills/video-shortform/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Video Shortform skill for this task: Use Video Shortform when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Video Shortform Skill
Short-form (≤ 10s) is the sweet spot for current text-to-video models — they're great at one **shot** with one **idea**, weaker at multi-cut narratives. Plan one shot per call.
Special case: `hyperframes-html` is **not** a photoreal text-to-video model. It's a local HTML-to-MP4 renderer. For that model, do not roleplay cinematography or "real-world" camera physics. Treat the brief as a motion design card / title-frame / product interstitial, ask at most one clarifying question, then dispatch immediately.
## Resource map
``` video-shortform/ ├── SKILL.md └── example.html ```
## Workflow
### Step 0 — Read the project metadata
`videoModel`, `videoLength` (seconds), `videoAspect`. These are hard-locks — clamp the prompt to whatever the chosen model supports (Seedance 2 caps at 10s; Kling 4 supports up to 10s + image-to-video; Veo 3 supports 8s with audio).
### Step 1 — Plan the shot
Write the shotlist BEFORE calling the model:
| Slot | Content | |---|---| | Subject | What's in frame? | | Camera | Static / pan / push-in / orbit? | | Lighting | Key direction + temperature | | Motion | What moves, at what pace? Subject motion vs camera motion. | | Sound | Ambient bed? (only if the model supports audio) |
Normally, show this to the user as a one-sentence plan before dispatching — they can redirect cheaply.
For `hyperframes-html`, skip the extra pre-dispatch narration once the user has answered the discovery form. Collapse the plan into the actual generation prompt and dispatch immediately.
### Step 2 — Compose the prompt
Use the format the upstream model prefers (Seedance: motion + camera + mood; Kling: subject + camera + style; Veo: subject + cinematography + sound). Bind the project's `videoAspect` and `videoLength` directly to the API parameters; never put them in prose.
For `hyperframes-html`, write a concise motion-design brief instead of a camera-realism prompt. Focus on subject, layout, palette, motion character, and overall tone. Do not spend turns narrating environment checks, missing side files, or "I am about to dispatch" status updates.
### Step 3 — Dispatch via the media contract
Use the unified dispatcher — do **not** call provider APIs by hand:
```bash "$OD_NODE_BIN" "$OD_BIN" media generate \ --project "$OD_PROJECT_ID" \ --surface video \ --model "<videoModel from metadata>" \ --aspect "<videoAspect from metadata>" \ --length <videoLength seconds> \ --output "<short-slug>-<seconds>s.mp4" \ --prompt "<assembled shot prompt from Step 2>" ```
The command prints one line of JSON: `{"file": {"name": "...", ...}}`. The bytes land in the project; the FileViewer plays it automatically.
### Step 4 — Hand off
Reply with: shot summary, the filename returned by the dispatcher, and one sentence on what to try if the user wants a variation.
For `hyperframes-html`, keep the reply especially short: what was rendered, the filename, and one concrete variation idea.
## Hard rules
- One shot per turn. Multi-shot timelines belong in a hyperframes / interactive-video skill, not here. - Match `videoAspect` exactly — re-renders are slow. - Never ship a video without saving the file — the user expects something to play in the file viewer. - When the underlying model fails (NSFW filter, content policy, timeout), keep the raw provider error in the tool trace and give the user the media contract's `nextStep` sentence for that outcome. Never paste upstream error text into the reply. Don't silently retry. - Do not claim a render has been "sent", "started", or "is running" unless you have already called `"$OD_NODE_BIN" "$OD_BIN" media generate`.
Intended uses
- Use Video Shortform when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.