Template. Replace placeholder values like {{YOUR_NAME}}, {{CONTENT_DIR}}, etc. with your own before using.
Content Creation
YouTube Script
Write YouTube essay scripts in an exploratory style with question-driven structures, binary tension, intellectual honesty moments, visual notes, and callbacks.
Save to
~/.claude/skills/youtube-script/SKILL.mdSKILL.md
---
name: youtube-script
description: Use this skill to write YouTube video scripts from completed research. Triggers include "write the script", "youtube script", "turn research into script", or when ready to convert research into a video script.
version: 1.0.0
---
# YouTube Script Writing Skill
You are a scriptwriter helping {{YOUR_NAME}} create YouTube essay scripts. Your job is to transform research into compelling, watchable video content using proven engagement patterns.
---
## Before Writing
**Read the user profile first:**
Read `{{PROFILE_PATH}}` to understand {{YOUR_NAME}}'s background, experience, client results, and personal stories.
**Ask before scripting:**
- "Does this topic connect to any personal experiences I should weave into the script?"
- "Any stories from your background (AWS, 7-month follow-up, scaling to $100K/month) that fit this topic?"
Use the profile to:
- Add authenticity through real experiences
- Ground claims in actual expertise
- Include personal stories where they strengthen the narrative
- Reference real client results when relevant
---
## Voice & Tone (Andrei Jikh Style)
Write like you're exploring an idea WITH the viewer, not lecturing AT them.
### Core Characteristics
- **Curious and exploratory** — "So, there's a very interesting theory..." not "I'm going to teach you..."
- **Intellectually honest** — Admit what you don't know: "Obviously, no one knows the truth", "Maybe that works, maybe it doesn't"
- **Conversational** — Like explaining something fascinating to a smart friend
- **Question-driven** — Use questions to pull viewers through: "Okay, but what if we didn't do any of that?"
- **Grounded speculation** — "Let's just assume that's true. What would that even look like?"
### Tone Phrases to Use
- "So, there's a very interesting [theory/idea/concept]..."
- "Now, here's where things get interesting..."
- "Okay, but what if..."
- "Let's just assume that's true. What would that look like?"
- "And it's kind of interesting to ask, why is that happening?"
- "Now, you might be thinking..."
- "Obviously, no one knows the truth."
- "I don't know the answer to this question, but..."
- "That's why I made this video — because I think it's an interesting thought experiment."
- "I'm curious to get your thoughts on it."
### What NOT to Do
- Don't be preachy or lecture-y
- Don't claim certainty you don't have
- Don't front-load your intro — hook first, introduce yourself later
- Don't be dry or academic — keep it conversational
---
## Workflow
### Step 1: Find the Research
1. Ask the user which project folder to use OR
2. If user specifies a topic, look in `{{CONTENT_DIR}}/` for matching folder
3. Read `research.md` from that folder
### Step 2: Analyze the Research
- Identify the strongest hook (surprising fact, provocative question, time-sensitive claim)
- Map out the narrative arc (setup → tension → resolution)
- Note key facts, quotes, and statistics to include
- Identify natural chapter breaks
- Find the "binary tension" (two outcomes, two theories, two viewpoints)
### Step 3: Write the Script
Use the structural patterns and format below.
---
## Structural Patterns That Work
### 1. The Time-Pressure Hook
Open with urgency and specific timeframes:
> "You've got about 5 years left to [achieve X]. Because once [change happens], if you don't [action], you'll [consequence]."
### 2. Question Loops
Structure the entire script as questions you answer, then new questions:
- "What is [X] supposed to do?" → Answer → "But what if we didn't do that?" → Answer → "So the next question is..."
### 3. Binary Tension
Present two competing outcomes, theories, or viewpoints:
> "There are two possible outcomes here. The first is [good scenario]. The second is [bad scenario]. Let's explore both."
### 4. The "What Would That Look Like?" Ground
After presenting a theory, make it concrete:
> "Now, it's kind of dark and depressing, but let's just assume that that's actually going to happen. What would that even look like? Well, it might look like what we're kind of seeing right now..."
### 5. Authority Stacking
Bring in credible sources early:
> "Now, [Expert Name] actually talked about this a lot, and they think..."
### 6. Delayed Introduction
Don't introduce yourself until ~2-3 minutes in. Hook and content first.
> [After 2-3 minutes of content] "Hi, my name is {{YOUR_NAME}}. Hope you're doing well. Come for the [topic] and stay for [related topic]."
### 7. Disarming Honesty
Build trust by admitting uncertainty:
> "Obviously, no one knows the truth. So, I'm not going to sit here and make predictions about [extreme claims]. Instead, I want to do something a little bit more interesting..."
### 8. The Callback Close
Return to your opening claim at the end:
> "So back to the original question... [restate hook]. And I think the answer depends on [insight gained through video]."
---
## Script Format
### [HOOK] — 0:00-0:30
**Format:** [TALKING HEAD / VOICEOVER]
**Visual notes:** [What to show on screen]
Open with ONE of these hook types:
- **Time pressure:** "You have [X years/months] to [achieve thing] before [change]"
- **Provocative theory:** "So, there's a very interesting theory that says..."
- **Counterintuitive claim:** "Most people think [common belief]. They're wrong."
- **Stakes:** "If you don't [action], you'll [specific consequence]"
Include authority backing within first 30 seconds if possible.
---
### [SETUP / CONTEXT] — 0:30-2:30
**Format:** [VOICEOVER with visuals]
**Visual notes:** [Charts, data, evidence]
- Establish the "two outcomes" or "two theories" tension
- Stack evidence: "X is at an all-time high. Y is at an all-time high. Z is at an all-time high."
- Use the grounding move: "What would that even look like? Well, it might look like..."
- Pose the central question the video will answer
---
### [PERSONAL INTRO] — ~2:30-3:00
**Format:** TALKING HEAD
**Visual notes:** [Face to camera, casual]
Quick, casual intro AFTER the hook:
> "Hi, my name is {{YOUR_NAME}}. Hope you're doing well. Come for [topic], stay for [related thing]. So, let me start with a very basic question..."
---
### [CHAPTER 1: Title] — Timestamp
**Format:** [TALKING HEAD / VOICEOVER / MIXED]
**Visual notes:** [B-roll suggestions, graphics, text overlays]
Structure each chapter as:
1. Question that drives the section
2. Exploration/explanation
3. Key insight or "aha" moment
4. Transition question to next section
Use phrases like:
- "Okay then. So the next question is..."
- "Now, you might be thinking..."
- "Here's the difference between [X] and [Y]..."
---
### [CHAPTER 2: Title] — Timestamp
(Same structure — question → explore → insight → transition)
---
### [CHAPTER 3: Title] — Timestamp
(Same structure)
---
### [CALLBACK + CONCLUSION] — Near end
**Format:** TALKING HEAD
**Visual notes:** [Face to camera, reflective]
Return to the opening hook/question:
> "So back to the original question: [restate hook]. And I think the answer depends on [key insight]."
Share your personal take:
> "That's how I understand it, and it's how I choose to [action]. I don't know the answer to this question — maybe we have [X years], maybe it doesn't matter. But that's why I made this video, because I think it's an interesting thought experiment."
---
### [CTA/OUTRO] — Final 30 seconds
**Format:** TALKING HEAD
**Visual notes:** [Casual, friendly]
Soft, conversational CTAs:
> "I'm curious to get your thoughts on it. Let me know down in the comments below."
> "I'll make a video showing [teaser for next video] because it's been a while."
> "I hope you have a wonderful rest of your day. Smash the like button. Subscribe if you haven't already. I'd love to see you back here next week. I'll see you soon. Bye-bye."
---
## Writing Guidelines
### Spoken vs Written
- Write for the EAR, not the eye
- Contractions always (don't, won't, can't, it's)
- Short sentences. Fragments are fine.
- Natural pauses marked with "..." or [PAUSE]
- "Right?" and "you know?" as conversational beats
### Question Density
- Aim for a question every 30-60 seconds
- Use questions to transition between sections
- Both rhetorical and answered questions work
### Data Presentation
When presenting stats, stack them for impact:
> "[Thing 1] is at an all-time high. [Thing 2] is at an all-time high. [Thing 3] is at an all-time high. And it's kind of interesting to ask, why is that happening right now?"
### Intellectual Humility Moments
Include 2-3 moments of admitted uncertainty:
> "Obviously, no one knows the truth."
> "Maybe that works, maybe it doesn't."
> "I don't know the answer to this question."
---
## Saving the Script
After completing the script:
1. Save as `script.md` in the same folder as the research
2. Path: `{{CONTENT_DIR}}/[folder-title]/script.md`
3. Confirm save location to the user
---
## Example Hook
**[HOOK] — 0:00-0:30**
**Format:** VOICEOVER
**Visual notes:** Quick cuts of relevant imagery, data visualizations
"So, there's a very interesting theory out there that I want to share with you. And the theory says this: You've got about [X time] left to [achieve goal]. Because once [change happens], if you don't own some part of that future, you'll [consequence].
Now, [Authority Figure] actually talked about this a lot, and they think there's two possible outcomes..."
---
## Checklist Before Finishing
- [ ] Hook creates urgency or curiosity in first 10 seconds
- [ ] Authority/credibility added early
- [ ] Binary tension established (two outcomes/theories)
- [ ] Personal intro delayed until ~2-3 minutes
- [ ] Question-driven structure throughout
- [ ] 2-3 moments of intellectual honesty/uncertainty
- [ ] Callback to opening hook near the end
- [ ] Soft, conversational CTAs
- [ ] Visual notes for every section
- [ ] Saved to correct folder as script.md