Youtube Outliner

YouTube Video Outliner - Samin Yasar Style

Create YouTube video outlines that follow Samin's proven structure. Given a topic or concept, this skill produces a full video outline with hooks, frameworks, analogies, and practical walkthroughs.

When to Use

• User gives a video topic, concept, or idea
• User wants to plan a YouTube video
• User asks for a video outline or script structure
• User says "outline this video" or "plan this video"

Two Video Modes

Samin makes two types of videos. Identify which mode fits the topic:

Mode 1: Framework Video (Teaching a concept)

Used when: explaining a concept, teaching a skill, showing how to do something Examples: "Claude Just Replaced Doing Taxes Forever!", "How to Use Claude Code Better than 99% of People"

Mode 2: Build Walkthrough (Live demo/project)

Used when: building something live, showing a tool in action, walking through a project Examples: "Claude Just Changed Content Creation Forever!", "Claude Skills Just Changed AI Agents Forever!"

Many videos blend both - a framework structure with walkthrough demos at each step.

Mode 1: Framework Video Structure

1. HOOK (first 30 seconds)

Goal: Confirm the click. Make the viewer think "yes, this is what I need."

Pattern:

• Start with a relatable pain point or bold claim
• Immediately show visual proof or demo on screen (this is critical in Samin's niche - people need to SEE it working)
• Keep it under 30 seconds

Example (Taxes video):

"Tax season is right around the corner, and most people end up paying $300-$500 for an accountant they see once a year. Or they spend 3-5 hours fighting TurboTax. So I thought, what if I could just get Claude to do it for me?"

Formula:

[Relatable pain point or bold claim] + [What if AI could solve this?] + [Visual proof on screen]

NOTE: Do NOT default to financial angles (costs, savings, money). Lead with frustration, time waste, complexity, or a bold "what if" instead. Numbers are fine if natural, but never force a dollar amount into the hook.

2. TEASE (next 15-30 seconds)

Goal: Tell them exactly what they'll learn and give the framework name.

Pattern:

• "We'll be doing this in [N] steps"
• Name the framework with an acronym
• Preview each letter briefly
• Add credibility: "Even if you have zero technical background, you'll be able to do this"

Example:

"We'll be doing this in three steps. The GPS framework. G is Gather your documents. P is Process them with Claude. S is Send them to the IRS. And all we're doing is simply speaking to Claude."

Formula:

"We'll cover this in [N] steps using the [ACRONYM] framework."
[Brief one-liner for each letter]
"Even if [objection], you'll be able to do this because [reassurance]."

3. CONCEPT + ANALOGY (before each framework step)

Goal: Make the concept click before showing how.

Pattern:

• Explain the concept in 2-3 sentences
• Drop a short analogy or metaphor that makes it immediately tangible
• The analogy should be visual and relatable (hide and seek, chef in empty kitchen, filing cabinet, CPA vs genius)

Example (Connectors):

"Think of it like a game of hide and seek. The documents are hiding in Gmail, Google Drive, your computer. But Claude can't just walk into any room he wants. Every room has a lock on it. That's where connectors come in. A connector is basically a key."

Formula:

[What is the concept in plain language]
"Think of it like [vivid analogy]."
[Extend the analogy to explain how it works]

4. WALKTHROUGH/DEMO (for each framework step)

Goal: Show it working on screen.

Pattern:

• "So let me show you how to do that"
• Screen recording of the actual process
• Talk through what you're doing conversationally
• Call out what the viewer should see: "And you see right here..."
• If something goes wrong, show the fix (adds authenticity)

Formula:

"Let me show you how to do that."
[Screen demo with narration]
"And you can see [what happened]."
[Brief result/outcome]

5. REPEAT FOR EACH FRAMEWORK LETTER

Each letter/step follows the same sub-structure:

1. Name the step
2. Explain it (2-3 sentences)
3. Analogy to make it click
4. "Let me show you" walkthrough/demo
5. Brief result before transitioning to next step

6. CLOSE

• Brief recap of the framework
• Show the final result
• CTA (subscribe, community link, related video)

Mode 2: Build Walkthrough Structure

1. HOOK

• Show the end result first - visual proof of what was built
• "Every [thing] you're seeing was made by [doing X]"
• Or show the finished product demo

2. SETUP

• Brief context: what are we building and why
• "And to prove this actually works, I'm going to be using it for [this video / real project]"

3. LEVELS/BEATS

• Break the build into levels or milestones
• "First, we're going to [level 1]. Then [level 2]. Then [level 3]."
• Each level gets progressively more advanced

4. RIFF THROUGH EACH BEAT

For each level:

• Brief analogy if introducing a new concept
• Screen recording walkthrough
• Show the output at each stage
• Transition: "Now let's go deeper"

5. CLOSE

• Show the final complete build
• Recap what was built
• CTA

Analogy Bank (Samin's patterns)

Use these types of analogies - they should be visual, simple, and immediately relatable:

When creating outlines, generate a FRESH analogy for each concept that fits the topic. Don't reuse these exact ones.

Outline Template

When generating an outline, use this format:

# [VIDEO TITLE] - Outline

**Mode:** Framework / Build Walkthrough / Hybrid
**Framework:** [ACRONYM] - [What each letter stands for]
**Estimated Length:** [X] minutes
**Key Demo/Proof:** [What visual proof to show]

## HOOK (0:00 - 0:30)
- Pain point: [specific cost/time/frustration]
- Bold claim: [what we'll achieve]
- Visual proof: [what to show on screen]

## TEASE (0:30 - 1:00)
- Framework intro: [ACRONYM breakdown]
- Promise: "Even if [objection], you can do this because [reassurance]"

## [LETTER 1] - [Step Name] (1:00 - X:00)
- **Concept:** [2-3 sentence explanation]
- **Analogy:** [vivid metaphor]
- **Demo:** [what to show on screen]
- **Result:** [what the viewer sees after this step]

## [LETTER 2] - [Step Name] (X:00 - X:00)
- **Concept:** [explanation]
- **Analogy:** [metaphor]
- **Demo:** [screen walkthrough]
- **Result:** [outcome]

## [LETTER 3] - [Step Name] (X:00 - X:00)
- **Concept:** [explanation]
- **Analogy:** [metaphor]
- **Demo:** [screen walkthrough]
- **Result:** [outcome]

## CLOSE
- Recap framework
- Show final result
- CTA: [community link / subscribe / related video]

Example: Mapped from "Claude Just Replaced Doing Taxes Forever!" (16K views)

# Claude Just Replaced Doing Taxes Forever! - Outline

**Mode:** Framework + Walkthrough Hybrid
**Framework:** GPS - Gather, Process, Send
**Estimated Length:** 15 minutes
**Key Demo/Proof:** Real tax filing walkthrough with fake persona "Alex"

## HOOK (0:00 - 0:30)
- Pain point: "$300-$500 for an accountant you see once a year, or 3-5 hours fighting TurboTax"
- Bold claim: "What if I could just get Claude to do it for me?"
- Visual proof: Show Claude desktop opening up

## TEASE (0:30 - 1:00)
- Framework: "GPS framework - Gather, Process, Send"
- G: Gather your documents from everywhere
- P: Process them into Form 1040
- S: Send to IRS via FreeTaxUSA automatically
- "Even if you have zero technical background, all we're doing is speaking to Claude"

## G - GATHER (1:00 - 6:00)
- **Concept:** Before doing taxes, you need W2s, 1099s, mortgage docs, donation receipts. Normally scattered everywhere.
- **Analogy:** "Hide and seek. Documents are hiding in Gmail, Drive, your computer. Claude can't enter any room - every door is locked. Connectors are the keys."
- **Demo:** Setting up connectors (Gmail, Google Drive, computer access). Speaking to Claude: "Go find all tax documents for Alex."
- **Result:** Claude creates a folder with all gathered documents organized.

## P - PROCESS (6:00 - 10:00)
- **Concept:** Take all gathered docs and compile into Form 1040 (the government document).
- **Analogy:** "Think like an accountant - but Claude does the thinking."
- **Demo:** New Claude task scoped to the tax folder. "Process these into Form 1040 and tell me my expected return."
- **Result:** Claude generates the completed form with expected refund amount.

## S - SEND (10:00 - 14:00)
- **Concept:** Take the processed form and submit through FreeTaxUSA.
- **Analogy:** N/A (straight walkthrough)
- **Demo:** Claude opening browser, navigating FreeTaxUSA, filling in every field automatically.
- **Result:** Tax return ready to review and submit.

## CLOSE (14:00 - 15:00)
- Recap: "We gathered, processed, and sent - all by speaking to Claude"
- CTA: Community link, subscribe

Rules

• Every framework MUST have an acronym (3-5 letters)
• Every concept MUST have an analogy before the demo
• The hook SHOULD include a specific number if it fits naturally, but it's not required
• Visual proof in the first 30 seconds is non-negotiable
• Include "[Let me show you]" transition before every demo section
• Analogies should be fresh - never reuse the exact same one across videos
• For build walkthroughs, use "levels" (Level 1, Level 2, Level 3) instead of framework letters
• Always include a real or realistic example/persona to walk through (like "Alex" in the taxes video)
• NEVER use em dashes in any content