plugins/copywriting/skills/video-scripting/SKILL.md
Use when writing long-form video scripts that need retention engineering and narrative structure. Trigger phrases - "writing YouTube video script", "VSL (video sales letter)", "long-form video script", "course module video", "explainer video", "retention curve optimization", "video script for course", "scénář YouTube videa", "VSL skript", "long-form video", "scénář kurzového videa", "video script". Do NOT use for short-form TikTok/Reels under 60s — use copywriting:ig-content.
npx skillsauth add petrogurcak/skills video-scriptingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Long-form video lives or dies on retention curve. Three layered frameworks combined:
Core principle: Hook → Substance → Payoff. If the payoff is missing, the algorithm punishes you and trust breaks.
Announce: "I'm using video-scripting to engineer retention and structure."
USE:
DON'T USE:
copywriting:ig-contentcopywriting:web-copycopywriting:storytellingThe first 5-7 seconds decide everything. If retention drops below 70% here, the video is dead.
Snyder Logline (4 elements compressed into hook):
Heath Curiosity Gap: State what viewer doesn't know but should. "Most people get X wrong — here's why."
Auditory + Visual hook combination: First 2s = strong visual (pattern interrupt, motion, face). First 5s = verbal hook delivering promise.
Top hook templates (from Video Playbook 50-list):
| Beat | 15-min YouTube (×0.13) | 45-min VSL (×0.4) | | --- | --- | --- | | 1. Opening Image | 0:00-0:15 | 0:00-0:40 | | 2. Theme Stated | 0:15-0:45 | 0:40-2:00 | | 3. Set-Up | 0:45-1:30 | 2:00-4:30 | | 4. Catalyst | 1:30-2:00 | 4:30-6:00 | | 5. Debate | 2:00-3:00 | 6:00-9:00 | | 6. Break Into Two | 3:00-3:45 | 9:00-11:00 | | 7. B Story | 3:45-4:30 | 11:00-13:30 | | 8. Fun and Games | 4:30-7:30 | 13:30-22:30 | | 9. Midpoint | 7:30 | 22:30 | | 10. Bad Guys Close In | 7:30-9:45 | 22:30-29:00 | | 11. All Is Lost | 9:45-10:30 | 29:00-31:00 | | 12. Dark Night of the Soul | 10:30-11:30 | 31:00-34:00 | | 13. Break Into Three | 11:30-12:15 | 34:00-36:30 | | 14. Finale | 12:15-14:30 | 36:30-43:30 | | 15. Final Image | 14:30-15:00 | 43:30-45:00 |
| Video type | Snyder genre | | --- | --- | | VSL | Dude with a Problem / Golden Fleece | | Educational YouTube | Whydunit / Institutionalized | | Personal Narrative | Rites of Passage / The Fool Triumphant |
Warning: Payoff missing → trust break + algorithm penalty (watch-time + return-viewer score both drop).
Jon Benson 5-step VSL structure:
Snyder All Is Lost = "agitate problem" phase — the moment where viewer realizes status quo is unsustainable.
Length rule:
| Mistake | Fix | | --- | --- | | "Pope in the Pool" missed — boring exposition kills retention | Disguise setup with visual action / B-roll / demonstration | | Inactive Hero — narrator/protagonist passive | Hero must make decisions and act, not just observe | | Talking the Plot — narrator describes instead of showing | Show Don't Tell — demonstrate on screen | | Too Much Pipe — 40-min Minority Report problem, setup eats body | Trim setup to <15% of runtime | | Missing Payoff — open loop never closed | Map every promise in hook to a payoff beat | | Wrong genre — educational dressed as Action | Use Snyder genre map above | | Static talking-head — no pattern interrupts | Cut every 3-7s, B-roll every abstract claim |
Full research with sources (MrBeast/Veritasium/Ali Abdaal benchmarks, Video Creator Playbook 50-hook templates, Heath SUCCESs, Snyder 15-beat detail):
docs/research/2026-05-12-video-scripting-retention.md
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).