youtube-titles-thumbnails

Original source / Raw SKILL.md

---
name: youtube-titles-thumbnails
description: >
  Create high-performing YouTube titles and thumbnail text that maximize CTR and virality
  while maintaining authenticity. Use when analyzing video transcripts to generate title
  and thumbnail suggestions, optimizing existing titles/thumbnails, or when users request
  help with YouTube content strategy for click-through rate optimization.
allowed-tools: AskUserQuestion
---

# YouTube Titles & Thumbnails

Generate titles and thumbnail text that drive clicks while maintaining viewer trust and satisfaction.

## Philosophy: The Curiosity-Value Framework

YouTube success depends on creating **irresistible curiosity** while **promising clear value**. The title and thumbnail work as a complementary pair, not duplicates.

**Mental Model: The Curiosity Equation**

```
Thumbnail (Visual Hook) + Title (Verbal Promise) = Irresistible Curiosity Gap
```

- **Thumbnail text**: Creates emotional response and intrigue (3-5 words max)
- **Title**: States the promise or value proposition (what they'll learn/get)
- **Together**: Create curiosity gap that demands clicking

### Core Principles

1. **Complementarity over Redundancy**: Title and thumbnail should reinforce each other, not repeat the same information
2. **Neutrality Builds Trust**: Neutral language ("The Real Reason...") outperforms hype ("YOU WON'T BELIEVE...")
3. **Specificity Beats Generic**: "3 Python Tricks for Async" > "Python Tips"
4. **Strategic Curiosity Gap**: Promise value without revealing the answer
5. **Conceptual Alignment**: Thumbnail and title must tell the same story

**Exception**: Strategic redundancy is acceptable for SEO when the keyword is critical for discovery.

---

## Interactive Discovery: Clarifying Questions

Before generating titles and thumbnails, use the **AskUserQuestion** tool to gather context that shapes the output. This ensures recommendations are tailored to the creator's specific needs rather than generic advice.

### When to Ask Questions

**Always ask when:**
- User provides only a transcript without context
- User asks for title/thumbnail help without specifying constraints
- User's niche or audience is unclear
- Multiple valid approaches exist

**Skip questions when:**
- User has already specified their constraints clearly
- User explicitly asks for quick suggestions
- User provides detailed context upfront

### Clarifying Question Flow

Use AskUserQuestion to gather essential context through targeted questions. Ask 2-4 questions maximum per interaction to avoid overwhelming the user.

#### Question Set 1: Content Context

**Question 1 - Content Type:**
```
Question: "What type of video is this?"
Header: "Content type"
Options:
  - Tutorial (Teaching a skill or concept)
  - Analysis/Opinion (Hot take, industry insight, critique)
  - Story/Experience (Personal journey, lessons learned)
  - Comparison (X vs Y, reviews, alternatives)
```

**Question 2 - Target Audience:**
```
Question: "Who is your target viewer?"
Header: "Audience"
Options:
  - Beginners (New to the topic, needs clarity)
  - Intermediate (Has basics, wants depth)
  - Advanced (Experts, wants nuance and novelty)
  - Mixed (Broad appeal needed)
```

#### Question Set 2: Emotional Hook & Strategy

**Question 3 - Primary Emotional Hook:**
```
Question: "What emotion should drive clicks?"
Header: "Hook"
Options:
  - Curiosity (I need to know what happens)
  - Frustration relief (Finally, someone addresses my pain)
  - Ambition (This will level me up)
  - FOMO (I can't miss this insight)
```

**Question 4 - SEO vs Creativity Priority:**
```
Question: "What's more important for this video?"
Header: "Priority"
Options:
  - Discovery (SEO keywords matter most)
  - Click-through (Curiosity and intrigue matter most)
  - Balanced (Equal weight on both)
```

#### Question Set 3: Channel Context (Optional, for New Users)

**Question 5 - Channel Tone:**
```
Question: "What's your channel's personality?"
Header: "Tone"
Options:
  - Authoritative (Expert, credible, professional)
  - Casual (Friendly, approachable, conversational)
  - Provocative (Contrarian, debate-starting, bold)
  - Educational (Teacher-like, methodical, clear)
```

**Question 6 - Competitive Differentiation:**
```
Question: "What makes this video different from others on the topic?"
Header: "Differentiator"
Options:
  - Unique angle (Perspective no one else has)
  - Better depth (More comprehensive than competitors)
  - Simpler approach (Clearer than existing content)
  - Fresh data/research (New information or insights)
```

### Conditional Follow-Up Questions

Based on initial answers, ask follow-up questions when needed:

**If content type is "Comparison":**
```
Question: "Does the comparison have a clear winner?"
Header: "Winner?"
Options:
  - Yes, one is clearly better (Definitive recommendation)
  - No, it depends on context (Nuanced, "it depends" answer)
  - Surprising winner (Common choice isn't actually best)
```

**If audience is "Beginners":**
```
Question: "Should the title signal beginner-friendliness?"
Header: "Signal level"
Options:
  - Yes, explicitly (Use "for Beginners", "Complete Guide")
  - No, keep it aspirational (Beginners still want to feel capable)
  - Subtle hint (Use simpler language without labels)
```

**If emotional hook is "Frustration relief":**
```
Question: "What's the main frustration you're addressing?"
Header: "Pain point"
Options:
  - Common mistake everyone makes
  - Misleading advice from others
  - Overcomplicated approaches
  - Missing piece no one explains
```

### Using Answers to Shape Output

After gathering answers, apply them directly to title/thumbnail generation:

| Answer | Impact on Title/Thumbnail |
|--------|---------------------------|
| **Tutorial** content | Use "How to", numbered patterns, outcome-focused |
| **Advanced** audience | Avoid "Beginner" signals, use specific jargon |
| **Curiosity** hook | Use revelation patterns: "The Real Reason...", "What Nobody..." |
| **Discovery** priority | Front-load SEO keywords, accept some redundancy |
| **Provocative** tone | Stronger statements, contrarian takes, debate-starters |
| **Unique angle** differentiator | Emphasize perspective in title, thumbnail shows stance |

### Example Question Flow

**User provides:** "I made a video about why I switched from React to Vue after 5 years. Can you help with the title and thumbnail?"

**Claude uses AskUserQuestion:**

```
Questions to ask in first call:

1. Content type: Story/Experience (likely, but confirm)
2. Target audience: Intermediate developers (likely)
3. Emotional hook: Curiosity or FOMO (developers care about framework choices)
4. Priority: Probably balanced (framework keywords matter, but intrigue is key)
```

**After answers received, generate titles/thumbnails that align:**

If user chose "Curiosity" + "Provocative" + "Unique angle":
- Thumbnail: "Why I Left React"
- Title: "5 Years of React: The Problems Nobody Talks About"

If user chose "FOMO" + "Authoritative" + "Fresh data":
- Thumbnail: "React vs Vue 2024"
- Title: "What 5 Years of React Development Actually Taught Me About Vue"

---

## Before Creating Titles and Thumbnails

Analyze the content to understand:

- **Core Value**: What's the single most valuable insight/outcome from this video?
- **Target Audience**: Who is this for? What level? (beginner, intermediate, advanced)
- **Emotional Hook**: What emotion drives clicks? (curiosity, frustration, ambition, fear of missing out)
- **Content Type**: Tutorial, analysis, story, showcase, comparison, revelation?
- **Niche Context**: What works in this specific niche? What's oversaturated?

Good answers shape effective title-thumbnail pairs.

---

## Title Guidelines

### Structure Patterns

**1. Curiosity + Specificity**
```
"The Real Reason [Specific Thing] [Unexpected Outcome]"
"Why [Expert/Company] [Surprising Action]"
"What [Authority] Got Wrong About [Topic]"
```

Examples:
- "The Real Reason Senior Developers Use Vim"
- "Why Google Abandoned Their Own Framework"
- "What Most Tutorials Get Wrong About React Hooks"

**2. Value Promise + Constraint**
```
"[Number] [Specific Things] That [Outcome]"
"How to [Outcome] Without [Common Approach]"
"[Outcome] in [Time/Effort Constraint]"
```

Examples:
- "3 Python Patterns That Make Async Code Readable"
- "How to Learn TypeScript Without JavaScript Fatigue"
- "Master Git Rebase in 10 Minutes"

**3. Revelation + Context**
```
"[Something] Is Not What You Think"
"The Hidden [Aspect] of [Popular Thing]"
"What Nobody Tells You About [Topic]"
```

Examples:
- "Microservices Are Not What You Think"
- "The Hidden Cost of Premature Optimization"
- "What Nobody Tells You About Learning to Code"

**4. Comparison + Insight**
```
"[Thing A] vs [Thing B]: [Unexpected Insight]"
"Why [Thing] Is Better Than [Expected Alternative]"
```

Examples:
- "REST vs GraphQL: The Choice Nobody Talks About"
- "Why Boring Technology Is Better Than Cutting Edge"

### Title Best Practices

✅ **Use neutral, conversational tone**
- "The Problem with Redux" ✅
- "Redux WILL DESTROY YOUR APP!!!" ❌

✅ **Be specific, not generic**
- "3 TypeScript Utility Types That Simplify APIs" ✅
- "TypeScript Tips and Tricks" ❌

✅ **Front-load important words** (first 50 characters visible in search)
- "Rust Memory Safety Without Garbage Collection" ✅
- "How I Learned That Rust Has Memory Safety Without Garbage Collection" ❌

✅ **Use power words strategically**
- Neutral: Real, Hidden, Actually, Nobody, Most, Wrong
- Action: Master, Build, Create, Fix, Solve
- Outcome: Without, Faster, Better, Simple, Clean

✅ **Keep length practical**
- Optimal: 40-70 characters (fully visible)
- Maximum: 100 characters (truncates after)

---

## Thumbnail Text Guidelines

Thumbnail text creates the **emotional hook** that complements the title's **verbal promise**.

### Core Rules

**3-5 Words Maximum**
- 3 words: "React Hooks Explained"
- 4 words: "The Redux Anti-Pattern"
- 5 words: "Why Experts Avoid Classes"
- 6+ words: Too hard to read ❌

**Neutral Voice Preferred**
- "The Real Cost" ✅
- "SHOCKING TRUTH!!!" ❌
- "Hidden Problem" ✅
- "YOU'RE DOING IT WRONG!" ❌

**Exception**: Expressive language allowed when it's authentic to the content tone (e.g., "Mind-Blowing" for genuinely surprising technical insight)

### Thumbnail Text Patterns

**1. The Subject Focus**
```
[Core Topic]
[Specific Technology]
[Person/Company Name]
```

Examples:
- "GraphQL"
- "Next.js 15"
- "Linus Torvalds"

Use when: Title provides the context/promise

**2. The Revelation**
```
"The Real [X]"
"Hidden [X]"
"The Truth About [X]"
```

Examples:
- "The Real Problem"
- "Hidden Costs"
- "The Truth"

Use when: Title specifies what the revelation is about

**3. The Status/Opinion**
```
"[Tech] Is [Status]"
"Why [Action]"
"[Comparison]"
```

Examples:
- "Async Is Hard"
- "Why I Quit"
- "Vim vs VSCode"

Use when: Provocative enough to create curiosity

**4. The Question**
```
"Why [X]?"
"What Is [X]?"
"When [X]?"
```

Examples:
- "Why Rust?"
- "What Is DX?"
- "When to Scale?"

Use when: Title answers the question

**5. The Action/Command**
```
"[Verb] [Object]"
"Stop [X]"
"Start [X]"
```

Examples:
- "Rethink Redux"
- "Stop Using Classes"
- "Start Simple"

Use when: Title provides the method/reason

---

## Title-Thumbnail Complementarity

The key to high CTR is creating a complementary relationship where **neither alone tells the full story**.

### Complementary Patterns

**Pattern 1: Thumbnail = Topic, Title = Promise**

Thumbnail: "React Hooks"
Title: "Why Senior Developers Avoid useState"

Why it works: Thumbnail identifies subject, title creates curiosity gap

**Pattern 2: Thumbnail = Question, Title = Teaser Answer**

Thumbnail: "Why Rust?"
Title: "What C++ Developers Wish They Knew Earlier"

Why it works: Thumbnail poses question, title hints at answer without revealing

**Pattern 3: Thumbnail = Status, Title = Context**

Thumbnail: "Redux Is Dead"
Title: "The State Management Tool Actually Worth Learning in 2024"

Why it works: Provocative thumbnail, title provides nuance and specificity

**Pattern 4: Thumbnail = Person/Entity, Title = Revelation**

Thumbnail: "Google"
Title: "Why Google Killed Their Best Developer Tool"

Why it works: Thumbnail shows who, title reveals what/why

**Pattern 5: Thumbnail = Emotion, Title = Specificity**

Thumbnail: "The Hidden Problem"
Title: "What 10,000 Hours of Coding Taught Me About Abstractions"

Why it works: Thumbnail creates intrigue, title provides credibility and scope

### Avoid Redundancy (Unless SEO)

❌ **Redundant** (wastes space):
```
Thumbnail: "How to Learn Python"
Title: "How to Learn Python for Beginners"
```

✅ **Complementary**:
```
Thumbnail: "Python for Beginners"
Title: "The 3 Concepts That Actually Matter"
```

✅ **Strategic redundancy for SEO**:
```
Thumbnail: "TypeScript Tutorial"
Title: "TypeScript Tutorial: The Parts Everyone Gets Wrong"
```
(Keyword "TypeScript Tutorial" helps discovery, but title adds differentiation)

---

## Anti-Patterns to Avoid

### ❌ Misleading Clickbait

```
Thumbnail: "I Got FIRED"
Title: "The JavaScript Pattern That Cost Me My Job"
Content: Not actually about getting fired
```

**Why bad**: Destroys trust, hurts retention, damages channel long-term

**Better**:
```
Thumbnail: "Career Mistake"
Title: "The Code Review Comment That Changed My Career"
```

### ❌ Generic Titles

```
"Python Tips and Tricks"
"How to Learn JavaScript"
"Web Development Tutorial"
```

**Why bad**: No differentiation, low CTR, unclear value

**Better**:
```
"3 Python Patterns That Make Code Self-Documenting"
"How to Learn JavaScript Without Tutorial Hell"
"The Web Development Approach Big Tech Actually Uses"
```

### ❌ Excessive Thumbnail Text

```
Thumbnail: "THE SHOCKING TRUTH ABOUT REACT"
```

**Why bad**: Too long to read at thumbnail size, visually cluttered

**Better**:
```
Thumbnail: "React's Problem"
```

### ❌ Hype Without Substance

```
Thumbnail: "MIND-BLOWING!!!"
Title: "This Will CHANGE EVERYTHING About Coding FOREVER!!!"
```

**Why bad**: Overpromises, feels like spam, attracts wrong audience

**Better**:
```
Thumbnail: "The Shift"
Title: "Why Experienced Developers Write Less Code"
```

### ❌ Title-Thumbnail Mismatch

```
Thumbnail: "Python vs JavaScript"
Title: "Why I Quit My Job to Learn Rust"
```

**Why bad**: Confusing, breaks trust, unclear what video is about

**Better**: Align them
```
Thumbnail: "Why Rust?"
Title: "What Python Developers Discover After Learning Rust"
```

### ❌ No Curiosity Gap

```
Thumbnail: "Async/Await Tutorial"
Title: "Complete Guide to Async/Await in JavaScript"
```

**Why bad**: No intrigue, no reason to click vs other tutorials

**Better**:
```
Thumbnail: "Async Secrets"
Title: "The Async/Await Patterns Senior Developers Actually Use"
```

---

## Content Type Adaptation

**IMPORTANT**: Vary your approach based on content type. No single formula works for everything.

### Tutorial Content

**Focus**: Clear value promise + outcome

Thumbnail approaches:
- "[Technology]" (if well-known)
- "Learn [X]"
- "From Zero" (for beginners)

Title patterns:
- "How to [Outcome] with [Technology]"
- "[Technology]: The [Approach] That Actually Works"
- "Master [Specific Skill] in [Timeframe]"

Example:
```
Thumbnail: "Docker Basics"
Title: "Docker for Developers Who've Never Used Containers"
```

### Analysis/Opinion Content

**Focus**: Insight + perspective

Thumbnail approaches:
- "The Truth"
- "Hidden [X]"
- "[Opinion/Status]"

Title patterns:
- "Why [Popular Thing] Is [Unexpected Take]"
- "What [Group] Get Wrong About [Topic]"
- "The Real Reason [Phenomenon]"

Example:
```
Thumbnail: "The Microservices Trap"
Title: "Why Smart Teams Are Choosing Monoliths in 2024"
```

### Story/Experience Content

**Focus**: Relatability + lesson

Thumbnail approaches:
- "My Mistake"
- "The Lesson"
- "[Emotional State]"

Title patterns:
- "What [Experience] Taught Me About [Lesson]"
- "How [Event] Changed My [Outcome]"
- "The [Experience] Nobody Talks About"

Example:
```
Thumbnail: "I Failed"
Title: "What 6 Failed Startups Taught Me About Code Quality"
```

### Comparison Content

**Focus**: Decision clarity + insight

Thumbnail approaches:
- "[A] vs [B]"
- "The Choice"
- "What to Pick"

Title patterns:
- "[A] vs [B]: The Decision Matrix Nobody Shows"
- "When to Choose [A] Over [B]"
- "Why [Group] Prefer [Unexpected Choice]"

Example:
```
Thumbnail: "SQL vs NoSQL"
Title: "The Database Decision That Scales with Your Startup"
```

---

## Optimizing for CTR and Virality

### CTR Optimization

**Test multiple variations** mentally before committing:

1. **Specificity test**: Can you make it more specific?
   - "APIs" → "REST APIs" → "REST API Versioning"

2. **Curiosity test**: Does it create a gap?
   - "How Redux Works" → "Why Redux Works Differently Than You Think"

3. **Value test**: Is the outcome clear?
   - "JavaScript Patterns" → "3 JavaScript Patterns That Prevent Bugs"

4. **Audience test**: Does it speak to a specific person?
   - "Learn Coding" → "Learn Coding After 30"

### Virality Factors

**Shareability**: Would viewers share this?
- Contrarian insights ("Why Popular Thing Is Wrong")
- Surprising revelations ("The Hidden Cost of X")
- Practical value ("The Pattern That Saved Me Hours")

**Conversation-starting**: Does it spark debate?
- Opinion pieces: "Tailwind Is Better Than Writing CSS"
- Comparisons: "When Microservices Make Things Worse"

**Social proof triggers**:
- Authority: "What [Expert] Gets Right About [Topic]"
- Consensus-breaking: "Why Everyone Is Wrong About [Topic]"
- Results: "How [Outcome] in [Constraint]"

---

## Workflow: From Transcript to Title/Thumbnail

### Step 1: Gather Context via Interactive Questions

Before analyzing content, use AskUserQuestion to understand constraints:

```
Use AskUserQuestion with these questions:

Question 1:
- question: "What type of video is this?"
- header: "Content type"
- options:
  - Tutorial (Teaching a skill or concept)
  - Analysis/Opinion (Hot take, industry insight, critique)
  - Story/Experience (Personal journey, lessons learned)
  - Comparison (X vs Y, reviews, alternatives)

Question 2:
- question: "Who is your target viewer?"
- header: "Audience"
- options:
  - Beginners (New to the topic, needs clarity)
  - Intermediate (Has basics, wants depth)
  - Advanced (Experts, wants nuance and novelty)
  - Mixed (Broad appeal needed)

Question 3:
- question: "What emotion should drive clicks?"
- header: "Hook"
- options:
  - Curiosity (I need to know what happens)
  - Frustration relief (Finally, someone addresses my pain)
  - Ambition (This will level me up)
  - FOMO (I can't miss this insight)

Question 4:
- question: "What's more important for this video?"
- header: "Priority"
- options:
  - Discovery (SEO keywords matter most)
  - Click-through (Curiosity and intrigue matter most)
  - Balanced (Equal weight on both)
```

Skip this step if user has already provided this context explicitly.

### Step 2: Extract Core Value

Read transcript/content and identify:
- The single most valuable insight or outcome
- The "aha moment" viewers will experience
- What makes this video worth watching

### Step 3: Apply Context to Pattern Selection

Based on AskUserQuestion answers, select appropriate patterns:

| Content Type | Preferred Title Patterns | Preferred Thumbnail Patterns |
|--------------|-------------------------|------------------------------|
| Tutorial | "How to [Outcome]", "[Number] [Things] That [Result]" | Subject Focus, Action/Command |
| Analysis/Opinion | "The Real Reason...", "Why [Thing] Is [Take]" | Revelation, Status/Opinion |
| Story/Experience | "What [Experience] Taught Me...", "How [Event] Changed..." | Status/Opinion, Question |
| Comparison | "[A] vs [B]: [Insight]", "When to Choose [A] Over [B]" | "[A] vs [B]", Question |

| Audience Level | Adaptations |
|----------------|-------------|
| Beginners | Simpler language, explicit value signals, avoid jargon |
| Intermediate | Balance clarity with specificity, show depth |
| Advanced | Precise terminology, nuanced insights, novelty signals |
| Mixed | Clear language but sophisticated insights |

| Emotional Hook | Title/Thumbnail Emphasis |
|----------------|--------------------------|
| Curiosity | Revelation patterns, strategic gaps, "hidden" language |
| Frustration relief | Problem-solution framing, "finally" signals |
| Ambition | Outcome-focused, skill-building, mastery language |
| FOMO | Urgency, trend signals, "what others know" framing |

### Step 4: Draft Options

Draft 3-5 title options using patterns that match the gathered context:
- Each title should use a different pattern approach
- Ensure variety in structure and emphasis
- All options should align with audience level and emotional hook

### Step 5: Create Complementary Thumbnail Text

For each title, draft complementary thumbnail text (3-5 words):
- Thumbnail and title should reinforce, not repeat
- Match the emotional hook to the thumbnail pattern
- Consider visual context (face, product, reaction)

### Step 6: Validate Quality

Test each title/thumbnail pair:
- **Complementarity**: Do they reinforce without repeating?
- **Curiosity gap**: Is there a reason to click?
- **Value clarity**: Is the promise clear?
- **Anti-patterns**: No misleading, generic, or mismatched content?
- **Context alignment**: Does it match the answers from Step 1?

### Step 7: Present Recommendations

Present options with context:
- Lead with the strongest option for their stated priorities
- Explain why each option fits their audience/hook/priority
- Note trade-offs (e.g., "This is better for SEO but slightly less intriguing")

---

## Quality Checklist

Before finalizing, verify:

**Title**:
- [ ] Uses neutral, conversational tone (not hype)
- [ ] Specific rather than generic
- [ ] Front-loads important keywords (first 50 chars)
- [ ] Creates curiosity gap without misleading
- [ ] 40-70 characters (optimal) or <100 (maximum)
- [ ] Promises clear value or insight

**Thumbnail Text**:
- [ ] 3-5 words maximum
- [ ] Neutral voice preferred (expressive when authentic)
- [ ] Large enough to read at thumbnail size
- [ ] Creates emotional hook or identifies subject

**Complementarity**:
- [ ] Title and thumbnail reinforce each other
- [ ] Neither alone tells full story
- [ ] No redundancy (unless strategic for SEO)
- [ ] Conceptually aligned
- [ ] Together create irresistible curiosity gap

**Authenticity**:
- [ ] Accurately represents content
- [ ] No misleading promises
- [ ] Maintains viewer trust
- [ ] Builds channel credibility

---

## Variation Guidance

**IMPORTANT**: Title and thumbnail strategies should vary based on:

- **Content niche**: Tech tutorials vs personal growth vs entertainment
- **Audience sophistication**: Beginners need clarity, experts need nuance
- **Video goal**: Education vs entertainment vs persuasion
- **Channel brand**: Authoritative vs casual vs provocative
- **Competitive landscape**: Differentiate from oversaturated approaches

**Avoid converging on favorite patterns**:
- Don't always use "The Real Reason..." format
- Don't default to "X vs Y" for every comparison
- Vary between different title structures
- Mix emotional hooks in thumbnails

Each video deserves a fresh approach based on its unique value and context.

---

## Remember

**Title + Thumbnail = Trust + Curiosity**

The best YouTube titles and thumbnails:
- Create irresistible curiosity without misleading
- Promise clear value with specificity
- Work as complementary pairs, not redundant duplicates
- Use neutral language that builds long-term trust
- Adapt to content type and audience context

**The Interactive Workflow:**
1. **Ask first** — Use AskUserQuestion to gather context before generating
2. **Tailor output** — Apply answers to select appropriate patterns
3. **Explain choices** — Help users understand why recommendations fit their needs

These are not templates to fill in—they're frameworks to think with. Use judgment, know your audience, and prioritize viewer satisfaction over short-term clicks.

**Great titles and thumbnails get clicks. Authentic titles and thumbnails get clicks AND keep viewers coming back.**