Master Ira Glass's narrative storytelling methodology from This American Life to create podcasts that captivate listeners through the power of story. Use when: Creating a branded podcast or audio content series; Structuring episodes for maximum listener engagement; Transforming raw interviews into compelling narratives; Building thought leadership through audio storytelling; Planning podcast content that keeps audiences coming back
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill podcast-production
> Master Ira Glass's narrative storytelling methodology from This American Life to create podcasts that captivate listeners through the power of story.
Source: Ira Glass - This American Life (1995-present)
Core Principle: Every great audio story alternates between two essential building blocks: the anecdote (a sequence of actions) and moments of reflection (what it all means). "The anecdote is the most important thing... it's a story in its purest form, one thing following another."
Why This Matters: Most podcasts fail because they're just people talking. Ira Glass's methodology, refined over 30+ years and thousands of episodes, creates the emotional engagement that turns casual listeners into devoted fans. As Alex Blumberg (Gimlet Media founder) learned from Glass: "Anything that is really informative but wasn't fun to listen to, that's a lose."
| Claude Does | You Decide |
|-------------|------------|
| Structures production workflow | Final creative direction |
| Suggests technical approaches | Equipment and tool choices |
| Creates templates and checklists | Quality standards |
| Identifies best practices | Brand/voice decisions |
| Generates script outlines | Final script approval |
Help me structure a podcast episode about [topic] using Ira Glass's storytelling method.
Target length: [X] minutes
Format: [narrative/interview/hybrid]
I have a raw interview transcript. Help me identify the story threads and structure this into a compelling episode using anecdote + reflection.
[paste transcript excerpt]
Review this episode outline for storytelling effectiveness:
[paste outline]
When applying Ira Glass's methodology, follow these principles:
Every episode needs a story engine - the question or tension that pulls listeners through.
## Story Engine Template
**Central Question**: What question will listeners desperately want answered?
**Stakes**: Why does the answer matter? What's at risk?
**Tension**: What obstacles or conflicts create suspense?
**Promise**: What transformation or insight will listeners gain?
Key considerations:
The anecdote is a sequence of actions that moves forward in time. It answers: "And then what happened?"
## Anecdote Structure
**Opening Hook** (first 30 seconds):
- Drop listener into action immediately
- Raise a question or create intrigue
- Avoid "In this episode, we'll discuss..."
**Action Sequence**:
1. [First thing that happened]
2. [Then this happened]
3. [Which led to this...]
4. [Until finally...]
**Bait**: Every few paragraphs, raise a question that makes listeners want to keep listening.
**The Turn**: The moment when everything changes - the twist, revelation, or pivot.
Ira Glass's Rule: "You're constantly raising questions and answering them. The power of the anecdote is so great that you can hold people's attention just by telling a sequence of events."
Reflection is the "so what?" - the meaning behind the story.
## Reflection Placement
**After key story beats**: Pause to let the moment land
- "And that's when I realized..."
- "What makes this significant is..."
- "The thing about [topic] that most people miss..."
**Balance ratio**: Roughly 60% anecdote, 40% reflection
**Types of reflection**:
- Personal insight (what you learned)
- Universal truth (what this means for everyone)
- Expert analysis (what the research shows)
- Emotional processing (how it felt)
Critical: Reflection must feel earned. Don't tell listeners what to think until you've shown them the story that leads to that conclusion.
## Episode Arc Template
**ACT 1: Setup (10-15% of runtime)**
- Cold open: Start in the middle of action
- Introduce the question/tension
- Establish stakes
- "Signpost" what's coming (optional)
**ACT 2: Complication (60-70% of runtime)**
- Follow the anecdote sequence
- Introduce obstacles and setbacks
- Build tension through the middle
- Include 2-3 "movements" (distinct story beats)
- Each movement should feel complete but raise new questions
**ACT 3: Resolution (15-20% of runtime)**
- The turn/revelation
- Meaningful reflection on what it all means
- Emotional landing
- Future implication or call to action
Alex Blumberg's "good tape" criteria - the moments that make compelling audio:
## Good Tape Checklist
□ **Authentic emotion** - Real laughter, tears, surprise
□ **Unexpected honesty** - Moments of vulnerability
□ **Sound of thinking** - Person working through an idea in real-time
□ **Concrete details** - Specific, sensory descriptions
□ **Natural speech** - Not rehearsed, polished, or performative
□ **Tension in the voice** - You can hear the stakes
□ **The "aha" moment** - Realization happening live
Red flags for "bad tape":
## Audio Writing Rules
**Sentence structure**:
- Short sentences. Punchy.
- One idea per sentence.
- Use contractions (don't, won't, it's)
- Write how people actually talk
**Avoid**:
- Parenthetical asides (like this one)
- Complex subordinate clauses
- Jargon without explanation
- Long lists (max 3 items spoken)
**Read aloud test**:
- If you stumble, rewrite
- If it sounds formal, rewrite
- If you run out of breath, break it up
Context: A software company wants to create an episode about customer success stories.
Input:
> Help me structure a podcast episode about how a manufacturing company saved $2M using our inventory software.
Output:
*Start in crisis:*
"It was 3 AM when Maria got the call. The warehouse had just shipped $400,000 worth of product to the wrong customer. For the third time that quarter. Her father, who'd built the company from nothing, was on the other end of the line. And for the first time in her life, she heard him say: 'I don't know if we can survive this.'"
Movement 1: Discovery
Movement 2: The Bet
Movement 3: The Turn
Why this works: We're not selling software—we're telling a story about family, legacy, and change. The software is the vehicle, not the destination.
Context: A marketing consultant hosts a podcast interviewing industry experts.
Input:
> I interviewed a CMO for 45 minutes. Help me identify the narrative threads and structure this into a compelling 25-minute episode.
Output:
Scan the transcript for:
From the transcript, I'd look for the ONE story that:
Cold Open: Pull the most compelling 30-second clip
Introduction (after cold open):
Story Sequence (edited from 45 min to ~18 min):
Reflection segments:
Close:
Keep: Moments of authentic emotion, specific details, unexpected insights
Cut: Rambling explanations, repeated points, "um" and filler, anything you could read faster
Context: Creating a This American Life-style episode for a brand.
Input:
> We want to produce a 30-minute documentary-style podcast about the gig economy, featuring three different workers' stories.
Output:
Three interwoven stories showing different faces of gig work: the freedom seeker, the trapped, and the optimizer. Same economy, radically different experiences.
Each story needs:
Opening Montage (0:00-2:00)
Quick cuts between all three characters:
End on: "This is the gig economy. But whose version is the real one?"
Story 1: Sarah (The Freedom Seeker) (2:00-8:00)
Interlude: Data/context on gig economy (30 seconds, produced)
Story 2: Marcus (The Trapped) (8:30-16:00)
Interlude: Host reflection bridging the contrast (1 min)
Story 3: Diana (The Optimizer) (17:00-24:00)
Synthesis (24:00-28:00)
Close (28:00-30:00)
## Pre-Production
### Story Engine
- [ ] Central question is clear and compelling
- [ ] Stakes are established (why does this matter?)
- [ ] I can articulate the tension in one sentence
- [ ] The "promise" to listeners is defined
### Structure
- [ ] Cold open drafted (starts in action)
- [ ] Act breaks are clear
- [ ] Each movement has its own mini-arc
- [ ] Reflection moments are planned (not just added after)
- [ ] Ending is satisfying and meaningful
### Interview Prep (if applicable)
- [ ] Background research complete
- [ ] Questions designed to elicit stories (not opinions)
- [ ] Follow-up prompts ready for deeper tape
- [ ] Technical setup tested
## Questions That Get Good Tape
### For specific moments:
- "Take me to that exact moment. Where were you standing?"
- "What were you thinking right then?"
- "What did you say? What did they say back?"
### For emotional truth:
- "What were you most afraid of?"
- "When did you first realize...?"
- "What did you learn that you didn't expect?"
### For reflection:
- "Looking back, what do you make of that?"
- "What would you tell yourself back then?"
- "Why do you think this matters?"
### Follow-up prompts:
- "Tell me more about that."
- "What do you mean by...?"
- "And then what happened?"
## Episode: [Title]
**Central Question**:
**Target Length**:
**Format**:
---
### Cold Open (XX:XX - XX:XX)
[What's the hook? First 30 seconds.]
### Act 1: Setup (XX:XX - XX:XX)
- Introduce...
- Establish stakes...
- Promise...
### Act 2: Journey (XX:XX - XX:XX)
**Movement 1**:
- Anecdote:
- Reflection:
**Movement 2**:
- Anecdote:
- Reflection:
**Movement 3** (optional):
- Anecdote:
- Reflection:
### Act 3: Resolution (XX:XX - XX:XX)
- The turn:
- Final reflection:
- Landing:
---
### Production Notes
- Music cues:
- Ambient sound:
- Guest clips to pull:
name: podcast-production
category: audio
subcategory: podcast
version: 1.0
author: MKTG Skills
source_expert: Ira Glass
source_work: This American Life
difficulty: intermediate
estimated_value: $2,000-5,000 per episode (equivalent consulting)
tags: [podcast, storytelling, audio, content-marketing, thought-leadership]
created: 2026-01-26
updated: 2026-01-26
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.
Brainstorm and write high-retention short-form video and carousel content for TikTok, Reels, and YouTube Shorts. Use whenever someone wants viral hook ideas, a video script or outline, content concepts for a product or topic, or wants to critique and improve a draft hook or script. Works for any storytime, listicle, carousel, or meme. Produces several diverse hook options from proven patterns, structures scripts for retention (hook, escalation, payoff, CTA), and adapts to each platform. Pattern-based guidance grounded in how short-form tends to perform; it improves the odds, it does not guarantee virality."
Generate short-form video ideas at volume and stop the blank-page problem for good. Use whenever someone says they're stuck for ideas, asks for 20 TikTok ideas or Reels ideas or YouTube Shorts ideas for their niche, wants a content brainstorm, needs help building a content pillar system or content matrix, wants to turn one idea into 5 angles, asks what to post this week, or wants a real idea generator workflow instead of staring at a notes app. Runs the systems prolific creators actually use: pillars, mining (comments, Reddit, search autocomplete, competitor outliers), repurposing, evergreen vs trend balance. Pattern-based guidance grounded in how short-form ideation tends to work; never run out of ideas is the goal, virality is not promised.
| This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Create and publish concise Rivet launch or changelog posts through an approval-gated workflow, including release research, a required user-selected hero variation, local HTML-rendered social and technical images, an R2 hero upload, MDX authoring, a reviewed draft GitHub PR for manual merge, and a scheduled and verified Buffer thread for @rivet_dev. Use when asked to launch, announce, ship, or prepare and schedule a Rivet feature or release announcement.
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Generate a daily digest of today's policy-authorized meetings and voice memos — key decisions, action items, and themes across available recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.
Generate a daily digest of today's policy-authorized meetings and voice memos — key decisions, action items, and themes across available recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.
Take guia-matthieu/podcast-production from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.