Claude AI Podcast Prompts That Actually Work (2026)

I recorded my first real estate market podcast episode in early 2024 — 38 minutes of me talking about Madeira’s short-term rental market, property prices in Funchal, and what international buyers were actually asking me that quarter. The recording was solid. The show notes took me two and a half hours to write. Two and a half hours for a single episode. I almost quit podcasting before I had a second episode.

Then I started using Claude to handle the entire post-production text workflow. Now I go from raw transcript to polished show notes, a timestamped summary, three social captions, and an email teaser in about 22 minutes. That shift changed how I think about solo content creation — not just for podcasts, but for anything that starts as spoken word.

This article is a working prompt swipe file. Every prompt below is one I’ve tested personally, refined over multiple episodes, and currently use or have used in my Madeira real estate consulting workflow. Copy them, paste them into Claude, adjust the bracketed variables, and run them. No fluff, no theory — just prompts that work.

Why Claude Handles Podcast Content Better Than Other AI Tools

Claude’s context window — currently 200,000 tokens on Claude.ai Pro ($20/month) — means you can paste an entire one-hour transcript and ask it to work with the full thing. Most podcast episodes run between 4,000 and 12,000 words when transcribed. Claude handles that without truncating or forgetting the first 20 minutes by the time it reaches the end.

The other reason I use Claude specifically for this: it’s genuinely good at preserving the speaker’s voice. When I ask it to write show notes from my transcript, it doesn’t turn my casual Madeira market commentary into corporate HR-speak. It keeps the tone. That matters when you’re trying to sound like yourself to an audience that already knows you.

One honest limitation upfront: Claude cannot process audio files directly. You need a transcript first — tools like Otter.ai, Descript, or Riverside.fm will generate one. That’s an extra step other tools like Adobe Podcast are starting to collapse into one, so keep that in mind if you want a fully automated pipeline. Claude is the text engine, not the transcription engine.

Section 1: Generating Complete Show Notes From a Raw Transcript

These are the workhorses. Paste your full transcript after the prompt and Claude will do the structural heavy lifting. The key is giving it a format template so you get consistent output every episode instead of a different structure each time.

Prompt 1 — Standard Show Notes With Sections

When to use it: Your default prompt for any interview or solo episode where you want a structured, publish-ready show notes page.

You are a podcast producer writing show notes for [PODCAST NAME], a show about [TOPIC/NICHE]. The host is [HOST NAME]. The audience is [TARGET AUDIENCE DESCRIPTION].

Using the transcript below, write complete show notes in this exact format:

**Episode Title:** [Create a clear, specific title that reflects the main topic]
**Episode Summary:** [3-4 sentences. What was discussed, why it matters, what the listener will learn]
**Key Takeaways:** [5-7 bullet points. Each one a complete, standalone insight — not vague summaries]
**Topics Covered:** [Bulleted list of main subjects in order of appearance]
**Guest Bio:** [If applicable — pull from anything mentioned in the transcript]
**Resources Mentioned:** [Any tools, books, websites, or names mentioned — list them all]
**Connect With Us:** [Leave as placeholder: INSERT LINKS]

Tone: [DESCRIBE YOUR SHOW'S TONE — e.g., "conversational but professional, no corporate language"]

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 2 — Show Notes for SEO (Keyword-Optimized)

When to use it: When you want your show notes page to rank in search. Give Claude the keyword and it will weave it in naturally without stuffing.

Write SEO-optimized show notes for this podcast episode. The primary keyword I want to rank for is: [TARGET KEYWORD]. Secondary keywords: [2-3 SECONDARY KEYWORDS].

Format:
- SEO Title (under 60 characters, includes primary keyword)
- Meta Description (under 155 characters)
- Intro paragraph (150-200 words, primary keyword in first 100 words, written naturally)
- Main show notes body (600-900 words, H2 subheadings where logical, secondary keywords used naturally)
- FAQ section (3 questions a listener might search, with answers pulled from the transcript)

Do not keyword-stuff. Every mention should read naturally.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 3 — Minimal Show Notes (Under 300 Words)

When to use it: Shorter episodes, bonus content, or platforms where brevity matters. Also good for a quick publish when you’re behind schedule.

Write concise show notes for this episode. Maximum 300 words total. Include:
1. One-paragraph episode summary (3-4 sentences)
2. Three key takeaways (one sentence each)
3. Any resources or names mentioned

No padding. No filler. Every sentence earns its place.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Section 2: Timestamped Chapter Summaries and Episode Outlines

Timestamps are one of the most useful things you can give a listener — and one of the most tedious things to create manually. Claude can generate them from a transcript if your transcription tool includes timestamps in the text (Otter.ai and Descript both do this). If yours doesn’t include timestamps, you can still get chapter summaries without the time codes.

Prompt 4 — Timestamped Chapters From a Timestamped Transcript

When to use it: When your transcript includes time markers. Generates YouTube chapter descriptions or podcast chapter tags.

Using the timestamped transcript below, identify the 6-10 most distinct topic shifts in the conversation. For each one, provide:
- The timestamp where it begins (use the nearest timestamp marker from the transcript)
- A chapter title (5-8 words, specific and descriptive — not vague like "Introduction" or "Discussion")
- A one-sentence description of what's covered in that section

Format example:
[00:00] Welcome and Episode Context — Host introduces the topic and why it matters right now
[04:22] [Chapter Title] — [One-sentence description]

Timestamped transcript:
[PASTE TRANSCRIPT WITH TIMESTAMPS]

Prompt 5 — Topic Outline Without Timestamps

When to use it: When your transcript has no time markers but you still want a structured chapter list for your show notes or episode description.

Read this transcript and create a logical chapter outline. Identify the 5-8 main topic sections as they naturally occur in the conversation. Label each chapter with a clear, specific title and write 2-3 sentences explaining what was discussed in that section.

Present the output as a numbered list, in order of appearance.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 6 — One-Sentence Episode Summary for Podcast Directories

When to use it: Spotify, Apple Podcasts, and other directories often display only the first one or two sentences of your description. Make them count.

Write 5 different one-sentence episode descriptions for this podcast episode. Each one should:
- Be under 25 words
- Describe the specific topic and the listener benefit
- Be written for someone scrolling a podcast directory deciding whether to click play
- Sound like a human wrote it, not a press release

Present them numbered, no additional explanation needed.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Section 3: Social Media Captions and Promotional Content From Episodes

One episode should produce content for at least a week of social posts. These prompts do that extraction automatically. The trick is being specific about format — Claude will match the platform’s style if you tell it which one you’re writing for.

Prompt 7 — LinkedIn Post From Episode Highlight

When to use it: Promoting a B2B or professional episode to a LinkedIn audience. Works especially well for solo episodes where you’re sharing market insights.

Write a LinkedIn post promoting this podcast episode. 

Requirements:
- Opens with a bold, specific claim or counterintuitive statement from the episode (not "In our latest episode...")
- 150-250 words
- Short paragraphs, maximum 2-3 sentences each
- Ends with a clear call to action: "Full episode linked in the comments" or "Listen link in bio"
- No hashtag spam — maximum 3 relevant hashtags at the end
- Tone: [YOUR TONE — e.g., direct, professional, no corporate buzzwords]

Pull the most interesting or surprising insight from the transcript and build the post around that.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 8 — Instagram Caption With Hook

When to use it: Promoting a new episode on Instagram, especially if you’re posting an audiogram or quote card image alongside it.

Write an Instagram caption for a new podcast episode post. 

Structure:
Line 1: Strong hook — a question, bold statement, or surprising fact from the episode (under 125 characters so it shows before "more")
Lines 2-4: 2-3 short paragraphs expanding on why this episode matters
Final line: Call to action (e.g., "New episode in bio link 🎙️")
Hashtags: 8-12 relevant hashtags on a separate line at the end

The hook must be pulled from something actually said or discussed in the transcript — not invented.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 9 — 5 Twitter/X Posts From One Episode

When to use it: Batching a week’s worth of short-form content from a single episode. Space these out across 5-7 days.

Extract 5 distinct, standalone insights from this podcast transcript and turn each into a Twitter/X post.

Rules:
- Each post must be under 280 characters
- Each post must stand alone — a reader should understand it without having heard the episode
- Vary the format: use a mix of statements, questions, and short lists
- Do not start any post with "In this episode" or "My guest said"
- End 2 of the 5 posts with a curiosity hook that would make someone want to find the full episode

Number them 1-5.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 10 — Email Newsletter Blurb for New Episode

When to use it: Your weekly newsletter needs an episode blurb. This one writes it in a way that feels personal, not promotional.

Write a podcast episode blurb for a weekly email newsletter. 

Tone: Like I'm telling a friend about a conversation I just had — direct, no fluff, personal.
Length: 120-180 words
Structure:
- 1 sentence on what the episode is about (specific, not vague)
- 2-3 sentences on the most interesting thing discussed
- 1 sentence on who should listen and why
- 1 sentence CTA with a placeholder link: [LISTEN HERE]

Do not use phrases like "tune in," "don't miss this one," or "this episode is packed with."

Transcript:
[PASTE FULL TRANSCRIPT HERE]

My Real-World Experience Using Claude for Podcast Show Notes in Madeira

I want to be specific about what this actually looks like in practice, because “saves time” is a useless claim without numbers behind it.

I started recording quarterly market update episodes in early 2024 — solo recordings where I summarize what’s happening in Madeira’s property market for international buyers who follow my work. These run 30-45 minutes each. My transcription tool (I use Otter.ai at $16.99/month) delivers a transcript within about 10 minutes of uploading the audio file.

Before Claude, my post-production workflow looked like this: listen back to the episode while writing notes, draft the show notes from scratch, write the email blurb, write a LinkedIn post, write a caption for Instagram. Total time: 2.5 to 3 hours per episode. That’s per episode. I was recording four per year, so maybe 10-12 hours annually on text work for 4 episodes. Painful enough that I’d procrastinate publishing for days after recording.

Now my workflow is: upload audio to Otter, paste transcript into Claude with Prompt 1 from this article (modified for my real estate podcast format), then run Prompt 7 for LinkedIn, Prompt 10 for my email, and Prompt 9 for social posts. Total active work time: 22-28 minutes per episode, depending on how much editing the output needs.

The most recent episode I produced was a 41-minute solo piece on the Madeira Golden Visa alternatives and what the 2026 landscape looks like for non-EU buyers. The Otter transcript was 6,800 words. I pasted it into Claude on the Pro plan, ran my show notes prompt, and had a 780-word, publish-ready show notes page in under 4 minutes. I made 11 small edits — mostly adding specific local context that Claude got slightly wrong (it referenced a general Portuguese tax rule when the Madeira-specific version applies differently). That took 8 more minutes. Total: 12 minutes for show notes that previously took me 90 minutes to write.

Over the past 14 months, I’ve processed 11 episodes this way. My conservative estimate is that Claude has recovered about 26 hours of writing time across those 11 episodes — time I’ve redirected into recording more content and doing actual client work. At my consulting rate, that’s not a trivial number.

The genuine limitation I’ve run into: Claude struggles with heavily accented or jargon-heavy transcripts. When I interviewed a Portuguese property lawyer about NHR tax regime changes, the transcript from Otter was messy — legal terms transcribed incorrectly, Portuguese names mangled. Claude produced show notes based on those errors and I didn’t catch all of them on first read. The lesson: the quality of Claude’s output is directly tied to the quality of your transcript. Garbage in, plausible-sounding garbage out. Always read the output against the original on technical episodes.

Section 4: Guest Prep, Intros, and Episode Descriptions

These prompts work before and around the episode, not just from the transcript after recording.

Prompt 11 — Write a Guest Introduction From a Bio

When to use it: You have a guest’s bio (from their website or LinkedIn) and you need a spoken host intro that sounds natural, not like a CV readout.

Rewrite this guest bio as a spoken podcast introduction. 

Requirements:
- 60-90 seconds when read aloud at a natural pace (roughly 150-200 words)
- Written for the host to read, not for the guest to hear — no "I'm honored to introduce"
- Starts with the most interesting or unusual thing about this person, not their job title
- Conversational tone, no corporate language
- Ends with one question that naturally transitions into the conversation

Guest bio:
[PASTE BIO HERE]

Podcast topic for this episode: [TOPIC]

Prompt 12 — 10 Interview Questions From Guest’s Content

When to use it: Prep for a guest interview. Paste their website about page, a recent article they wrote, or their LinkedIn summary.

Based on the content below, write 10 interview questions for a podcast episode.

Rules:
- Questions should be open-ended (no yes/no questions)
- Order them from warm-up to deeper/more specific
- At least 3 questions should be ones the guest has probably NOT been asked in standard interviews
- Avoid generic questions like "How did you get started?" unless it leads somewhere specific
- Write a brief note after each question explaining why it's worth asking

Guest content:
[PASTE THEIR WEBSITE BIO, ARTICLE, OR LINKEDIN SUMMARY]

Podcast focus for this episode: [YOUR SPECIFIC ANGLE]

Prompt 13 — Episode Description for Podcast Directories (Apple, Spotify)

When to use it: Writing the episode description that goes into your podcast hosting platform and syndicates to directories. Different from show notes — this needs to work as browsable copy.

Write a podcast episode description for submission to Apple Podcasts and Spotify. 

Format:
- Paragraph 1 (60-80 words): What this episode is about and who it's for
- Paragraph 2 (60-80 words): 2-3 specific things the listener will learn or hear discussed
- Paragraph 3 (30-40 words): Guest credentials (if applicable) or host credibility statement
- Final line: "Subscribe wherever you listen to podcasts."

Total length: 180-220 words.
No clickbait. No "you won't believe" language. Write for someone who reads two sentences before deciding to download.

Episode details:
Topic: [TOPIC]
Guest (if any): [GUEST NAME AND ONE-LINE DESCRIPTION]
Key points covered: [LIST 3-5 MAIN POINTS FROM YOUR EPISODE PLAN OR TRANSCRIPT]

Prompt 14 — Episode Title Generator (10 Options)

When to use it: You know what the episode is about but can’t land on a title. Give Claude the transcript or the main topic and let it generate options across different styles.

Generate 10 podcast episode title options for the following episode. 

Vary the style across the 10 options:
- 2 titles using a number (e.g., "3 Reasons Why...")
- 2 titles framed as questions
- 2 titles with a colon (Topic: Subtopic format)
- 2 titles that are bold statements or counterintuitive claims
- 2 short punchy titles (under 6 words)

Rules: No clickbait. Every title must accurately reflect the episode content. No titles starting with "Unlocking" or "Mastering."

Episode topic: [DESCRIBE THE MAIN TOPIC IN 2-3 SENTENCES]
Guest (if applicable): [NAME AND EXPERTISE]
Key insight from the episode: [ONE SENTENCE — THE MOST INTERESTING THING DISCUSSED]

Section 5: Repurposing Transcripts Into Long-Form Content

A 40-minute episode is also a blog post, a lead magnet, and a FAQ page. These prompts pull that value out without starting from scratch.

Prompt 15 — Convert Episode Into a Blog Post

When to use it: Turn a strong solo episode into a standalone blog article. Especially useful if the episode covers evergreen advice.

Convert this podcast transcript into a blog post. 

This is NOT a recap — it should read as an original article, not a transcript summary.

Requirements:
- Target length: 900-1,200 words
- Use H2 and H3 subheadings to structure the content logically
- Write in first person, matching the speaker's voice from the transcript
- Expand on points where the spoken explanation was brief — add clarity where needed
- Do not include filler phrases like "As I mentioned earlier" or "Like I said in the episode"
- Include a short intro paragraph that hooks the reader without starting with "In this episode"
- End with a 2-3 sentence conclusion and a CTA to listen to the full episode

Primary keyword to include naturally: [TARGET KEYWORD]

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 16 — Extract Quotable Moments for Graphics

When to use it: Finding the 5-7 lines from an episode that work as quote cards, pull quotes, or audiogram captions.

Read this transcript and identify the 7 most quotable moments. A quotable moment is:
- A complete thought in 1-3 sentences
- Surprising, counterintuitive, or distinctly phrased
- Understandable without additional context
- Something that would make someone stop scrolling if they saw it as a graphic

For each quote:
1. Paste the exact quote (do not paraphrase)
2. Write one sentence explaining why it's quotable and who it would resonate with

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 17 — Create an Episode-Based Lead Magnet Outline

When to use it: When an episode covers enough ground to become a downloadable checklist, guide, or resource that grows your email list.

Based on this podcast transcript, create an outline for a short lead magnet (PDF guide or checklist) that complements the episode.

Output:
- Lead magnet title (specific, benefit-driven, under 10 words)
- Format recommendation: checklist / step-by-step guide / resource list / quick reference sheet (choose the best fit based on content)
- Section-by-section outline (4-6 sections) with 3-5 bullet points per section
- One-sentence description of what the reader gets from each section

The lead magnet should stand alone — someone who hasn't listened to the episode should still find it valuable.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Section 6: Advanced Prompts for Established Podcast Workflows

These are the prompts I reach for when I need more than a one-shot output — when I want Claude to work within a system, maintain consistency across episodes, or produce something more tailored than a general summary.

Prompt 18 — Create a Reusable Show Notes Template From 3 Past Episodes

When to use it: You want Claude to learn your existing show notes style so future prompts produce consistent output. Feed it 3 past examples.

I'm going to show you three examples of show notes from my podcast. Study the format, tone, section order, and length. Then confirm you understand the pattern before I give you a new transcript to process.

Do not write anything yet — just analyze and describe the pattern you see. I'll give you a new transcript after you confirm.

Example 1:
[PASTE PAST SHOW NOTES]

Example 2:
[PASTE PAST SHOW NOTES]

Example 3:
[PASTE PAST SHOW NOTES]

Prompt 19 — Identify the Episode’s Core Argument or Thesis

When to use it: Before writing anything else. Useful for complex or meandering conversations where you need to find the thread before you can summarize it.

Read this transcript carefully. Before writing any show notes or summaries, answer these four questions in 2-4 sentences each:

1. What is the central argument or main claim of this episode?
2. What is the single most important insight a listener should take away?
3. Who is the ideal listener for this episode, and what problem does it solve for them?
4. What is the most surprising or counterintuitive thing said in this conversation?

These answers will guide everything else I write for this episode.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 20 — Fact-Check Flags: What Needs Verification

When to use it: After generating show notes, especially on factual or technical episodes. Claude identifies the claims most likely to need a source check before you publish.

Review the following show notes I've written from a podcast transcript. Identify every specific claim, statistic, date, name, or fact that a reader might want a source for — or that could be inaccurate if the speaker misspoke.

For each item flagged:
- Quote the specific claim
- Explain briefly why it should be verified (e.g., "specific statistic that may be outdated," "legal claim that varies by jurisdiction")
- Suggest what source type would verify it (e.g., government website, academic study, brand's official page)

Do not fact-check yourself — only flag what needs external verification.

Show notes to review:
[PASTE YOUR GENERATED SHOW NOTES]

Prompt 21 — Repurpose Episode as a Script for a Short-Form Video

When to use it: Turning one key episode insight into a 60-90 second script for a Reel, TikTok, or YouTube Short.

Extract the single most interesting insight from this podcast transcript and write a 60-second script for a short-form video (Instagram Reel or YouTube Short).

Script structure:
- Hook (0-3 seconds): One bold sentence that stops the scroll
- Setup (3-20 seconds): Context — why this matters
- Main point (20-50 seconds): The insight explained simply, with one concrete example
- Closing line (50-60 seconds): One memorable sentence that lands the point
- On-screen CTA text: [SUBSCRIBE / FOLLOW / LINK IN BIO — choose one]

Write for spoken delivery. Short sentences. No bullet points. Read time should be 60-70 seconds at a natural pace.

Transcript:
[PASTE FULL TRANSCRIPT HERE]

Prompt 22 — Seasonal or Series Episode Recap (Multiple Episodes)

When to use it: End of a season or a multi-part series. Give Claude the show notes from 4-8 episodes and it synthesizes a recap piece.

Using the show notes from the episodes listed below, write a "Season Recap" article or newsletter piece.

Requirements:
- 600-800 words
- Identify the 3-4 overarching themes that ran across this season
- Reference specific episodes by name (use the titles provided)
- Pull the single best insight from each episode
- End with a "What's coming next" placeholder section and a CTA to subscribe

Tone: [YOUR TONE]

Episode show notes:
Episode 1 title + show notes: [PASTE]
Episode 2 title + show notes: [PASTE]
[Continue for each episode]

Quick Comparison: Claude vs Other AI Tools for Podcast Show Notes