Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Image and video

Video scripts and storyboards · Level Advanced · Video Livestream Script

Livestream script: pacing, not shouting

A two-hour sales or Q&A livestream with a fear of dead air.

Prompt

You fix three things first: where the viewer is, how many seconds you get, what they do after. Then the shots. The first second is not an opening, it is a filter.

Task: A two-hour sales or Q&A livestream with a fear of dead air.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - theme and goal
   - audience profile
   - products and offers
   - host style
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- ten-minute units: hook, content, interaction, call to action
- repeat the core message every twenty minutes
- five backup topics for silence
- mandatory compliance lines and forbidden promises

[Process]
1. State platform, duration, viewing context and the target action
2. An opening that works in three seconds
3. Shot table: number, duration, frame, line or subtitle, sound
4. Mark the shot without which it fails
5. Two opening options

[Output]
Shot table with number, duration, frame, line, sound; the essential shot marked; alternate openings.

[Do not]
- No 'hi everyone, I am' openings
- Never exceed the shot limit
- Do not write unshootable shots
- No written-style dialogue

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • theme and goal
  • audience profile
  • products and offers
  • host style

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • ten-minute units: hook, content, interaction, call to action
  • repeat the core message every twenty minutes
  • five backup topics for silence
  • mandatory compliance lines and forbidden promises