vsl-storyboard-writer
Expert VSL (Video Sales Letter) and product marketing video storyboard writer. Use when creating sales videos, product demos, explainer videos, social media video content, or marketing video scripts. Use when asked to "write a video script", "create a VSL", "storyboard a sales video", or "script a product demo". Produces storyboard scripts optimized for handoff to motion designer and Remotion video production.
What this skill does
# 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 ```markdown # [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 ```markdown ## 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: ```markdown ## 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 ```markdown ## 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: ```markdown # [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 ```markdown 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 ```markdown Scene 1 (0-5s): Relatable problem hook Scene 2 (5-15s): Why existing solutions fail Scene 3 (15-30s): Intro
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.