scenario-kinetic-music-video
Use when turning a song into a kinetic-typography or motion-design music video, lyric video, visualizer or K-pop style MV with Scenario, landscape or vertical 9:16 for TikTok, Reels and Shorts: a generated subject sheet, style frames and footage, plus a deterministic JavaScript/three.js engine for l…
Install / Use
npx skills add scenario-labs/skills --skill scenario-kinetic-music-videoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Our assessment of scenario-kinetic-music-video
scenario-kinetic-music-video scores 86/100 on our quality scale, 175th of 330 Other skills we index.
Its SKILL.md is 18 KB long, well organised into 13 sections and no code examples: 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-kinetic-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-kinetic-music-video compared with similar skills
All 4 of these similar skills score higher than scenario-kinetic-music-video; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-kinetic-music-video (this skill)by scenario-labs | 86 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-kinetic-music-video?
- Run
npx skills add scenario-labs/skills --skill scenario-kinetic-music-video. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-kinetic-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-kinetic-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-kinetic-music-video still maintained?
- The repository was last updated 29 days ago, so scenario-kinetic-music-video is actively maintained.
Skill content
View source on GitHubname: scenario-kinetic-music-video description: "Use when turning a song into a kinetic-typography or motion-design music video, lyric video, visualizer or K-pop style MV with Scenario, landscape or vertical 9:16 for TikTok, Reels and Shorts: a generated subject sheet, style frames and footage, plus a deterministic JavaScript/three.js engine for lyric type, mattes and tracked graphics timed to sung onsets. Also for revising, recutting or cutting teasers from such a video. Not for a brief-led launch film (scenario-kinetic-film)." license: MIT
Kinetic Music Video
A song goes in. A 1080p60 music video comes out, landscape for YouTube and X or vertical for TikTok, Reels and Shorts: a motion designer's showreel cut to the track. Kinetic type, 2D and 3D graphics and transitions land on the beats and sung syllables. Generated footage of the subject is woven through it where the concept wants a performer. The approved master is the only soundtrack. Preserve the original; an authorized audio edit produces a new, versioned master.
The work splits by what each tool does best:
- Scenario supplies what code can't: a consistent subject with real physics, choreography, hair and lip-sync, in whatever art style each section needs.
- The JS engine supplies what video models can't: exact typography, frame-exact timing to onsets and beats, infographics, compositing around the subject, and endless re-renders at zero generation cost.
- Sub-agents give each section a dedicated designer. A shared style bible and a verification loop keep them coherent.
Connection and the core generation loop: see the scenario skill in this repo. For a song-to-video
cut without the engine, see scenario-seedance-music-video. 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.
Read references/lessons.md before starting. Every item in it cost real time or money once.
references/motion_library.md is the design menu.
Before you start (ask once, then run)
- Workspace: the Scenario team and project (
teams_list; ask if there is more than one). - Subject:
- Who or what performs: a character from reference images, a mascot, a product, the artist's own likeness (their own photos and consent only), or nobody (a pure motion-graphics or lyric video).
- Footage share: performer-led, a mix (often about 60/40), or graphics only.
- Look:
- Ask for references: images, videos or links for the mood, the motion and the color. Vague color asks without references drift to safe palettes.
- Decide the 2-4 looks and which sections own which.
- Ask what must never appear.
- Defaults: generated footage shown clean (no filters on it), graphics layered on and around it, a fast and upbeat showreel energy.
- Brand: any logo, wordmark or credit. Use official files in their official colors, only where the director wants them.
- Budget: lean (6-10 video generations), moderate (12-20) or big. Price each paid step with
dry_run(one run per distinct payload, then total) before spending. Relative anchors at 720p: a 6 s clip costs about twenty style frames, a 10 s clip about thirty-five, and a full mixed video about five hundred. A 1080p clip measured about 2.5 times its 720p price, so settle the footage resolution before quoting. - Format: one canvas per project, asked once: portrait 9:16 for TikTok, Reels or Shorts,
landscape 16:9 for YouTube or X (unattended with no destination: landscape). It is
CANVASinengine/timeline.js, and style frames and footage are generated at that ratio, never cropped from the other. On portrait, check the destination's current length cap and plan the teaser as the platform cut when the song runs longer, or when you cannot check. Both ratios only on request: the code re-renders free with--canvasand most shots are windowed, but each shot that must fill the second frame (hook, lip-sync close-ups, finale) is paid again (references/pipeline.md§9). X caps standard accounts at 2:20, so plan a teaser. - Lyrics: use them if supplied (they beat any transcript). Otherwise transcribe and flag the uncertain words at the end.
With no one around to answer, choose sensible defaults for the creative choices and write them into TREATMENT.md. Do not default the money: with no stated budget or no explicit team and project, stop before the first paid step and say what is missing.
Workflow
1. Scaffold and analyze the song
Run bash <skill>/scripts/scaffold.sh <song> inside a new project folder (macOS on Apple Silicon or
Linux x86_64 with glibc 2.28+: the Python lock covers those two), then follow
references/pipeline.md §2:
audio_analysis.pywrites stems andengine/data/audio.json: beats, downbeats, kick/snare/vocal onsets, and 60 fps envelopes. Measure the tempo; labels lie (a "130 BPM" song was 98 with double-time drums).lyrics_align.py transcribe, then hand-correctanalysis/lyrics.txt, thenlyrics_align.py alignwritesengine/data/lyrics.jsonwith word onsets.- Check timing by eye with
plot_lyrics.py. Audition when playback is available; a spectrogram locates onsets but cannot prove pronunciation or musical continuity.
1a. Edit the soundtrack when requested
For pronunciation repairs, lyric changes, section replacements or structural cuts, read
references/audio_editing.md. Use scenario-ace-step for its
Cover/Repaint contracts. Keep the current cut and master until a candidate is selected; preserve
audio outside the agreed window and rebuild affected timing data after applying it. A picture-only
revision reuses the approved soundtrack.
2. Research (parallel, background)
Launch two sub-agents with web access while you work on other things:
- Culture: for the song's subject, find recognizable events, memes and visual tropes, each with a verified fact, its iconic visual form, an insert idea and a short on-screen string.
- Craft: study the user's motion references (download them, contact-sheet them, read the
frames), plus genre direction techniques. Extract timing numbers, color hex values and
implementable JS moves. Measure each reference per section into
analysis/targets.json(references/dynamism.md §5).
Save the condensed results as analysis/research_*.md. Scene agents read them alongside
references/motion_library.md.
3. Concept, style bible and treatment
- Give the video a spine. The strongest concepts make the edit itself carry the song's meaning: a device that progresses through the whole video, for example a counter, clock or countdown that moves with the song while the cut rate or the looks escalate with it. The spine usually lives in the HUD counters.
- STYLE.md (the law):
- a one-line concept and the spine
- the footage rules (clean plate and the back/mid/front layers, or another policy)
- the looks, each with ground, ink, accent, rendering rule and matching footage style
- the palette with roles
- 4-5 type roles with named fonts
- lyric display rules
- a motion grammar mapping beats to effects, with the cut density per section
- the subject (identity, design details usable as graphic motifs)
- brand rules, references and bans
- TREATMENT.md:
- song facts and the energy map
- the arc
- the hook for the first 3 seconds (the strongest idea in the video, and it must work as a muted autoplay)
- one row per section: time range on downbeats, lyrics, look, must-have ideas
- a footage map (filled in as clips land)
- PLAN.md: a one-page version for the director to approve before you spend on footage (unattended, this is the stop point if the budget is unstated).
4. Subject, style frames and footage on Scenario
Skip this for a graphics-only video, apart from any stills or 3D props. Otherwise follow
references/pipeline.md §3-5:
- Subject sheet: a turnaround, expressions and callouts from the user's references. Look at it, then crop identity references from it.
- Style frames: one still per shot at the canvas ratio (an image model that takes reference images), in its section's look. Compose with negative space for type (on portrait, the face and the type space inside the safe band), on a set that composites (black void with rim light, flat color cyc, or white high-key). No text. In a lip-sync frame nothing covers the mouth (no mic, hand or prop): a covered mouth fails the sync check and is paid again. Contact-sheet them and get the look approved cheaply (unattended: proceed only inside a stated budget).
- Footage routes:
- Image-to-video from the frame for actions.
- A video model with reference images and reference audio, given a synthesized beat track for dances that lock to the song, then beat-warp.
- Audio-to-video from a frame plus a vocal-stem slice for lip-sync. The alternative is reference-audio video plus a lip-sync correction model.
- Code instead of generation for networks, charts, UI and particles.
- Never send the song to a video model. Turn the model's native audio off when its schema offers it
(the render takes sound only from the master either way), and launch in waves within the team's
concurrency ceiling (
jobs_waitre-called withpending_job_ids, neverjob_get). Relaunch only a launch refused with 429parallel-custom-jobs: it created no job, and dropping it leaves a hole in the cut. - Prep every clip with
tools/prep_clip.sh: frames, a subject matte (Apple Vision, with Scenario background removal as the fallback; seereferences/pipeline.md§5) and tracking (MediaPipe pose plus the matte bbox). Inspect the mattes. Write each clip's content, key moments, slot and matte quality into the footage map.
5. Engine and scene agents
- Smoke-test first:
- Set
PALincore.js, and inengine/timeline.jssetCANVAS, the sections on downbeats with theirenergy,HUD(title, mark, section codes, spine counters) andPOST(neutral by default). - Write a tiny
_smoke.js: plate → type behind the subject → matte → tracked label. - Render one still and a 5 s clip, then confirm audio and flashes line up with
av_sync_check.py.
- Set
- Brief the agents. Fill in
AGENTS_BRIEF.mdfrom the template, then launch one background agent per section in a single message. Each gets its file, time range, lyrics, must-have ideas and clips, and reads AGENTS_BRIEF, STYLE, TREATMENT, ENGINE_API and the research first. Log the agent ids. For a teaser or anything under about 30 s, the lead may write the scenes itself and skip the research agents, PLAN.md and the per-section agents; keep the smoke test. - Deliver clips as they land. Message the agent that needs each one ("clip ready: content, key moments, slot").
- Review every report. Contact-sheet the best stills and Read them. Fix engine-level problems yourself (they affect everyone) and tell the agents what changed.
6. Assemble, watch, iterate
- Render the full cut (3 workers, about 5 min for 2:00 on an M-series Mac, 2.5 times that with
motion blur). Wait for it in the foreground (or poll until it prints
wrote), then verify and deliver: never end the run mid-render or mid-encode, since a headless session that stops kills it. - Verify:
av_sync_check.py: expect 0.0 ms audio and 0 to +1 frame visual. Below a correlation of about 0.15 the visual lag means nothing (type leading byE.LEADreads as up to -3 frames): check onset stills instead.dynamism_check.py gateon each delivered render: exit 0. On exit 1, fix and re-gate (--forcereplaces its JSON); unattended, after 3 rounds on a section or at
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
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.
