Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@contentstudio

Video script writer

@contentstudio/video-script-writer

Write video scripts that are easy to film: short vertical videos (15 to 90 seconds) and longer explainers or demos (3 to 10 minutes), in a two-column format with what is said, what is on screen, timing from word count, and a shot list.

SkillContentv1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: video-script-writer
  3. 3description: Write a filmable video script, either a short vertical video (Reels, TikTok, Shorts, LinkedIn, 15 to 90 seconds) or a longer explainer, product demo, or YouTube video (3 to 10 minutes). Uses a two-column format (spoken words and on-screen visuals), times every section from word count, and adds a shot list and captions notes. Use when the user says "write a video script", "script for a reel", "demo video script", "YouTube script", "explainer video", or "what should I say on camera?"
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Video script writer
  8. 8
  9. 9A script for video is not an article read aloud. It has to hook in seconds, be sayable in one breath per line, and tell the person holding the camera what to shoot. This kit writes scripts in the two-column format editors use, timed from the word count.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- Short vertical video for Reels, TikTok, Shorts, or LinkedIn.
  14. 14- Product demos, explainers, onboarding videos, YouTube videos, webinar intros.
  15. 15- "Script this", "what do I say in a 60-second video about X?", "turn this blog into a video".
  16. 16
  17. 17## Inputs
  18. 18
  19. 191. **Topic and the one takeaway** the viewer should leave with.
  20. 202. **Length and platform.** Default: 60 seconds vertical. Pacing assumption: about 150 spoken words per minute (130 for a demo with clicks, 170 for a fast talking-head).
  21. 213. **Who is on camera** (founder, presenter, voiceover only, screen recording only) and what can be filmed (a phone, a screen recorder, b-roll of the office).
  22. 224. **Source material:** a post, doc, or demo flow in `content/`.
  23. 235. **Call to action:** follow, visit a link, book a demo, comment.
  24. 246. **Voice:** `brand.md` if it exists.
  25. 25
  26. 26## Steps
  27. 27
  28. 281. **Write three hooks** for the first 3 seconds (short) or 15 seconds (long). Types: a surprising result, a direct question, a "you are doing X wrong", or showing the end result first. Pick one and say why.
  29. 292. **Outline the beats:**
  30. 30 - **Short:** hook (0 to 3s), problem (3 to 10s), 2 or 3 points or steps, payoff, call to action (last 5s).
  31. 31 - **Long:** hook and promise (0 to 30s), context (why it matters), 3 to 5 sections each with one idea and a visual, recap, call to action. Put a re-hook ("here is where it gets interesting") at about one third.
  32. 323. **Write the script in two columns.** Spoken lines short enough to say in one breath (under 15 words). Plain words. Contractions. No lines that only work when read.
  33. 334. **Time it.** Count words per section, convert at the pacing above, and show seconds per row and a total. If over length, cut the weakest point, not the hook or the call to action.
  34. 345. **Add on-screen text** for the key line of each section (most short video is watched muted) and caption notes.
  35. 356. **Add a shot list** grouped by location or setup, so filming happens in one pass.
  36. 367. **Save** to `content/video/<slug>.md` and show the script.
  37. 37
  38. 38## Output format
  39. 39
  40. 40```markdown
  41. 41# Video: <title> (60s vertical, talking head)
  42. 42Takeaway: <one line> | Words: 148 | Est. 59s at 150 wpm
  43. 43
  44. 44Hook options
  45. 451. "Your reminder texts are too long." (chosen: direct and testable)
  46. 462. ...
  47. 47
  48. 48| Time | Spoken | On screen | Shot |
  49. 49| --- | --- | --- | --- |
  50. 50| 0:00 to 0:03 | "Your reminder texts are too long." | TEXT: "Too long." | Close-up, phone in hand |
  51. 51| 0:03 to 0:10 | "We tested short versus long across thousands of reminders." | Two phones side by side | Screen recording |
  52. 52
  53. 53Call to action: <line>
  54. 54
  55. 55## Shot list
  56. 56- Desk setup: talking head, rows 1, 4, 6
  57. 57- Screen recording: rows 2, 3
  58. 58
  59. 59## Caption notes
  60. 60- Burn in captions; key words in bold: "too long", "2 lines".
  61. 61```
  62. 62
  63. 63## Guardrails
  64. 64
  65. 65- Never invent results, customer names, or testimonials. Use `<need: real number>` placeholders.
  66. 66- Do not script claims a regulated industry cannot make (health outcomes, financial returns) without flagging them for review.
  67. 67- Keep on-screen text to 6 words or fewer per card.
  68. 68- If a demo shows a product, script only features the user confirms exist.
Sign in to comment on a line