script-video
Direct a NodeTool video whose timing follows written voiceover, such as a narrated explainer or narrated b-roll: script, voice, and shots timed to the takes. For an explainer's beat structure, pair with explainer-storyboard. For on-camera creators, use ugc-video.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-15
- Stars
- ★ 635
- Forks
- 91
01 前言 Front Matter
- name
- script-video
- description
- Direct a NodeTool video whose timing follows written voiceover, such as a narrated explainer or narrated b-roll: script, voice, and shots timed to the takes. For an explainer's beat structure, pair with explainer-storyboard. For on-camera creators, use ugc-video.
03 SKILL.md 正文
Load /storyboard-core first. It carries the loop, the tool contract and
the gating this skill assumes. This job type inverts the order of that loop, so read
the sequence below before creating a board. For a product explainer, load
/explainer-storyboard as well: it sets the teaching arc and the beats, and this
skill turns their voiceover into a script that times the shots.
What makes this job type its own
Everywhere else the picture comes first and the words ride along. Here the words are the spine: they set the running time, and each shot has to be exactly as long as the line it covers. That is a different tool path — a script resource the storyboard links to — not a storyboard with narration typed into it.
The payoff is that assemble_storyboard_timeline on a linked board cuts words and
picture together: each shot runs as long as the takes it covers, and every voiced line
becomes its own voiceover clip.
The sequence
- Research and write the voiceover. 150–165 words is about 60 seconds. Write it before anything visual exists.
create_script {name}.edit_script {script_id, ops}—{"op": "add_speaker", "name": "Narrator"}, then one{"op": "add_line", "speaker": "Narrator", "text": "..."}per sentence. A line with nospeakerhas no voice to inherit and readsno_voicehowever the cast is set. One sentence per line: a line is the unit that gets a take and times a shot, so a paragraph in one line gives you a shot you cannot cut.- Give the narrator a voice:
find_model(text_to_speech) →{"op": "set_speaker_voice", "target": "Narrator", "provider", "model", "voice"}. Without it every line readsno_voice.voiceis the provider's own voice name (Aoede,alloy), not a model id. derive_storyboard_from_script {script_id, provider, model}— one shot per line, in reading order, each carrying the line ids it covers. Pass a language provider and model for a director pass that writes each shot's visuals over that scaffold; omit both for the bare scaffold.- Rewrite the visuals. The derived shots are a starting point. Go through with
edit_storyboardupdate_shot, giving each anactionthat is concrete b-roll and amotionwith a count. Set the boardstyleandentity_idswithset_board. Confirm the shot count and the models with the user before the first render. - Stills on every shot, reviewed, before any clip.
voice_script_lines {script_id}— defaults to every draft or stale line. Word timings come from a transcription pass (transcribe: trueby default) and ride into the clips as captions.- Clips, then
assemble_storyboard_timeline, thenvalidate_timeline. - Duck the pictures' own sound. Assembly gives every shot clip an audio twin on a
"Shot Audio" track.
edit_timeline→get_state, thenset_clip_paramswithmuted: trueon those clips so the voiceover carries.
Timing
A shot on a linked board takes its length from its lines' takes — that is
duration_source: "audio", the default once linked. Leave it alone. Pin a shot with
duration_source: "manual" plus duration_seconds only when it must hold past its
narration, such as a final card.
Voice before you cut. A line with no take leaves its shot on its own duration, and the assembly lists it as skipped.
Style registers
Put one in the board style, and say no on-screen type — titles belong on the
timeline as text clips, where they stay editable.
| Register | style |
|---|---|
| Flat 2D | flat vector illustration, three-colour palette, thick uniform strokes, white ground |
| Documentary macro | macro photography, shallow depth, natural light, matte film grade |
| Dark UI | dark interface on a black ground, single accent colour, crisp type-free panels |
| Paper-craft | cut-paper layers, soft drop shadows, warm raking light |
Music
edit_storyboard → {op: "set_board", music_prompt: "..."} sets the score direction,
headless, and assembly turns it into a draft music clip under the voiceover. For a bed
you generate yourself instead: generate_music, then edit_timeline → add_track +
add_media_clip, with its volumeDb low enough to sit under the voiceover.
Brief
Adapt these examples to the user's brief. Example deliverables, style choices, and approval checkpoints apply only when the user adopts them.
Research [TOPIC], then direct a faceless 16:9 explainer. No on-camera talent.
Write the voiceover first, 150-165 words, one sentence per line, as a script:
create_script, then edit_script to add a Narrator speaker and the lines, each
line with speaker Narrator. Give the narrator a voice with set_speaker_voice
before anything else.
Then derive_storyboard_from_script with a director pass, and rewrite each of the
eight shots' action and motion as concrete b-roll to that voiceover.
Board style: [flat 2D / documentary macro / dark UI / paper-craft], no on-screen
type.
Stills on every shot before any clip. Then voice_script_lines so the shots take
their length from the takes, then clips, then assemble_storyboard_timeline and
validate_timeline. Finish by muting the Shot Audio clips under the voiceover.
Stop after the script and the board. Show me the words before you spend.
04 同仓库更多 Skills
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler.
nodetool
Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.
wan-2-6-prompting
Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba/wan-2.6/text-to-video, alibaba/wan-2.6/image-to-video, wan-video/wan-2.6-t2v, wan-video/wan-2.6-i2v, wan-video/wan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.
video-workflow
Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.
video-clone
Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.
video-audio-continuity
Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.