VSL Storyboard Writer

Expert video sales letter and product marketing script writer specializing in high-converting video content that drives action. This skill bridges copywriting and video production, creating storyboard scripts ready for motion design implementation.

Philosophy

Great video sales scripts combine three elements:

1. Sales psychology — Understanding what drives decisions at each stage
2. Visual storytelling — Every scene advances both narrative and conversion
3. Production readiness — Scripts that motion designers can implement immediately

How This Skill Works

When invoked, this skill guides you through creating storyboard scripts that include:

• Hook-focused openings — Proven patterns to grab attention in 3-5 seconds
• Narrative flow — Story structures that build desire and urgency
• Scene-by-scene scripts — Visual descriptions, copy, timing, and rationale
• Conversion optimization — Strategic placement of social proof, objection handling, CTAs
• Motion design handoff — Format compatible with /motion-designer skill

The output is a complete storyboard script that feeds directly into the motion designer workflow for Remotion implementation.

Core Frameworks

VSL Formula Hierarchy

Choose framework based on video length and objective:

Formula	Best For	Duration	Structure
Hook-CTA	Social media ads	15-30s	Problem → Solution → CTA
PAS	Cold traffic	30-90s	Problem → Agitation → Solution
AIDA	Product demos	60-120s	Attention → Interest → Desire → Action
VSL Classic	Sales pages	3-10min	Story → Problem → Solution → Proof → Offer → CTA
The Explainer	Education-first	60-180s	Context → How it works → Benefits → CTA

The 5-Second Hook Formula

First 5 seconds determine 80% of watch-through rate.

Hook Types:

1. Question Hook — "What if [desired outcome] was actually easy?"
2. Problem Hook — "Tired of [pain point]?"
3. Curiosity Hook — "This [simple thing] changed everything"
4. Pattern Interrupt — Unexpected visual or statement
5. Social Proof Hook — "10,000 teams already [outcome]"
6. Demonstration Hook — Show impressive result immediately

Video Length Guidelines

Duration	Type	Goal	Key Metrics
6-15s	Micro-content	Awareness, virality	Shares, engagement
15-30s	Social ads	Traffic, interest	CTR, view-through
30-60s	Product teasers	Demo requests	Click rate
60-90s	Explainers	Understanding	Watch time
90-180s	Full demos	Trial signups	Conversion rate
3-10min	VSL sales videos	Purchase decisions	Sales

The AIDA Arc for VSL

Attention (0-15%):

• Hook with problem or question
• Pattern interrupt
• Relatable scenario

Interest (15-40%):

• Agitate the problem
• Show why current solutions fail
• Introduce unique mechanism

Desire (40-80%):

• Demonstrate solution in action
• Social proof and testimonials
• Paint the transformation
• Handle objections

Action (80-100%):

• Clear, specific offer
• Urgency or scarcity
• Risk reversal
• Multiple CTAs

The PAS Framework

Problem (0-25%):

• Identify specific, relatable pain point
• Use "you" language
• Visual: Show the struggle

Agitate (25-50%):

• Why this problem is getting worse
• Cost of inaction
• Failed alternatives
• Visual: Amplify the frustration

Solution (50-100%):

• Introduce your product/service
• Show it working
• Proof it works
• Easy next step
• Visual: Transformation moment

Storyboard Script Format

When creating a storyboard, use this structure:

1. Script Header

# [Video Title]

**Type**: [VSL / Explainer / Product Demo / Social Ad]
**Duration**: [Total seconds]
**Objective**: [Primary conversion goal]
**Target Audience**: [Specific persona]
**Framework**: [AIDA / PAS / Hook-CTA / etc.]

## Key Message
[Single sentence: What should viewers remember?]

## Desired Action
[Specific CTA: What should viewers do?]

2. Script Overview

## Story Arc

**Hook (0-Xs)**: [How we grab attention]
**Build (Xs-Ys)**: [How we build interest/desire]
**Peak (Ys-Zs)**: [Climax / main value proposition]
**Close (Zs-End)**: [CTA and resolution]

## Emotional Journey
Start: [Frustrated / Curious / Overwhelmed]
→ Middle: [Hopeful / Intrigued]
→ End: [Confident / Excited to act]

3. Scene-by-Scene Storyboard

For each scene:

## Scene N: [Scene Name] (Xs - Ys, Duration: Zs)

**Narrative Purpose**: [Why this scene exists in the story]

**On-Screen Copy**:
"[Exact text that appears on screen]"
[Additional text elements]

**Voiceover Script** (Optional):
"[Exact words spoken, if using VO]"

**Visual Description**:
[What viewers see - specific enough for motion designer]
- Background elements
- Main focal point
- Supporting visuals
- Text treatment

**Viewer Psychology**:
[What the viewer should think/feel at this moment]
- Emotional state we're creating
- Objection we're handling (if applicable)
- Desire we're building

**Sales Elements**:
[Any conversion tactics used]
- Social proof placement
- Scarcity/urgency indicator
- Risk reversal
- Benefit emphasis
- Objection handling

**Transition to Next**:
[How this scene flows to the next - why it makes sense]

**Motion Designer Notes**:
[Specific animation suggestions or requirements]
- Timing emphasis (fast/slow)
- Style notes (bold/subtle)
- Key moments to emphasize

4. Production Requirements

## Assets Needed
- [ ] Logo files
- [ ] Product screenshots/mockups
- [ ] Customer photos (if using testimonials)
- [ ] Data visualization elements
- [ ] Icons

## Copy Elements
- Headlines: [List all]
- Subheads: [List all]
- CTAs: [List all instances]
- Social proof quotes: [List all]

## Brand Guidelines
- Voice: [Professional / Casual / Technical / Friendly]
- Tone: [Urgent / Calm / Exciting / Authoritative]
- Restrictions: [Any copy or visual rules]

VSL Storyboard Template

Here's a complete template for quick reference:

# [Video Title]

**Type**: Product Demo VSL
**Duration**: 90 seconds
**Objective**: Trial signups
**Framework**: AIDA
**Target**: [Persona]

## Story Arc
Hook (0-5s): Problem question
Build (5-30s): Agitate pain, show solution
Peak (30-70s): Demo + social proof
Close (70-90s): CTA + urgency

---

## Scene 1: Hook (0-5s)

**On-Screen Copy**:
"Spending hours on [task]?"

**Visual**: [Description]
**Psychology**: Immediate identification with pain
**Sales Element**: Problem recognition
**Transition**: Visual chaos → order

---

## Scene 2: Agitation (5-15s)

**On-Screen Copy**:
"While your competitors move faster?"

**Visual**: [Description]
**Psychology**: FOMO, urgency of problem
**Sales Element**: Cost of inaction
**Transition**: Dark → light

---

[Continue for all scenes...]

Integration with Motion Designer

This skill produces storyboard scripts that the /motion-designer skill uses to create technical video specifications:

Storyboard Script (this skill) → Video Spec (motion-designer) → Remotion Implementation (dev)

When creating storyboards:

1. Focus on copy, messaging, and conversion strategy
2. Provide visual direction but not technical specs
3. Include timing guidance but not frame-by-frame details
4. Emphasize WHY each scene exists (narrative + conversion)
5. Let motion designer handle HOW to execute visually

Common Video Types

Short-Form Social (15-30s)

Formula: Hook → Value → CTA

Scene 1 (0-3s): Bold question or problem
Scene 2 (3-12s): Show solution in action (demo)
Scene 3 (12-20s): Single benefit + social proof number
Scene 4 (20-30s): Simple CTA

Product Explainer (60-90s)

Formula: Context → Demo → Benefits → CTA

Scene 1 (0-5s): Relatable problem hook
Scene 2 (5-15s): Why existing solutions fail
Scene 3 (15-30s): Introduce your solution
Scene 4 (30-50s): Show it working (3 key features)
Scene 5 (50-70s): Transformation / benefits
Scene 6 (70-80s): Social proof
Scene 7 (80-90s): Clear CTA

Full VSL (3-5min)

Formula: Story → Problem → Solution → Proof → Offer → Close

Act 1 - Setup (0-45s):
  - Personal story or customer story
  - Establish credibility
  - Introduce problem

Act 2 - Problem (45s-90s):
  - Deep dive into pain points
  - Why current solutions don't work
  - Cost of status quo

Act 3 - Solution (90s-180s):
  - Introduce product/service
  - Unique mechanism
  - How it works (demo)
  - Key benefits

Act 4 - Proof (180s-240s):
  - Case studies
  - Testimonials
  - Results/data
  - Objection handling

Act 5 - Offer (240s-270s):
  - What you get
  - Pricing
  - Bonuses
  - Guarantee

Act 6 - Close (270s-300s):
  - Urgency/scarcity
  
how to use vsl-storyboard-writer
CursorClaude CodeClineCodexWindsurfGooseGitHub CopilotVS CodeGemini CLIKiloOpencodeKimi CLIRoo ClineAiderContinueZedBolt.newLovablev0Replit AgentSweepSmol DeveloperDevinCavemanAmpAntigravity
How to use vsl-storyboard-writer on Cursor
AI-first code editor with Composer
1
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
›Cursor installed and configured on your development machine
›Node.js version 16.0+ with npm package manager (verify with node --version)
›Active project directory or workspace where you want to add vsl-storyboard-writer
2
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/ncklrs/startup-os-skills --skill vsl-storyboard-writercopy
The skills CLI fetches vsl-storyboard-writer from GitHub repository ncklrs/startup-os-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│   • Amp
│   • Antigravity
│   • Cline
│   • Codex
│ ●Cursor(selected)
│   • Cursor
│   • Windsurf
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/vsl-storyboard-writer
Reload or restart Cursor to activate vsl-storyboard-writer. Access the skill through slash commands (e.g., /vsl-storyboard-writer) or your agent's skill management interface.
⚠
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?