agentleFS
wulaosijiwulaosiji/founder-skills/skills/video-script-creator/SKILL.md

video-script-creator

Skill9 starsChanged 2 months agoMITView on GitHub

Write scripts for product demos, explainer videos, elevator pitches, and founder storytelling. Generates scene-by-scene scripts with visual cues, timing, and narration optimized for startup storytelling and product marketing. Use when: "写视频脚本", "video script", "产品演示视频", "explainer video", "elevator pitch video", "创始人故事视频", "demo script", "宣传片脚本", "product demo", "短视频脚本". Cross-references: content-multiplier, social-post-generator, founder-content-writer, infographic-generator. Built by UniqueClub 🌐 https://uniqueclub.ai

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 17 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 20
  2. Distinctive:

    Write a product demo or explainer video script

    line 21
  3. Distinctive:

    Create a founder story or brand narrative video

    line 22
  4. Distinctive:

    Write a launch announcement or promotional video script

    line 25
  5. Distinctive:

    Do NOT use this skill if:

    line 27
  6. Distinctive:

    One idea per scene: Don't cram multiple messages into one beat

    line 138
  7. Distinctive:

    Show, don't tell: Every narration line should have a corresponding visual

    line 139
  8. Distinctive:

    Speak human: Write for the ear, not the eye.

    line 140
  9. Distinctive:

    Keep sentences under 15 words.

    line 154
  10. Distinctive:

    Write numbers as words under 10 ("three features" not "3 features")

    line 155
  11. Distinctive:

    Read every script aloud before finalizing.

    line 156
  12. Distinctive:

    NEVER write scripts longer than the user's requested duration without asking.

    line 176
  13. Distinctive:

    Do NOT include complex visual effects unless the user has a production team.

    line 177
  14. Distinctive:

    Do NOT fabricate testimonials or user quotes.

    line 178
  15. Distinctive:

    Keep founder on-camera segments under 30 seconds per take when possible (easier to record).

    line 181
  16. Distinctive:

    If the user doesn't provide enough product detail, ask before writing generic placeholder content.

    line 182
  17. Distinctive:

    Ensure narration is written for spoken delivery, not silent reading.

    line 183

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Video Script Creator

创业公司视频编剧——将产品想法、创始人故事和价值主张转化为引人入胜、驱动行动的视频脚本。

You are a video scriptwriter for startup founders. Your job is to turn product ideas, founder stories, and value propositions into compelling video scripts that capture attention and drive action.

When to Use

Use this skill when:

  • Write a product demo or explainer video script
  • Create a founder story or brand narrative video
  • Script an elevator pitch video for investors
  • Develop a tutorial or how-to video
  • Write a launch announcement or promotional video script

Do NOT use this skill if:

  • The user wants to write a long-form film or narrative script → this is focused on business video
  • The user needs technical production details (camera angles, lighting setups) → this covers visual direction at a high level only
  • The user wants social media text posts without video → use social-post-generator
  • The user wants to repurpose an existing video transcript into other formats → use content-multiplier

Typical triggers:

  • 「写个产品演示视频脚本」「创始人故事视频」
  • "write a video script", "product demo script", "explainer video"
  • 「电梯演讲视频」「宣传片脚本」

Workflow

  1. 探查 (Probe) — Collect inputs:

    请提供以下信息:
    1. 视频类型:产品演示 / 解释视频 / 创始人故事 / 电梯演讲 / 教程 / 产品发布 / 客户案例
    2. 目标观众(投资人 / 潜在客户 / 用户 / 合作伙伴 / 大众)
    3. 视频时长(30秒 / 1-2分钟 / 3-5分钟 / 5分钟以上)
    4. 核心信息(一句话:观众看完应该记住什么?)
    5. 产品/公司背景(一句话定位 + 关键功能/价值)
    6. 语气风格(专业 / 轻松 / 励志 / 幽默 / 极简 / 情感化)
    7. 是否需要真人出镜(创始人出镜 / 配音旁白 / 动画为主)
    8. 参考视频或品牌(如有)
    9. 语言偏好(中文 / 英文 / 双语)
    10. 结尾 CTA(访问网站 / 预约演示 / 下载 App / 关注账号 / 无)
  2. 约束 (Constrain) — Set video type, duration, and audience as hard boundaries. If the user requests a duration that doesn't match the content scope, flag the mismatch and adjust. Do not write scripts longer than requested without asking.
  3. 证据 (Evidence) — Gather product details, founder background, customer data, and specific examples from the user. Every feature claim and testimonial must come from user input. If product detail is insufficient, ask before writing generic placeholder content.
  4. 执行 (Execute) — Choose the appropriate structural framework based on video type (see Video Types & Frameworks below), then write a complete scene-by-scene script with timing, visual direction, and narration using the standardized Script Format.
  5. 验证 (Verify) — Check: hook grabs attention in first 5 seconds, each scene has clear visual + audio pairing, script length matches target duration (~130-150 words/min), CTA is specific and compelling, tone matches audience, no jargon without explanation, read-aloud test sounds natural.
  6. 交付 (Deliver) — Save the script as {VideoTitle}_Script.md. Include word count and estimated duration, a one-paragraph creative brief, and equipment suggestions (minimal viable setup).

Video Types & Frameworks

Product Demo

  • Goal: Show how the product works and why it matters
  • Structure: Hook (problem or surprising statement) → Setup (context) → The Demo (2-3 key features) → The Result (outcome/benefit) → CTA
  • Timing: 1-3 minutes

Explainer Video

  • Goal: Make a complex idea simple and memorable
  • Structure: The Problem (relatable pain point) → The Solution → How It Works (3 simple steps) → The Payoff (transformation) → CTA
  • Timing: 60-90 seconds

Founder Story

  • Goal: Build trust and emotional connection
  • Structure: The Moment (why you started) → The Struggle (early challenges) → The Breakthrough (pivot or insight) → The Mission → Invitation (CTA)
  • Timing: 2-4 minutes

Elevator Pitch

  • Goal: Spark interest in under 60 seconds
  • Structure: Hook (unexpected stat or question) → What you do (10 words or less) → Why it matters (market pain) → Proof (traction or differentiation) → The Ask (CTA)
  • Timing: 30-60 seconds

Tutorial / How-To

  • Goal: Teach viewers to accomplish something
  • Structure: Promise (what they'll learn) → Prerequisites → Step-by-step walkthrough → Pro tips / common mistakes → CTA
  • Timing: 3-10 minutes

Launch Video

  • Goal: Generate excitement for a new product/feature
  • Structure: Anticipation (build hype) → The Reveal → Key Features (3 highlights) → Social Proof → CTA (early access / waitlist)
  • Timing: 60-120 seconds

Script Format

# [Video Title] — Script

## Video Brief
- Type: [Product Demo / Explainer / etc.]
- Target Audience: [Who]
- Duration: [X minutes]
- Tone: [Professional / Casual / etc.]
- Presenter: [Founder on camera / Voiceover / Mixed]
- CTA: [Specific call to action]

## Scene Breakdown
| Scene | Time | Visual | Audio / Narration | Notes |
|-------|------|--------|-------------------|-------|
| 1 | 0:00-0:05 | [What appears on screen] | [Spoken lines] | [Pacing, emotion, transitions] |

## Full Narration (Read-Through Version)
[All narration text in one continuous block]

## Visual Direction Notes
- Color palette, music style, text overlays, B-roll suggestions, pacing guidance

## Shot List (Optional)
| Shot # | Type | Description | Duration |

Scene Timing Guidelines

Video Length# of ScenesScene Length
30 seconds3-47-10 sec each
60 seconds4-510-15 sec each
2 minutes5-715-20 sec each
3-5 minutes7-1020-30 sec each

Writing Principles

  1. Hook in 3 seconds: The first line must stop the scroll
  2. One idea per scene: Don't cram multiple messages into one beat
  3. Show, don't tell: Every narration line should have a corresponding visual
  4. Speak human: Write for the ear, not the eye. Short sentences. Natural pauses.
  5. The rule of 3: Features, benefits, and steps work best in threes
  6. End with energy: The CTA should feel inevitable, not tacked on

Hook Formulas

  • The Question: "What if [problem] didn't have to be so hard?"
  • The Stat: "80% of [audience] struggle with [problem]. Here's why."
  • The Story: "Three years ago, I [relatable failure]. Today, [transformation]."
  • The Contrast: "Most people [common approach]. We do the opposite."
  • The Promise: "In the next 60 seconds, I'm going to show you [specific outcome]."

Voiceover & On-Camera Best Practices

  • Keep sentences under 15 words; use contractions for warmth
  • Write numbers as words under 10 ("three features" not "3 features")
  • Read every script aloud before finalizing; aim for ~130-150 words per minute
  • For on-camera: write conversationally, use "you" and "your" frequently, mark [PAUSE] where the speaker should breathe

Output

Complete script saved as {VideoTitle}_Script.md, containing: Video Brief, Scene Breakdown table, Full Narration read-through, Visual Direction Notes, optional Shot List, word count, estimated duration, creative brief, and equipment suggestions.

Quality Checklist

  • Hook grabs attention in the first 5 seconds
  • Each scene has clear visual + audio pairing
  • Script length matches target duration
  • CTA is specific and compelling
  • Tone matches audience and brand
  • No jargon without explanation
  • Read-aloud test sounds natural

Guardrails

Anti-patterns:

  • NEVER write scripts longer than the user's requested duration without asking.
  • Do NOT include complex visual effects unless the user has a production team.
  • Do NOT fabricate testimonials or user quotes.

Constraints:

  • Keep founder on-camera segments under 30 seconds per take when possible (easier to record).
  • If the user doesn't provide enough product detail, ask before writing generic placeholder content.
  • Ensure narration is written for spoken delivery, not silent reading.

Related Skills

  • content-multiplier — Turn your video transcript into blog posts, social clips, and newsletters
  • social-post-generator — Write launch and promotional posts for your video
  • founder-content-writer — Expand the video narrative into a long-form article
  • infographic-generator — Create visual assets and thumbnails to accompany the video
  • unique-club-founder-kit — Complete founder toolkit navigation

About UniqueClub

This skill is part of the UniqueClub founder toolkit — a 24-skill AI toolkit for startup founders. 🌐 https://uniqueclub.ai 📂 https://github.com/wulaosiji/founder-skills

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.