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.
Fetches vsl-storyboard-writer from ncklrs/startup-os-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/vsl-storyboard-writer
Restart Cursor to activate vsl-storyboard-writer. Access via /vsl-storyboard-writer in your agent's command palette.
⚠
Security 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 environment. Always review source, verify the publisher, and test in isolation before production.
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:
Sales psychology — Understanding what drives decisions at each stage
Visual storytelling — Every scene advances both narrative and conversion
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:
Question Hook — "What if [desired outcome] was actually easy?"
Pattern Interrupt — Unexpected visual or statement
Social Proof Hook — "10,000 teams already [outcome]"
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 JourneyStart: [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
Include timing guidance but not frame-by-frame details
Emphasize WHY each scene exists (narrative + conversion)
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
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
