MCP HubMCP Hub
스킬 목록으로 돌아가기

podcast-interview

guia-matthieu
업데이트됨 2 days ago
2 조회
111
20
111
GitHub에서 보기
디자인aidesign

정보

이 Claude Skill은 NPR의 방법론과 팀 페리스의 기법을 적용하여 개발자들이 팟캐스트 인터뷰를 준비하고 진행할 수 있도록 돕습니다. 이는 짧은 발췌문이 아닌 진정성 있고 깊이 있는 응답을 이끌어내는 질문을 설계하는 데 지원을 제공합니다. 인터뷰 계획 수립, 질문 구성, 또는 게스트가 효과적으로 마음을 열도록 하는 기술을 향상시킬 때 활용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add guia-matthieu/clawfu-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git 클론대체
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/podcast-interview

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Podcast Interview Mastery

Master the art of podcast interviewing using NPR training methodology and Tim Ferriss's preparation techniques to extract compelling stories and insights from any guest.

When to Use This Skill

  • Preparing for a podcast interview with a guest
  • Designing questions that elicit stories, not soundbites
  • Struggling to get guests to open up authentically
  • Planning a new interview-format podcast
  • Improving your interviewing technique
  • Coaching others on interview skills

Methodology Foundation

Source: NPR Training + Tim Ferriss (The Tim Ferriss Show, 700+ episodes)

Core Principle: Great interviews are 80% preparation and 20% presence. "The best interviews feel like conversations, but they're actually carefully orchestrated to extract specific moments of insight, emotion, and story." The interviewer's job is to be genuinely curious while guiding toward revelatory moments.

Why This Matters: Most podcast interviews are forgettable because hosts ask the same questions and accept surface-level answers. NPR-trained interviewers and Tim Ferriss have developed techniques that consistently produce the "good tape" that makes episodes shareable and memorable.

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures production workflowFinal creative direction
Suggests technical approachesEquipment and tool choices
Creates templates and checklistsQuality standards
Identifies best practicesBrand/voice decisions
Generates script outlinesFinal script approval

What This Skill Does

  1. Designs interview questions for story extraction - Questions that get narrative, not bullet points
  2. Prepares comprehensive guest research - Know enough to ask unexpected questions
  3. Creates psychological safety - Techniques for making guests vulnerable
  4. Navigates difficult moments - How to redirect, follow up, and challenge respectfully
  5. Identifies and pursues good tape - Recognizing when to dig deeper

How to Use

Prepare for an Interview

Help me prepare for a podcast interview with [guest name].
They are known for: [brief background]
Episode angle/theme: [what you want to explore]
Length: [target runtime]

Design Better Questions

I'm interviewing [guest type] about [topic]. Help me design questions that get stories, not just information.

Improve Existing Questions

Review these interview questions and suggest improvements:
[paste questions]

Instructions

When preparing and conducting interviews, follow this methodology:

Step 1: Deep Research Phase

Before writing a single question, immerse yourself in your guest.

## Research Checklist

**Primary Sources** (1-2 hours minimum):
□ Read/watch their most substantial long-form content
□ Their book, keynote, or signature work
□ Previous podcast appearances (note what's been asked before)
□ Recent social media activity (what are they thinking about NOW?)

**Secondary Sources** (30-60 min):
□ Wikipedia/bio for career arc and timeline
□ Company/project announcements
□ Industry news involving them
□ Interviews with people who've worked with them

**Look For**:
- Contradictions between what they say and do
- Topics they're NEVER asked about
- Recent changes in their thinking
- Personal moments that shaped their professional life
- The question you're dying to ask

Tim Ferriss's Rule: "I try to find the question they've never been asked that they'd love to answer."


Step 2: Design Questions for Story, Not Information

The difference between a mediocre and great interview is the type of questions asked.

## Question Types Hierarchy

**AVOID - Information Questions** ❌
- "What do you do?"
- "How did you get started?"
- "What advice would you give?"
→ Gets: Rehearsed talking points

**BETTER - Scenario Questions** ✓
- "Take me to the moment when..."
- "Walk me through the day..."
- "What was going through your mind when..."
→ Gets: Specific memories, sensory details

**BEST - Emotional Truth Questions** ✓✓
- "What scared you most about that decision?"
- "What did you learn that surprised you?"
- "What's the thing about [topic] that most people get wrong?"
→ Gets: Authentic reflection, vulnerability

Step 3: Structure Your Question Arc

Don't just list questions—design a journey.

## Interview Arc Template

**Opening (5-10 min)**
Purpose: Establish rapport, get them talking
- Start with something CURRENT (not their origin story)
- Show you've done your homework
- Ask about something specific and recent
- Example: "I saw your tweet last week about [X]. What prompted that?"

**Middle - Act 1 (10-20 min)**
Purpose: Understand the journey
- Key inflection points
- Decisions that shaped their path
- "What most people don't know about that period..."
- Follow unexpected threads

**Middle - Act 2 (15-25 min)**
Purpose: Go deep on the main topic
- The questions you MUST ask
- Challenges to their public positions
- "How do you reconcile X with Y?"
- The uncomfortable but important questions

**Closing (5-10 min)**
Purpose: Synthesis and takeaways
- What they're working on now
- What they'd do differently
- One piece of advice (but make it specific)
- The question you're afraid to ask

Step 4: Master the Follow-Up

The best material comes from following up, not from prepared questions.

## Follow-Up Techniques

**The Silence**: Say nothing after they finish. Count to 5. They'll fill it with gold.

**The Echo**: Repeat their last few words as a question.
Guest: "...and that's when I knew it was over."
You: "You knew it was over?"

**The Dig**: "Tell me more about that."

**The Redirect**: "Let's go back to something you said earlier..."

**The Challenge**: "Some people would say [counter-argument]. How do you respond?"

**The Feeling**: "How did that make you feel?" (Use sparingly but powerfully)

**The Unexpected**: "That's not what I expected you to say. Why...?"

NPR Rule: Prepare 2x more questions than you'll need, but be ready to throw them all out if the conversation goes somewhere better.


Step 5: Create Psychological Safety

Vulnerability requires safety. Build it intentionally.

## Before Recording

- Share YOUR vulnerabilities about the topic
- Be explicit about your goals: "I want this to be a real conversation"
- Remind them they can say "off the record" anytime
- Start with low-stakes questions to warm up
- Match their energy and pace

## During Recording

- React authentically (laugh, express surprise)
- Share related personal experiences briefly
- Make eye contact (even on video calls)
- Nod, use "mm-hmm" to show engagement
- Never look at your phone or notes while they're sharing something vulnerable

## After Difficult Moments

- Acknowledge what they shared: "Thank you for being so honest about that."
- Give them an easy question to recover
- Return to vulnerable topics gently if needed

Step 6: Navigate Difficult Moments

## When They Give a Non-Answer

**Technique**: Acknowledge, then redirect
"That's interesting. But I'm curious specifically about..."
"I hear you. Let me ask it differently..."

## When They're Being Promotional

**Technique**: Accept, then pivot to story
"The product sounds great. Take me to the moment you decided to build it."
"Before we get to that—what was the biggest failure on the way there?"

## When They're Uncomfortable

**Technique**: Name it, give an out
"I can tell this is a sensitive topic. We can skip it if you prefer, or..."
"I'm asking because [explain why it matters to listeners]..."

## When You Disagree

**Technique**: Steel-man, then question
"The strongest version of that argument is [X]. But what about [Y]?"

## When They Say Something Wrong

**Technique**: Curious, not confrontational
"That's different from what I've read. Help me understand..."
"Some people would push back on that. What would you say to them?"

Examples

Example 1: Tech Founder Interview Preparation

Context: Interviewing a CEO who recently sold their company for $500M.

Input:

Help me prepare for a podcast interview with Sarah Chen, CEO of DataFlow (just acquired by Microsoft for $500M). Episode theme: the journey from side project to acquisition.

Output:

Interview Preparation: Sarah Chen

Research Summary

  • Timeline: Started DataFlow in 2019 as side project, quit Google 2020, Series A 2021, acquisition 2025
  • Previous interviews: Forbes, TechCrunch podcast, Bloomberg (all asked standard "founder journey" questions)
  • Untapped territory: Her co-founder left in 2022 (never discussed publicly), she's mentioned imposter syndrome on Twitter
  • Current focus: Posts about "what comes after" and hints at future projects

Questions That Get Stories

Opening (current, not origin)

  1. "You've been pretty quiet since the acquisition was announced. What's been going through your mind these past few weeks?"
  2. "I saw you tweeted about 'the silence after the storm.' What did you mean?"

The Journey (inflection points) 3. "Take me to the weekend you decided to quit Google. What was the conversation with your family like?" 4. "I noticed your co-founder David left in 2022, right before the Series B. What happened there?"

  • Follow-up: "How did that change how you lead?"
  1. "There's a two-month gap in your LinkedIn between leaving Google and officially starting DataFlow. What were those 60 days like?"

The Deal (specifics, not platitudes) 6. "Walk me through the call when Microsoft first reached out. Where were you? What did you think it was about?" 7. "At what point did you decide to sell rather than keep building? What tipped the decision?" 8. "What was the hardest part of the negotiation that no one talks about?"

The Real Stuff 9. "You've mentioned imposter syndrome. At $500M, does it go away?" 10. "What's the conversation with your 2019 self—the one with the side project—look like?" 11. "What did the acquisition cost you that money can't buy back?"

Closing 12. "A year from now, what do you hope to have figured out?" 13. "What question do you wish interviewers would stop asking?"

Follow-Up Triggers

  • If she mentions "lucky" → probe for what she actually did
  • If she deflects on co-founder → "I understand if you can't share, but listeners are often going through similar..."
  • If she mentions family → "How did your [spouse/kids] experience this journey?"

Example 2: Turning Boring Questions Into Gold

Context: Improving standard interview questions for an author interview.

Input:

Review these interview questions and suggest improvements:

  1. What's your book about?
  2. Why did you write it?
  3. What's your writing process?
  4. What advice would you give to aspiring writers?

Output:

Question Transformation

Original → Improved

1. "What's your book about?"Problem: Gets the dust jacket summary

Better:

  • "Your book argues [specific thesis]. What's the one story from your research that made you certain you were right?"
  • "If someone reads your book and changes ONE thing in their life, what should it be?"
  • "What's the most controversial claim in the book, and why are you confident about it?"

2. "Why did you write it?"Problem: Gets the rehearsed answer

Better:

  • "What personal experience made this topic impossible to ignore?"
  • "You've been [their job] for 20 years. Why did this particular book demand to be written NOW?"
  • "I read that you almost abandoned this project in 2023. What happened?"
  • "What were you angry about when you started writing?"

3. "What's your writing process?"Problem: Gets generic productivity tips

Better:

  • "Walk me through the worst writing day you had on this book. What happened and how did you get unstuck?"
  • "What's the weirdest ritual that actually helps you write?"
  • "Which chapter made you want to quit, and why?"
  • "Show me your outline for Chapter 7." (if visual component available)

4. "What advice would you give to aspiring writers?"Problem: Gets platitudes

Better:

  • "What advice do you wish you had ignored?"
  • "What's the advice that sounds good but actually doesn't work?"
  • "If you could only tell a new writer ONE thing—and it had to be specific and actionable—what is it?"
  • "What's a habit you developed that most people would find surprising or uncomfortable?"

Why This Works

Every improved question:

  • Asks for a specific story or moment
  • Shows you've done your research
  • Challenges them to think freshly
  • Can't be answered with a rehearsed soundbite

Checklists & Templates

Pre-Interview Checklist

## 48 Hours Before

Research:
- [ ] Read/watched their most significant recent work
- [ ] Listened to 2-3 previous podcast appearances
- [ ] Noted what they're NEVER asked
- [ ] Found one thing that surprised me

Questions:
- [ ] 15-20 questions drafted
- [ ] Questions progress from easy → hard
- [ ] At least 3 questions I'm nervous to ask
- [ ] Follow-up prompts ready for each section

Logistics:
- [ ] Confirmed time (with timezone!)
- [ ] Tested recording setup
- [ ] Backup recording method ready
- [ ] Questions sent to guest (optional, some hosts don't)

Interview Day Checklist

## 30 Minutes Before
- [ ] Tech check complete
- [ ] Recording test confirmed
- [ ] Water bottle ready
- [ ] Questions printed/visible
- [ ] Phone silenced

## During Recording
- [ ] Started with rapport-building
- [ ] Asked permission to go deeper when needed
- [ ] Followed unexpected threads
- [ ] Used silence effectively
- [ ] Listened more than talked

## After Recording
- [ ] Asked "What didn't I ask that I should have?"
- [ ] Captured any off-mic gold
- [ ] Thanked them genuinely
- [ ] Noted key timestamps for editor

Question Bank by Guest Type

## For Founders/Entrepreneurs
- "What was the lowest moment, and how did you get through it?"
- "What's the decision you'd make differently?"
- "What does your inner critic say to you?"

## For Authors/Experts
- "What changed in your thinking while writing this?"
- "What's the critique of your work that stings because it's partially true?"
- "What question do you hope someone asks you?"

## For Executives/Leaders
- "Tell me about a time you were wrong about someone."
- "What's a decision you made that was right but unpopular?"
- "What do you know now that you wish you knew at 30?"

## For Creatives
- "Walk me through the moment you knew this project would work."
- "What did you have to unlearn?"
- "What's the thing you made that you thought would succeed but didn't?"

Skill Boundaries

What This Skill Does Well

  • Structuring audio production workflows
  • Providing technical guidance
  • Creating quality checklists
  • Suggesting creative approaches

What This Skill Cannot Do

  • Replace audio engineering expertise
  • Make subjective creative decisions
  • Access or edit audio files directly
  • Guarantee commercial success

References

  • NPR Training. "NPR's Podcast Start Up Guide" (Glen Weldon) - Professional interview standards
  • Tim Ferriss. "The Tim Ferriss Show" (2014-present) - 700+ episodes of interview methodology
  • Terry Gross. "Fresh Air" - Master class in creating safe spaces for vulnerability
  • Marc Maron. "WTF with Marc Maron" - Authentic conversation technique

Related Skills


Skill Metadata (Internal Use)

name: podcast-interview
category: audio
subcategory: podcast
version: 1.0
author: MKTG Skills
source_expert: NPR Training, Tim Ferriss
source_work: NPR's Podcast Start Up Guide, The Tim Ferriss Show
difficulty: intermediate
estimated_value: $500-2,000 per interview (equivalent preparation time)
tags: [podcast, interview, research, questions, guests]
created: 2026-01-26
updated: 2026-01-26

GitHub 저장소

guia-matthieu/clawfu-skills
경로: skills/audio/podcast-interview
0
ai-skillsanthropicclaude-codeclaude-skillsmarketingmcp-server

연관 스킬

executing-plans

디자인

executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.

스킬 보기

requesting-code-review

디자인

이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.

스킬 보기

connect-mcp-server

디자인

이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.

스킬 보기

web-cli-teleport

디자인

이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기