video-prompt-builder
Skill0 starsChanged 4 months agoMITView on GitHub
Generate detailed, shot-by-shot AI video prompts for Seedance 2.0 from a creative brief. Use this skill whenever the user wants to create a video prompt, write a shot list, plan a video sequence, describe a video concept for AI generation, or mentions Seedance. Also trigger when the user describes a scene, ad concept, brand film, product video, or any visual sequence they want turned into structured prompts — even if they don't explicitly say "video prompt." Trigger on phrases like "write me a video prompt", "Seedance prompt", "shot list", "plan a video", "video concept", "create a sequence", "brand film prompt", "ad prompt", or any time the user describes what they want to happen in a video and needs it translated into generation-ready prompts.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- avenoxai/higgsfield-studiotheir own version, first seen Aug 19, 2026
- BH2-4/video-prompt-buildertheir own version, first seen Aug 6, 2026
- davekindl/skillsedited, first seen Jul 23, 2026
- monkroe/claude-skillsword for word, first seen Jun 18, 2026
Other versions4 projects use a version of this.
Word for word · 1
- monkroe/claude-skills★ 0100% same
Edited · 1
- davekindl/skills★ 297% same
Wrote their own version · 2
- avenoxai/higgsfield-studio★ 9same name
- BH2-4/video-prompt-builder★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository52 other files it gives its agents.
- skills/composition-patterns/AGENTS.mdAGENTS.md
- sample-project/CLAUDE.mdCLAUDE.md
- agent-orchestratorSkill
- api-designSkill
- banner-designSkill
- brainstormingSkill
- brandSkill
- capital-accountsSkill
- composition-patternsSkill
- continuous-learning-v2Skill
- contract-reviewSkill
- credential-scannerSkill
- deployment-patternsSkill
- design-systemSkill
- dispatching-parallel-agentsSkill
- docker-patternsSkill
- e2e-testingSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- fixed-assetsSkill
- frontend-designSkill
- git-guardrails-claude-codeSkill
- graphifySkill
- huashu-designSkill
- investmentsSkill
- iterative-retrievalSkill
- legal-agreementSkill
- plain-english-translationSkill
- terms-of-service-generatorSkill
- pdfSkill
- prd-to-issuesSkill
- prd-to-planSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- security-reviewSkill
- shapeSkill
- slidesSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- triage-issueSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- webapp-testingSkill
- web-design-guidelinesSkill
- write-a-prdSkill
- writing-plansSkill
- writing-skillsSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read the reference file at references/effects-breakdown-reference.txt to internalise the structure and level of detail expected.
- Distinctive: line 28
If the brief is too vague to build a full prompt (e.g.
- Distinctive: line 32
ALWAYS output ALL FOUR sections in this exact order.
- Distinctive: line 52
Use language Seedance 2.0 can interpret: describe the visual result, not the editing software technique.
- Distinctive: line 93
Signature moments matter: Every video should have at least one "hero" effect — something visually distinctive that makes it memorable.
- Distinctive: line 94
Transitions are shots: Don't treat transitions as throwaway connectors.
- Distinctive: line 96
Energy must resolve: No matter how intense the opening, the video needs to land.
- Distinctive: line 100
Write in a direct, technical tone — like a director's shot notes, not a marketing brief
- Distinctive: line 101
Use bullet points within each shot block for clarity
- Distinctive: line 103
No hype language, no "stunning" or "breathtaking" — describe what happens and let the visuals speak
- Distinctive: line 113
If the user doesn't specify a duration, default to 15-20 seconds (a sweet spot for AI video generation).
- Very specific: line 120
Read references/effects-breakdown-reference.txt to calibrate detail level
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video Prompt Builder for Seedance 2.0
Build cinematic, shot-by-shot video prompts from a creative brief. Every output follows a structured effects breakdown format designed to give Seedance 2.0 maximum detail on camera work, effects, transitions, pacing, and energy arc.
How this skill works
- The user provides a creative brief — this can be as simple as "a runner in a stadium for a Nike-style ad" or as detailed as a full storyboard description. They may also provide a reference video, mood, brand context, or specific effects they want.
- Read the reference file at
references/effects-breakdown-reference.txtto internalise the structure and level of detail expected. - Generate a complete video prompt in plain text, structured into the four mandatory sections below.
Input expectations
The user's brief can include any combination of:
- Subject/talent description (who or what is on screen)
- Setting/environment
- Mood, tone, energy level
- Brand or product context
- Specific effects or camera moves they want
- Duration target
- Reference to existing ads, films, or visual styles
- Colour palette or grade preferences
If the brief is too vague to build a full prompt (e.g. "make something cool"), ask one focused clarifying question before proceeding. Don't over-interrogate — work with what you're given and make creative decisions where the user hasn't specified.
Output structure
ALWAYS output ALL FOUR sections in this exact order. Never skip a section.
Section 1: SHOT-BY-SHOT EFFECTS TIMELINE
This is the core of the prompt. Each shot gets its own block structured like this:
SHOT [N] ([timestamp]) — [Shot Name / Description]
• EFFECT: [Primary effect name] + [secondary effects if stacked]
• [Detailed description of what's happening visually]
• [Camera behaviour — angle, movement, lens if relevant]
• [Speed/timing information]
• [How this shot connects to the next — transition type]Guidelines for writing shots:
- Each shot should be 1-4 seconds unless the brief calls for longer holds
- Name effects precisely: "speed ramp (deceleration)" not just "speed ramp"; "digital zoom (scale-in)" not just "zoom"
- Describe stacked effects explicitly — if 3 things happen at once, list all 3
- Include transition logic: how does this shot EXIT and how does the next shot ENTER?
- Use language Seedance 2.0 can interpret: describe the visual result, not the editing software technique. For example, say "the frame scales inward rapidly" rather than "apply a keyframed scale effect in After Effects"
- Note the most impactful or signature shot with a callout like "This is the SIGNATURE VISUAL EFFECT"
- Be specific about speed percentages when using slow-motion (e.g. "approximately 20-25% speed")
- Describe motion blur, light behaviour, and atmospheric effects where relevant
Section 2: MASTER EFFECTS INVENTORY
A numbered list of every distinct effect used across the full prompt, with:
- Effect name
- How many times it's used (e.g. "used 3x")
- Which shots it appears in
- A one-line description of its role in the edit
This section helps the user (and the generator) see the full palette of techniques at a glance. Group similar effects together. Typical categories include: speed manipulation, camera movement, digital effects, transitions, compositing, optical effects.
Section 3: EFFECTS DENSITY MAP
Break the timeline into segments (roughly 3-6 second chunks) and rate each as:
- HIGH DENSITY — 4+ effects stacked or rapid-fire
- MEDIUM DENSITY — 2-3 effects
- LOW DENSITY — 1 effect or clean/simple footage
Format:
[timestamp range] = [DENSITY LEVEL] ([brief list of effects] — [count] effects in [duration])Section 4: ENERGY ARC
Describe the overall energy structure of the video as a narrative arc. The reference uses a three-act model:
- Act 1: Opening energy — how the video grabs attention
- Act 2: Middle section — how it develops and what the signature moments are
- Act 3: Resolution — how the energy resolves and lands
Adapt the number of acts to suit the video's length and structure. A 5-second clip might only need two beats; a 30-second brand film might need four.
Creative principles
These principles should guide every prompt you write:
- Contrast drives impact. Alternate high-density and low-density moments. A slow-motion shot after a speed ramp hits harder than two speed ramps back-to-back.
- Signature moments matter. Every video should have at least one "hero" effect — something visually distinctive that makes it memorable. Call it out explicitly.
- Transitions are shots. Don't treat transitions as throwaway connectors. A whip pan, a bloom flash, a motion blur smear — these are creative moments, not just cuts.
- Specificity over vagueness. "The frame rotates clockwise by approximately 15-20°" is better than "the camera tilts." "Approximately 20-25% speed" is better than "slow motion."
- Energy must resolve. No matter how intense the opening, the video needs to land. The final moments should feel intentional, not like the effects budget ran out.
Tone and style
- Write in a direct, technical tone — like a director's shot notes, not a marketing brief
- Use bullet points within each shot block for clarity
- Be concise but complete — every detail should earn its place
- No hype language, no "stunning" or "breathtaking" — describe what happens and let the visuals speak
Duration calibration
Adjust the number of shots and effects density to match the target duration:
- 5-10 seconds: 4-7 shots, lean and punchy, 1 signature effect
- 10-20 seconds: 8-14 shots, room for contrast and build, 1-2 signature effects
- 20-30 seconds: 12-20 shots, full three-act arc, 2-3 signature effects
- 30+ seconds: Scale accordingly, but maintain density contrast — don't fill every second with effects
If the user doesn't specify a duration, default to 15-20 seconds (a sweet spot for AI video generation).
Example workflow
User says: "I want a dramatic brand film for a trail running shoe. Mountain setting, golden hour, single runner. Make it feel epic but not over-the-top. About 15 seconds."
You do:
- Read
references/effects-breakdown-reference.txtto calibrate detail level - Generate the full four-section output: shot-by-shot timeline (8-12 shots), master effects inventory, density map, and energy arc
- Present in plain text in chat
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

