Video Script from Talking Points

What this skill does

Takes a list of talking points and produces a 90-second (about 240 words) two-column video script: spoken lines on the left, B-roll and on-screen text suggestions on the right. The output is paste-ready into a teleprompter app.

Inputs

• points: array of strings (3-7 ideas).
• audience: developer, business, general — drives vocabulary.
• Optional format: monologue (default) or interview (with on-camera Q&A cues).
• Optional cta: a single line for the closing.

Steps

1. Estimate words: aim for 230-250 words at ~150 wpm.
2. Allocate words: 15 to the hook, 30 to context, 25 per talking point, 30 to the CTA. Adjust if points count is large.
3. Write the hook (about 6 seconds): a question or a contrarian statement that sets up tension.
4. Write the context line (about 12 seconds): name the audience pain in one sentence, frame the goal of the next 60 seconds.
5. For each point, write a spoken sentence (10-15 words) plus a B-roll cue. Cues describe what the viewer sees while you speak (e.g., "screen recording: terminal running npm install", "cutaway: stack of receipts", "graphic: title card with point #").
6. For each spoken line, suggest a 3-5 word on-screen text overlay that reinforces the key noun (e.g., "Saved 30%").
7. Write the CTA: a verb + the action (e.g., "Try it in your repo today.") followed by cta if provided.
8. Build the two-column layout in markdown using a table: | Spoken | B-roll / On-screen |.
9. Append a shot-list summary: total shots, count of on-camera vs cutaway.

Output

script-<topic>.md with the two-column table, an estimated runtime, and a shot list. Stdout prints word count and estimated seconds at 150 wpm.

Verification

Read the spoken column out loud with a stopwatch; total time should land between 80 and 100 seconds. If under 70, lengthen weak transitions; if over 100, cut filler ("really", "just", "actually"). Walk through B-roll cues and confirm each is filmable — abstract cues like "innovation" must be replaced with a concrete shot.

Edge cases

• Talking points overlapping heavily: consolidate adjacent points before scripting; do not repeat the same idea in different words.
• Highly technical points: include an on-screen overlay defining the term so viewers don't lose context.
• Talking points that imply screen demos: pad those with extra B-roll seconds since live screen demos run long.
• Sensitive topics (legal, medical): add a disclaimer on-screen overlay; do not present prescriptive advice as fact.