CommunityWriting & Editinggithub.com

scriptwriting

Writes, edits, and optimizes vertical video scripts, including hook, voice-over, dialogue, on-screen text, pacing, payoff, and CTA.

What is scriptwriting?

scriptwriting is a Claude Code agent skill that writes, edits, and optimizes vertical video scripts, including hook, voice-over, dialogue, on-screen text, pacing, payoff, and CTA.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/achmdfzn/motionforge-atelier/tree/main/.claude/skills/scriptwriting

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

SCRIPTWRITING — Video Narrative Skill

Goal

Produce scripts that are clear when heard, strong when read on screen, and translatable into visuals and Remotion timing.

1. Preparation

Before writing, understand:

  • the creative brief and the output of beyond-video;
  • audience, platform, goal, duration;
  • the main message and the audience's knowledge level;
  • the brand's tone/voice;
  • factual, legal, and sourcing limits;
  • the visual style and production capacity.

Do not write a script that contradicts the creative brief without explaining why.

2. Script structure

Use a fitting structure, not a rigid formula:

  • Hook.
  • Context/setup.
  • Development/progression.
  • Evidence/example/demo.
  • Turn/reveal.
  • Payoff.
  • CTA.

Short-form does not mean every sentence must be mechanically short. Vary rhythm and sentence length so it sounds natural.

3. Writing rules

  • Prefer one idea per sentence.
  • Avoid long intros and filler.
  • Use conversational language suited to the target audience.
  • Use concrete words, examples, analogies, and visual verbs.
  • Remove repetition that adds no meaning.
  • Do not use jargon without context.
  • Do not make absolute claims when the source only supports a limited claim.
  • Flag numbers, names, dates, quotes, and statistics that need verification.
  • Never fake testimonials or personal experiences.

4. Voice-over vs on-screen copy

Voice-over carries context/narration. On-screen text emphasizes keywords and information that needs to be read. Do not copy the whole VO onto the screen unless that is a deliberate design choice.

Every piece of on-screen text must be:

  • short and easy to scan;
  • hierarchical;
  • readable on a phone screen;
  • inside the safe area;
  • on screen long enough to read;
  • in sync with the visuals and VO.

5. Timing at 60 FPS

  • Set duration from word count, idea complexity, pauses, and visual action.
  • Reading-speed estimates are only a starting point; do not assume one speaking rate fits every narrator/language.
  • Record beats in seconds and convert to frames, or work directly in frames, using one rounding rule.
  • Leave room for visual payoff and transitions.
  • Avoid cramming in too much information just to hit a duration.

6. Script table

Use this format:

Beat/SceneTime / FrameVoice-over / DialogueOn-screen textVisual intentAudio cue
Hook...............

Include the total estimated duration and a list of claims that need verification.

7. CTA

The CTA must be one primary action: specific, easy to do, and relevant to the video. Do not automatically add "like, comment, subscribe". Tie the CTA to the benefit or follow-up the video promised.

Coordinate the CTA copy and ending context with the beyond-video skill; the closing logo + CTA must be bespoke.

8. Revision protocol

When editing a script:

  • identify the goal of the revision;
  • keep the parts that still work;
  • do not change the main message without explaining;
  • re-check facts after changes;
  • check sync with the storyboard and duration;
  • record trade-offs when the script is shortened.

8a. Tells of AI-written scripts

VO scripts are read aloud; mechanical patterns are caught faster by the ear than by the eye. Check the draft against this list before finalizing. A single occurrence is usually fine; what you are looking for is a repeated pattern. The list is written for English, with an Indonesian example per pattern because the same tells appear across languages; for other languages, build an equivalent list rather than translating these examples literally.

CodePatternEnglish exampleIndonesian exampleFix
A1Nominalized verbs (translationese)"perform an analysis of", "have an impact on""melakukan pembahasan"Use the direct verb: "analyze", "affect"
A2Stacked passive / missing agent"changes were made by the team""telah dilakukan perubahan oleh tim"Restore the agent: "the team changed…"
A3"Can" / "may" on every claim"this can help improve…""ini dapat meningkatkan…"Assert when it is true; hedge only when the source hedges
A4All-purpose connectors"in terms of", "with regard to", "where""terkait", "dalam hal", "di mana"Split the sentence or use the precise connector
B1Connective spam"Moreover… Therefore… As a result…" in every paragraph"Selain itu… Oleh karena itu…"Drop most of them; the order of ideas already connects them
B2List preambles"There are three things you need to know:""Ada tiga hal yang perlu diketahui:"Go straight to the first thing
B3Summary closers"In conclusion…", "At the end of the day…""Kesimpulannya…"End on a concrete payoff or the CTA
C1Significance inflation"crucial", "revolutionary", "game-changing""sangat penting", "revolusioner"Replace with a concrete fact, or delete
C2Repeated contrast formula"It's not X, it's Y" more than once"Bukan X, tapi Y"Keep one; turn the rest into direct statements
C3Transformation formula"From X to Y", "Beyond X""Dari X menjadi Y"At most once per video
C4Personified abstractions"technology asks", "the era demands""zaman menuntut"Use a real human/organizational subject
C5Speech-style closers"Now is the time…", "It's time to…""Inilah saatnya…"A concrete verb: what the viewer should do
D1Uniform sentence lengthEvery sentence 12–15 words—Mix very short sentences with longer ones
D2Constant triplets"fast, easy, and efficient" in every sentence"cepat, mudah, dan efisien"Pick the single strongest word
E1Term + gloss on every mention"skill (a reusable instruction)… skill (a reusable instruction)""skill (keterampilan)…"Explain once, then stay consistent
E2Empty marketing words"seamless", "robust", "next-level"—Say what actually happens
F1Emoji/symbol overload in on-screen text🚀✨ on every line—Only when it has a clear visual function

Safe-edit limits:

  • Do not touch: proper names, product names, numbers, dates, units, direct quotes, and standard technical terms (API, frame, render).
  • Content words must survive. Before editing, mark the nouns and concepts that carry the claim in each sentence. Remove only filler and inflation; do not swap content words for synonyms that change the meaning. When unsure, restore the original sentence.
  • Do not over-edit. If more than about a third of the words change, stop and check whether the meaning is still the same. The goal is a script that sounds natural, not a new script.
  • After editing, re-check the VO duration: tightened sentences change the storyboard timing.

Idea reference: epoko77-ai/im-not-ai (MIT) — category structure and safe-edit limits. The pattern list above was written from scratch, not translated from the Korean list.

9. Deliverables

Provide the final script, separate VO/dialogue, on-screen copy, beat timing, CTA, estimated duration, and fact-check notes.

Individual skills in this repo

This repo contains 6 individual skills — each has its own dedicated page.

Related Skills