ugc-multicut-script
Skill4 starsChanged 5 months agoMITView on GitHub
Step 4 of the ugc-ad pipeline. Write a motion-dense multi-cut video script — 0–15s split into three time-sliced cuts matching the storyboard (Hook / Setup-Action / Recommendation), with camera behavior, physical interaction beats, and a spoken monologue with sound cues. This becomes the Seedance prompt. No generation; authoring only. Brand-agnostic.
In this repository7 other files it gives its agents.
- ugc-adSkill
- ugc-base-characterSkill
- ugc-briefSkill
- ugc-enhanceSkill
- ugc-product-profileSkill
- ugc-storyboard-sheetSkill
- ugc-videoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 53
No em-dashes / en-dashes anywhere in the VO lines.
- Distinctive: line 68
Keep the WRITTEN brand spelling correct everywhere else (profile, caption, on-screen label) — ONLY the spoken VO quote gets the phonetic …
- Very specific: line 76
When a word with an aɪ.əl glide (vial / trial / dial / phial) misfires, anchor it to a real one-syllable word the TTS already knows rather …
≈ “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
ugc-multicut-script
Writes the directorial prompt that drives the single Seedance generation.
Inputs
PROFILE(product-profile.md),BRAND_FACTS(voice/positioning),DEST, optionalDURATION(default 15, max 15).
Steps
- Map three cuts onto the timeline (e.g. 0–4s Hook, 4–10s Setup/Action, 10–15s Recommendation), each matching its storyboard panel.
- For each cut, specify:
- camera behavior (handheld micro-shake for selfie hook vs locked-off for macro),
- the physical interaction (the exact usage step from PROFILE — sanitizing, pouring, applying, gesturing),
- the spoken monologue line (natural creator voice, brand facts woven in, NO em-dashes; write brand names / unusual words PHONETICALLY — see the VO Pronunciation Playbook below),
- sound cues (ambient room tone, product sfx).
Write
DEST/script.md:# UGC Script — <slug> (<DURATION>s, 3 cuts) ## Cut 1 — Hook (0–Xs, Tight, handheld micro-shake) - Action: ... - VO: "..." - SFX: ... ## Cut 2 — Setup/Action (X–Ys, Macro, locked-off) - Action: <exact usage step> - VO: "..." - SFX: ... ## Cut 3 — Recommendation (Y–<DURATION>s, Wide, handheld) - Action: ... - VO: "..." - SFX: ... ## SEEDANCE_PROMPT <one dense paragraph concatenating the three cuts as a continuous motion+dialogue description — this exact block is what the video step passes to seedance_2_0. OPEN with a one-line voice spec (e.g. "The voiceover is a calm, credible late-20s female narrator speaking clear American English. No subtitles, no on-screen captions."). Introduce each spoken line with `she says:` / `he says:` and put the line in quotes. End the block with "No subtitles.">
Output
DEST/script.md containing a SEEDANCE_PROMPT block.
Constraints
- Total runtime ≤ 15s (Seedance hard cap).
- Monologue must be speakable in the allotted seconds (~2.5 words/sec). (~32 words across 15s validated comfortable.)
- No em-dashes / en-dashes anywhere in the VO lines.
VO Pronunciation Playbook (validated 2026-06-22, Seedance 2.0 native audio)
Seedance synthesizes the VO from the literal text in the prompt, so spelling drives pronunciation. Two failure modes seen live:
- Letter-by-letter spell-out: a non-word brand like
nustandardlabsis read "N-U-standard-labs". - Mangling: the naive fix
New Standard Labscame out "newstandard labbers" (words fused + a schwa turned "Labs" into "labbers").
Rules that fixed it:
- Respell phonetically with clear word boundaries.
nustandardlabs->Noo Standard Labz. Use "z" for voiced plural endings ("Labz" not "Labs") to stop schwa insertion. Test it by reading your spelling aloud as a stranger would. - Explicit dialogue form:
she says: "..."(notsaying, "...") — uses your exact words. - Append
No subtitles.or the model burns auto-captions into the video. - Specify the voice once at the top of SEEDANCE_PROMPT: tone + age + gender + language.
- Only a human can verify the audio. Render 720p first (cheap; audio is resolution-independent), confirm pronunciation, keep that take. Never pay for 1080p just to check audio.
Keep the WRITTEN brand spelling correct everywhere else (profile, caption, on-screen label) — ONLY the spoken VO quote gets the phonetic respelling.
Known-fix lexicon (drop these spellings straight into the spoken VO quote)
| Word | Mispronounced as | Use this spelling | Why |
nustandardlabs | "N-U-standard-labs" / "newstandard labbers" | Noo Standard Labz | word boundaries + voiced "z" ending |
vial | "vawl" / "vile-uhl" | vile (validated 2026-06-22) | one-syllable /vaɪl/; the engine knows the word and says it clean, and in context (vials on screen) the ear reads "vial". Two-syllable respellings (vye-uhl, VY-ull) collapse to "vawl". |
When a word with an aɪ.əl glide (vial / trial / dial / phial) misfires, anchor it to a real one-syllable word the TTS already knows rather than hyphenating syllables.
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.

