Turns user intent into model-specific prompts for text-to-video and image-to-video generation across seven models (Ovi, Sora, Veo 3, Wan 2.2, Seedance 2.0, LTX-2, LTX-2.3), plus character sheet prompts for image models when you need consistent characters across shots. Routes requests, asks minimal clarifying questions, then follows strict per-model formatting rules stored in reference files. Handles the full workflow from character turnaround to scene still to i2v prompt if you're building a sequence. Strips out metadata like duration and aspect ratio from the prompt text itself, since those live in API parameters. Useful if you're working with multiple video models and tired of remembering which one wants camera movement first versus action beats, or how to structure dialogue differently for each.
npx -y skills add square-zero-labs/video-prompting-skill --skill video-prompting --agent claude-codeInstalls into .claude/skills of the current project.
Turn a user’s intent into either:
Model-specific video guidance lives in references/models/. Character-sheet guidance lives in references/workflows/character-sheets.md.
This file is the entry point: route to the right path, ask the minimum clarifying questions, then draft the prompt in the expected format.
references/models/ovi/prompting.mdreferences/models/sora/prompting.mdreferences/models/veo3/prompting.mdreferences/models/wan22/prompting.mdreferences/models/seedance2/prompting.mdreferences/models/ltx2/prompting.mdreferences/models/ltx2-3/prompting.mdreferences/workflows/character-sheets.mdTo add a new model later: create references/models/<model>/prompting.md, then add it to this index.
To add a new workflow later: create references/workflows/<workflow>.md, then add it to the Workflow Index.
These rules apply to every video model reference:
Decide whether the user wants:
Route to the character-sheet workflow when the user wants a reusable reference sheet, turnaround, expression sheet, costume sheet, photographic identity sheet, or a consistent-character starting point for a longer image-to-video project.
If the user is asking for both, do them in this order:
If the user did not name a model, ask which model they are using (or offer supported options from the Model Index).
Then confirm the input mode:
If i2v: ask the user to share the image (optional, but it will help you generate a better prompt). Use the image as an anchor according to the chosen model’s guidance (e.g., keep identity/wardrobe/composition stable; focus your text on motion/camera/what changes).
If the chosen model has versions, duration constraints, or required parameters, ask the minimum questions needed to select the right format (see the model guide). For LTX-2.3 specifically: default to 10 seconds as the external duration setting when duration is missing, ask if the user wants shorter or longer, and scale motion complexity to match that duration. Do not write the duration into the prompt itself.
For video prompts: open the model’s prompting.md from the Model Index and follow its rules strictly.
For character sheets: open references/workflows/character-sheets.md and follow its structure strictly. Treat this as an image-model prompt, not a video-model prompt.
Draft the prompt using the structure and constraints from the markdown file you selected in Step 3.
For video prompts: follow the chosen model’s prompting.md exactly, including its preferred section order, dialogue/audio format, and any shot-structure guidance.
Before returning a video prompt, remove any prompt-internal references to model name/version, clip length, aspect ratio, resolution, or generation settings.
For character sheets: follow references/workflows/character-sheets.md exactly, including layout, consistency constraints, and expression-row guidance.
Default: output only the final prompt text. Default formatting: output prompts as a single line with no line breaks unless the user explicitly requests multiline formatting.
If the user asks for options: provide 2–3 distinct prompt variants, each fully self-contained and compliant with the model’s formatting.
If the model uses required API parameters (e.g., duration/size), include a short “Recommended parameters” line only when the user has specified them or explicitly asks for them.
If the user wants the full consistency workflow, after the character-sheet prompt also provide:
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills