youtube-script-writer

name	youtube-script-writer
description	Write engaging, high-retention YouTube video scripts with visual and audio cues. Use when asked to write a YouTube script, design a video outline, draft a video hook, or structure a video narrative. Produces a polished script with multiple hook options, step-by-step video body, and clear visual/audio directions.

YouTube Script Writer Skill

This skill helps creators write highly engaging, structured, and visually-dynamic scripts optimized for YouTube's retention algorithm. It converts raw ideas, articles, or transcripts into a ready-to-shoot script with clear visual cues, pacing indicators, and audio directions.

What This Skill Produces

• 3 Title & Thumbnail Concepts: CTR-optimized titles matching distinct psychological triggers (curiosity, result-driven, contrarian) paired with clear visual thumbnail layout suggestions.
• 3 Hook Variations (0:00 - 0:30): Different hook formats (contrarian statement, story setup, pattern interrupt) that deliver immediately on the title's promise.
• Retention-Optimized Script Table: A side-by-side or block-formatted script separating video cues (B-roll, camera angles, text overlays, zooms) and audio cues (dialogue, voiceover, sound effects, music changes).
• Outro & Video Metadata: A seamless video outro designed to prevent viewer exit, along with search-optimized description templates and relevant tags.

Required Inputs

Ask the user for these if not provided:

• Topic/Concept — What is the video about? (e.g., "How I built a SaaS in 30 days")
• Target Audience — Who is watching? (e.g., beginner developers, student designers)
• Target Duration — Approximate length in minutes (e.g., 5-7 minutes, 10-15 minutes)
• Script Tone/Voice — E.g., energetic, educational, storytelling, conversational, comedic
• Primary Goal — (e.g., get newsletter signups, sell a course, increase viewer retention)

Pacing & Retention Model

Every YouTube script must follow this structure to prevent early drop-off:

1. The Hook (0:00 - 0:30): Promise immediate value. No intros, no logo animation, and no generic greeting ("Hey guys, welcome back...").
2. The Stakes / Re-Hook (0:30 - 1:00): Establish why this topic is difficult, urgent, or valuable. Introduce the "villain" (the problem) and the "hero" (the solution).
3. Chapters / Milestones (1:00 - 90% mark): Divide the core content into 3-5 distinct chapters. Every chapter must have a clear micro-payoff.
4. Pattern Interrupts: Suggest visual or audio changes every 4-8 seconds. Use zoomed frames, pop-up text, B-roll transitions, or sound effects (whoosh, ding, pop) to keep attention.
5. The Payoff / Climax (90% - 95% mark): Deliver the ultimate piece of advice or final revelation promised in the hook.
6. Seamless Transition CTA (95% - end): Never signal the end with "in conclusion" or "that is all." Bridge the final value point directly to recommending the next video or a quick call to action before the viewer leaves.

---

Output Format

[Working Title]

Target Duration: [Duration] | Audience: [Target Audience] | Tone: [Tone]

---

1. Title & Thumbnail Optimization

Title Options

1. The Curiosity Gap: [e.g., "The Real Reason Your Code is Slow (It's Not Python)"]
2. The Result-Oriented: [e.g., "How I Optimized My App to Handle 100k Users in 1 Hour"]
3. The Contrarian: [e.g., "Stop Using React for Simple Projects"]

Thumbnail Concepts

• Concept 1: [Visual details, e.g., Close-up of host with a worried face, split-screen showing a massive red 'Error' banner on one side and a clean green checkmark on the other. Large, bold 3-word text overlay: "STOP DOING THIS."]
• Concept 2: [Visual details, e.g., Clean graphic representation of a server load graph spiking to the moon, contrasted with a flat green line. Text overlay: "100K USERS."]

---

2. Hook Variations (Choose One)

Variation 1: The Contrarian Hook

• Visuals: [Host leans close to the camera, looking directly into the lens. Fast zoom-in on the word 'Slow' appearing in bold red letters on screen.]
• Audio: "Almost every developer I talk to blames Python for their slow apps. But 90% of the time, the language isn't the problem. The bottleneck is actually inside a single line of config you probably wrote yesterday."

Variation 2: The Story Hook

• Visuals: [Show B-roll of an editor showing 500 error logs flashing. Cut to host rubbing their forehead in frustration.]
• Audio: "Last Tuesday at 3 AM, our database completely crashed under load. We were losing $200 every minute the site was down. After searching through stack traces for hours, we found a fix so simple I couldn't believe we missed it."

Variation 3: The Pattern Interrupt Hook

• Visuals: [A stopwatch counts down from 5 seconds in the center of the screen. Sudden loud 'Ding' sound effect as the timer hits zero.]
• Audio (Voiceover): "In the next 5 minutes, I am going to show you the exact performance tweak that saved our team $4,000 in monthly server costs. And no, you don't need to rewrite a single database query."

---

3. The Main Script

Time / Chapter	Video Cues (B-Roll, Overlays, Camera Angles)	Audio Cues (Spoken Script, Sound Effects, Music)
0:30 - 1:00 The Re-Hook	Show on-screen graphics displaying server costs. Zoom in slightly on the host.	"Here is the reality: database optimization sounds incredibly complex. But most tutorials make you learn SQL queries you will never use. Today, we are keeping it purely practical."
1:00 - 3:30 Chapter 1: [Chapter Name]	[Visual Cue: Transition to screencast. Highlight lines 12-15 in the config file. Add cursor highlight.]	"[Spoken Dialogue]: First, let's open up the default configuration file. Notice this specific pool size limit... [Sound Effect: soft click]"
3:30 - 6:00 Chapter 2: [Chapter Name]	[Visual Cue: Cut back to host. Push-in zoom on host's face to emphasize the point.]	"[Spoken Dialogue]: This brings us to the next step. If you set this value too high, your server will freeze. If it's too low, users will wait forever. Here is how to find the sweet spot..."
6:00 - 8:30 Chapter 3: [Chapter Name]	[Visual Cue: B-roll of server monitoring dashboard showing a flatline turning into a healthy wave.]	"[Spoken Dialogue]: Once we applied this setting, look at what happened to the response times. They dropped from 800 milliseconds down to 45."
8:30 - 9:00 The Payoff	Show split screen: Before config vs After config load times.	"So, by changing just that one variable, we solved the crash problem completely without spending a single dollar on hardware upgrades."
9:00 - 9:30 Seamless CTA	[Visual Cue: On-screen card pops up pointing to a related video. Text overlay: 'Watch next: Scaling PostgreSQL Databases.']	"[Spoken Dialogue]: Now that your server is configured correctly, your next bottleneck is going to be database indexing. Click on this video right here where I break down indexing in under 5 minutes..."

---

4. Search-Optimized Metadata

• Video Description: [First 3 sentences containing key terms for search ranking. E.g., 'Learn how to optimize server performance and prevent database crashes. This step-by-step tutorial walks you through server configuration tweaks to save hosting costs.']
• Suggested Tags: server optimization, database configuration, web development, hosting costs, system architecture
• Call-to-Action Link: [Insert link to newsletter or product page]

---

Quality Checks

• Every title option is under 60 characters to prevent truncation on mobile devices.
• No generic intro fillers (e.g., "Welcome back to my channel," "Don't forget to like and subscribe") in the first 60 seconds of any hook or script section.
• Visual direction (B-roll, text overlays, zoom adjustments) is specified at least once every 10 seconds in the main script.
• Script transitions to the Call to Action immediately after the payoff without declaring "in conclusion" or "thank you for watching."
• Spoken audio lines are written in conversational language (short sentences, natural pauses, no overly academic jargon).

Anti-Patterns

• Do not write paragraphs of dialogue without accompanying visual cues. YouTube is a visual-first medium; every paragraph of speech needs visual transitions.
• Do not pitch sponsors, channel subscriptions, or external links during the hook (first 60 seconds).
• Do not create a single generic hook; always provide 3 distinct hook variations (Contrarian, Story, Pattern Interrupt) to give the creator flexibility.
• Do not use a generic outro that triggers the "viewer exit ramp" (e.g., "That's all for today's video, hope you enjoyed, see you next time!"). Suggest another video to keep viewers on the platform.

Example Trigger Phrases

• "Write a YouTube script about my personal productivity system."
• "Help me script a 10-minute video explaining inflation to college students."
• "I need a YouTube outline and script for a tutorial on clean code in Python."
• "Draft a retention-optimized YouTube script on how to build a SaaS in 2026."