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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionvsl-storyboard-writerExecute the skills CLI command in your project's root directory to begin installation:
Fetches vsl-storyboard-writer from ncklrs/startup-os-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate vsl-storyboard-writer. Access via /vsl-storyboard-writer in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
13
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
13
stars
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.
Great video sales scripts combine three elements:
When invoked, this skill guides you through creating storyboard scripts that include:
/motion-designer skillThe output is a complete storyboard script that feeds directly into the motion designer workflow for Remotion implementation.
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 |
First 5 seconds determine 80% of watch-through rate.
Hook Types:
| 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 |
Attention (0-15%):
Interest (15-40%):
Desire (40-80%):
Action (80-100%):
Problem (0-25%):
Agitate (25-50%):
Solution (50-100%):
When creating a storyboard, use this structure:
# [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?]
## 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]
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
## 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]
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...]
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:
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
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
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
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
704mattpocock/skills
Productivitysame categorypremortem
218parcadei/continuous-claude-v3
Productivitysame categorydeslop
164cursor/plugins
Productivitysame categorytravel-planner
145ailabs-393/ai-labs-claude-skills
Productivitysame categorynutritional-specialist
141ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
140pproenca/dot-skills
Productivitysame categoryReviews
4.6★★★★★34 reviews- PPratham Ware★★★★★Dec 20, 2024
vsl-storyboard-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- CCarlos Flores★★★★★Dec 20, 2024
vsl-storyboard-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- SSofia Singh★★★★★Dec 16, 2024
Solid pick for teams standardizing on skills: vsl-storyboard-writer is focused, and the summary matches what you get after install.
- MMei White★★★★★Dec 16, 2024
Registry listing for vsl-storyboard-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
- MMeera Ramirez★★★★★Dec 12, 2024
vsl-storyboard-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAva Perez★★★★★Nov 11, 2024
vsl-storyboard-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- LLi Martin★★★★★Nov 7, 2024
Keeps context tight: vsl-storyboard-writer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- LLi Sharma★★★★★Oct 26, 2024
I recommend vsl-storyboard-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- WWilliam Lopez★★★★★Oct 2, 2024
vsl-storyboard-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- YYash Thakker★★★★★Sep 17, 2024
vsl-storyboard-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 34
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.