scenario-seedance-music-video
Use when turning a song, track, or audio master into a finished music video with Scenario and Seedance: planning shots against beats and sections, transcribing lyrics, generating clips that cut to music, keeping the shots' own sound while the song stays the only score, assembling a delivery over theβ¦
Install / Use
npx skills add scenario-labs/skills --skill scenario-seedance-music-videoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Tags
Our assessment of scenario-seedance-music-video
scenario-seedance-music-video scores 86/100 on our quality scale, 176th of 330 Other skills we index.
Its SKILL.md is 7.3 KB long, split into 6 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-seedance-music-video is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
scenario-seedance-music-video compared with similar skills
All 4 of these similar skills score higher than scenario-seedance-music-video; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-seedance-music-video (this skill)by scenario-labs | 86 | 1.0k | 29d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-seedance-music-video?
- Run
npx skills add scenario-labs/skills --skill scenario-seedance-music-video. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-seedance-music-video work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-seedance-music-video safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-seedance-music-video still maintained?
- The repository was last updated 29 days ago, so scenario-seedance-music-video is actively maintained.
Skill content
View source on GitHubname: scenario-seedance-music-video description: "Use when turning a song, track, or audio master into a finished music video with Scenario and Seedance: planning shots against beats and sections, transcribing lyrics, generating clips that cut to music, keeping the shots' own sound while the song stays the only score, assembling a delivery over the untouched master soundtrack, or verifying the final cut. Keywords: music video, beat sync, shot list, lyric transcription, reference frames, ffmpeg assembly, Seedance." license: MIT
Scenario Seedance Music Video
Overview
Five steps: song, lyrics, story, frames, video. The supplied master is the only score, and no shot writes its own. scripts/build.py lays the master over the cut once, at the end, and proves the file untouched by hash. scripts/song.py reads the master so cuts land on its structure. The scripts need ffmpeg and ffprobe on PATH, and numpy for song.py.
Connection and the core generation loop: see the scenario skill in this repo. The Seedance
parameter contract and conditioning traps: see the scenario-seedance skill. If a sibling skill
named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the
user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool
schemas and flag the gap.
The two soundtracks
Music written inside a shot restarts in a new key at every cut, so the score comes from outside the
video model: the supplied master. What Seedance makes is the sound bolted to the picture. The choice
sets generateAudio on every shot, so make it before generating:
- Song alone:
generateAudio: falseeverywhere. build.py stream-copies the master whenever MP4 allows, so the delivered soundtrack is the supplied file, bit for bit. - Song over the shots' own sound:
generateAudio: true, every prompt naming the sound the scene itself makes (heels on wet asphalt, room tone) after "diegetic sound only:" and nothing else, plus"sound": 0.2in the edit file. Name no instrument or genre, however well it fits the track, and no exclusion such as "no music": an instrument invites a score, one run failed on an output-audio content check for an added "distant guitar", and the exclusion has failed that check too. build.py cuts each clip's audio to its slot, mixes it under the master at that gain, and refuses a mix that would clip. The delivery is then one AAC encode, trading the bit-for-bit guarantee for the sound; the master file stays hash-checked.
Quick reference
| Step | Call | Notes |
| --------- | ------------------------------------------------- | ----------------------------------------------------------------- |
| 1. Song | python3 scripts/song.py master.mp3 -o song.json | hash, duration, loudness, tempo, sections, cut candidates |
| 2. Lyrics | recommend for transcription, model_run | supplied lyrics win; sung-vocal transcription is a draft |
| 3. Story | one page, shown to the user first | the cheapest place to be wrong; name what must not drift |
| 4. Frames | image model at the delivery aspect ratio | reference stills, one per look to hold |
| 5. Shots | Seedance model_run, audio per the choice above | dry_run first; wait=false; jobs_wait with pending_job_ids |
| 6. Cut | python3 scripts/build.py edit.json out.mp4 | one ffmpeg pass: conform, concatenate, lay the master, verify |
Ask once before starting: team and project, track clearance, aspect ratio and length, sound under the song or not, what must and must not appear, spend ceiling. With no one to answer, take the song alone, and write the story down rather than waiting to show it. Then run without stopping.
Worked example: one verse, three shots
python3 scripts/song.py master.mp3 -o song.json. Sections are shot boundaries, cut candidates are cut points; listen before trusting them.- Upload the master: multipart
upload_asset, thenupload_asset_complete(see thescenarioskill).recommenda transcription model (the need in the user's own words asprompt),model_schema_get,model_run,jobs_wait. The transcript is a text asset among the job's asset ids:asset_getreturns it whole inmetadata.previewwhenhasFullPreviewis true (at authoring time the Whisper-based tool wrote SRT-style timed blocks), elseasset_downloadfetches the file. Instrumental track: say so and move on. - Write one page: what happens, where, how it turns across the sections; name the closing image. Show it to the user before spending anything.
- Generate reference stills with an image model (via
recommend) at the delivery aspect ratio, one per look. Look at them: they set identity and palette downstream. Holding one character across several: see thescenario-consistencyskill. - Per shot, decide the conditioning: opening state matters, pass a first-frame
image; only identity and world matter, passreferenceImages(see references/shots.md). Generate each shot one or two seconds longer than its slot for a trim handle. To land an action on a beat inside a shot, timecode it from the clip's start: the beat's master time minus the shot'sat, plus any head trim planned asin(an unplanned trim moves every beat). Hold one camera move and one location across the timecodes; timecoded verbs survive generation where mood words do not. - Write
edit.jsonand runpython3 scripts/build.py edit.json out.mp4:
{
"master": "master.mp3",
"fps": 24,
"width": 1280,
"height": 720,
"sound": 0.2,
"shots": [
{ "clip": "clips/01.mp4", "at": 0.0 },
{ "clip": "clips/02.mp4", "at": 12.5, "in": 1.0 }
]
}
Each shot runs until the next starts and the last to the master's end, so gaps are impossible, and
every at snaps to the nearest frame. in is an optional head trim. sound is the gain on the
clips' own audio: 0.1 to 0.3 under a mastered track, up to 1.0 when the clips run quiet (build.py
takes 0 to 4); drop the line for the song alone. The build fails loudly on a clip too short, a mix
that would clip, or delivered audio that is not the master.
Common mistakes
- Letting a shot score itself: its score restarts at every cut.
- Turning
soundon before listening to every clip:generateAudiois one switch over the whole track, so a clip that leaked music goes back withgenerateAudio: falserather than an exclusion in words. - Trimming, normalizing, fading, or re-encoding the master yourself: build.py copies it or carries it at unity, and hash-checks the file either way.
- Trusting a requested aspect ratio: stills and clips land near it, not on it, and build.py pads the difference; crop to the delivery ratio first.
- Prompting an opening state in reference mode: it will not appear; pass a first-frame
image. - Judging a clip from a sparse contact sheet: a continuous camera move looks like a hard cut; measure first (see references/shots.md).
- Trusting the beat grid: sections and cut candidates are suggestions; check them against what you hear.
- Calling it done without watching the delivery with sound, then muted.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 β pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way β as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an emβ¦
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVGβ¦
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
