Spoken Podcast Scripts You Record
Paste into Claude. Fill [PLACEHOLDERS]. Get spoken opens, solo rundowns, guest intros, ad reads, closes, and series-arc lines. You still record the episode. Not show notes after the tape. Not a show bible.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Open
5 promptsFirst Forty Cold Open
1/30โจ What it does
Claude writes five spoken first-40-second cold opens for [EPISODE TOPIC] with pause marks and the promise later segments must pay. You still record two opens on the mic and keep the take you can say without looking down.
You are a podcast scriptwriter who writes the first 40 seconds a host can say on tape, not a show bible and not show notes. <context> I need spoken cold opens for one episode. Each open must hook a stranger in the first 12 seconds, plant one promise later segments will pay, and work if someone is still putting in earbuds. Do not write the body, the ads, or the close. Spoken script only. Not HTML. Not a YouTube open. </context> <inputs> - Episode topic and unique angle: [EPISODE TOPIC] - Show name: [SHOW NAME] - Who is listening and why they skip: [AUDIENCE] - The one outcome if they stay: [OUTCOME] - Segments I will actually record: [SEGMENT LIST] - Host voice: [WARM / DIRECT / DRY] - I use a house music sting: [YES / NO] </inputs> <task> Write 5 first-40-second spoken opens. For each: exact words with pause marks, a 5-second recap line if they missed the first sentence, the unanswered promise, and which segment in [SEGMENT LIST] pays it. Rank the top 2 to record first. Do not write segment 2 or the CTA. </task> <constraints> - No welcome-back-to-the-show filler that lasts 25 seconds. - Do not resolve the promise in the open. - Every line must be speakable on the first take. - The tease must match a real segment in [SEGMENT LIST]. - Spoken podcast open only. Not show notes. Not a webinar waiting-room open. Not HTML. - Do not invent a guest quote, a download number, or a clip I did not list. </constraints> <format> Return a ranked table: spoken open, seconds, recap line, paying segment. Name the two I should record first. Paste-ready spoken lines only. </format>
Pro tip: Say each open on a timer with headphones on. If you need a breath before the promise, cut words, do not talk faster.
Mid-Scene Cold Open
2/30โจ What it does
Claude writes six mid-scene spoken cold opens from [STORY BEAT] that start in the charged moment, then hand to the house intro. You still record the scene first and keep the take that starts mid-action, not last Tuesday.
You are a podcast scriptwriter who opens mid-scene, not with a calendar and not with a welcome. <context> I need spoken cold opens that start on [STORY BEAT], hold 20 to 35 seconds, then hand to the house intro. Spoken lines only. Not a transcript rewrite and not HTML. </context> <inputs> - The charged moment I can tell: [STORY BEAT] - What happened, in facts I can stand behind: [WHAT HAPPENED] - The twist or lesson later: [TWIST] - Show name and house intro I already use: [SHOW NAME] / [HOUSE INTRO OR NONE] - Audience: [AUDIENCE] - Voice: [QUIET / BLUNT / WARM] </inputs> <task> Write 6 mid-scene cold opens (20 to 35 seconds). First line is action from [STORY BEAT], not a date. Honor only [WHAT HAPPENED]. Tease [TWIST] without paying it. End with a one-line handoff into [HOUSE INTRO OR NONE] or a 4-second silence if NONE. Rank 3 that sound like tape, not a blog lede. </task> <constraints> - First word cannot be a date, welcome back, or so I wanted to talk about. - Do not invent dialogue or a happier ending. - Do not write the rest of the episode. - Spoken podcast open. Not show notes. Not a YouTube smash cut. Not HTML. </constraints> <format> Return spoken open, seconds, first-line note, handoff. Star two I should record first. </format>
Pro tip: Start in the messy middle. If the first word is last week, you already lost the skip-happy listener.
House Intro Then Promise
3/30โจ What it does
Claude writes a spoken house-intro-plus-promise open for [SHOW NAME] that keeps the sting short and names what this episode will pay. You still record the intro in one take and trim the sting if the first 20 seconds sag.
You are a podcast scriptwriter who writes a house intro a host can say every week, then a fresh promise for this episode. <context> I need a spoken open: short house ID for [SHOW NAME], then the promise for this episode. Not a 90-second trailer and not directory copy. Spoken script only. Not HTML. </context> <inputs> - Show name and one-line premise: [SHOW NAME] / [PREMISE] - This episode topic: [EPISODE TOPIC] - Promise I will actually pay on tape: [PROMISE] - Host credit I can say in one breath: [HOST CREDIT] - Music sting length I can keep: [STING SECONDS] - Voice: [WARM / DIRECT] </inputs> <task> Write 5 spoken opens (25 to 45 seconds). Each: [SHOW NAME] ID in under 8 seconds, [HOST CREDIT] in one clause, then [PROMISE] for [EPISODE TOPIC] before second 20. Mark where the sting sits. Give a 12-second cut if I drop the sting. Do not write the body. </task> <constraints> - Do not invent a download count or an award. - Do not turn the intro into a host bio. - Promise must match [PROMISE], not a bigger claim. - Spoken podcast open. Not show notes. Not a YouTube channel trailer. Not HTML. </constraints> <format> Return spoken open, seconds, sting cue, 12-second cut. Star two I should record. </format>
Pro tip: Name the episode payoff before your bio. If the sting plus credits eat 40 seconds, people skip to chapter 2.
Listener Question Open
4/30โจ What it does
Claude writes seven spoken opens that put [LISTENER QUESTION] in the first sentence, then name the segment that answers it. You still record the question in their words and keep the take that does not rewrite them into marketing.
You are a podcast scriptwriter who opens on a real listener question, not a fake mailbag. <context> I have [LISTENER QUESTION]. I need spoken opens that quote or closely paraphrase that question, then point at the segment that answers it. Open only. Not a full mailbag rundown and not HTML. </context> <inputs> - The question in their words: [LISTENER QUESTION] - How they sent it: [EMAIL / DM / VOICE NOTE / FORM] - Name I may use on tape: [FIRST NAME OR ANONYMOUS] - Segment that answers it: [PAYING SEGMENT] - Show name: [SHOW NAME] - Voice: [WARM / DRY] </inputs> <task> Write 7 spoken opens (15 to 30 seconds). Each puts [LISTENER QUESTION] in the first sentence, credits [FIRST NAME OR ANONYMOUS] honestly, and teases [PAYING SEGMENT] without answering yet. If ANONYMOUS, do not invent a name. Rank 3 that sound like a host reading a real note, not a landing page. </task> <constraints> - Do not invent a second question or a fake listener. - Do not answer the question in the open. - Do not write the mailbag body. - Spoken podcast open. Not show notes. Not a newsletter. Not HTML. </constraints> <format> Return spoken open, seconds, paying segment, invent-risk note. Star two I should record. </format>
Pro tip: Use the words they typed. If you polish the question into a topic label, it sounds like every other show.
Who Stays Who Skips Open
5/30โจ What it does
Claude writes six who-this-is-for spoken opens for [IDEAL LISTENER] that also name who should skip, plus one reason to stay. You still record both lines and keep the pair you would say to a friend, not a directory blurb.
You are a podcast scriptwriter who qualifies the listener out loud so the right people lean in. <context> I need spoken opens that name [IDEAL LISTENER], name who this episode is not for, and give one reason to stay through the first segment. Open only. Not directory listing copy and not HTML. </context> <inputs> - Ideal listener: [IDEAL LISTENER] - Who should skip this episode: [NOT FOR] - Why staying pays: [STAY REASON] - Episode topic: [EPISODE TOPIC] - Show name: [SHOW NAME] - Tone: [KIND / BLUNT / CALM] </inputs> <task> Write 6 who-stays-who-skips opens (30 to 50 seconds). Each names [IDEAL LISTENER] in the first 15 seconds, names [NOT FOR] without insult, and lands [STAY REASON] before any host bio. Do not pitch a sponsor in the open. Rank 3 that sound like a host, not a show-notes listen-if blurb. </task> <constraints> - Do not mock the people you send away. - Do not invent a persona I did not list. - No long origin story. - Spoken podcast open. Not show notes. Not a webinar qualify. Not HTML. </constraints> <format> Return spoken open, seconds, stay line, skip line. Star the two I should record. </format>
Pro tip: Say the skip line kindly and fast. If you apologize for five seconds after it, the stay line dies.
Solo Rundown
5 promptsFull Solo Timed Rundown
6/30โจ What it does
Claude writes a minute-marked spoken solo rundown for [SOLO TOPIC] with open, three segments, optional ad slot, and close. You still record each block on a timer and cut a story if block two runs long.
You are a podcast scriptwriter who writes a full solo rundown a host can record, not a blog outline and not show notes. <context> I need a complete spoken solo rundown: timed open, three segments, optional mid-roll hole, close. Spoken lines with pause marks. Not an interview question list. Not HTML. </context> <inputs> - The one thing I am teaching: [SOLO TOPIC] - Audience and level: [AUDIENCE] - Target length: [MINUTES] - The three segments I will actually record: [SEGMENT LIST] - Host voice: [VOICE] - Mid-roll I can take: [YES / NO] - Proof or story I can tell: [STORY I HAVE] - CTA I am allowed to use: [CTA] </inputs> <task> Write a [MINUTES] spoken rundown as a table (minutes, spoken lines, pause, optional music cue). Open in under 45 seconds. Teach only [SEGMENT LIST]. Use only [STORY I HAVE]. If [YES], mark a 30-second hole for an ad, do not write the ad. Close on [CTA]. Give a cut list if I run 4 minutes long. </task> <constraints> - Spoken lines, not bullet titles pretending to be the script. - Word count must fit [MINUTES] at a talking pace, not a read-aloud essay. - Do not invent a fourth segment or a fake case study. - Solo podcast rundown. Not show notes. Not a webinar teach block. Not HTML. </constraints> <format> Return the rundown table, a rehearsal timer per block, the cut list, and the one minute most likely to lose the listener. Paste-ready spoken lines only. </format>
Pro tip: Time each block standing up. If block two runs long in rehearsal, cut a story, do not speed through the close.
Three-Block Teaching Rundown
7/30โจ What it does
Claude writes one named three-block teaching rundown for [FRAMEWORK NAME] with a definition, three spoken uses, and a recap. You still record the three uses from notes and keep the take that does not read a list.
You are a podcast scriptwriter who turns a working method into three spoken solo blocks, not a white paper. <context> I need a solo teaching rundown that ships [FRAMEWORK NAME] so a listener can steal the name and the three parts. Spoken script. Not a course module and not HTML. </context> <inputs> - Framework name I will stand behind: [FRAMEWORK NAME] - The three parts, in my words: [PART A / PART B / PART C] - A real situation it explained: [SITUATION] - Audience: [AUDIENCE] - Voice: [TEACHER / PEER / BLUNT] - Time I can spend: [MINUTES] </inputs> <task> Write a [MINUTES] spoken rundown. Structure: 20-second stake, one-sentence definition, three blocks with a spoken example each tied to [SITUATION], when NOT to use it, then a 30-second recap. Mark pause points so I can breathe. Do not write an ad or a guest intro. </task> <constraints> - Do not invent a fourth part or a fake origin story. - Never read a bullet list aloud. Turn every list into spoken sequence. - Sentences under 22 words where you can. - Solo podcast rundown. Not show notes. Not a YouTube chapter script. Not HTML. </constraints> <format> Return the spoken rundown with timestamps, the recap, and a 5-line card I can glance at while I record. </format>
Pro tip: Use the names you already say on calls. If the framework needs a footnote, listeners will not repeat it at work.
Story Then Framework Rundown
8/30โจ What it does
Claude writes a story-then-framework solo rundown from [STORY NOTES] that lands the scene before the steps. You still record the story in your own words and keep the take that does not invent dialogue.
You are a podcast scriptwriter who puts one true story in front of a framework, not a memoir and not a syllabus. <context> I need a solo rundown that opens on [STORY NOTES], then teaches the framework. Spoken lines. Not show notes from a transcript. Not HTML. </context> <inputs> - Raw story notes I can defend: [STORY NOTES] - Details I will not share: [OFF LIMITS] - The framework or rule: [FRAMEWORK] - Audience: [AUDIENCE] - Target length: [MINUTES] - Voice: [QUIET / BLUNT] - CTA: [CTA OR NONE] </inputs> <task> Write a [MINUTES] spoken rundown. First 90 seconds are the scene from [STORY NOTES], not a date. Honor [OFF LIMITS]. Then teach [FRAMEWORK] in two or three spoken steps anchored to that scene. Recap in 20 seconds. If [CTA] exists, close on it. Mark [VERIFY] on any beat not in the notes. </task> <constraints> - Do not invent dialogue or a cleaner ending. - Do not start with I want to share a story. - Do not write interview questions. - Solo podcast rundown. Not show notes. Not a TED close. Not HTML. </constraints> <format> Return timed spoken rundown, verify flags, and the story minute I should record first. </format>
Pro tip: Tell the scene first, then name the steps. If you teach the framework before the story, the story sounds like a slide.
Case Study Solo Rundown
9/30โจ What it does
Claude writes a case-study solo rundown for [CASE] with before, decision, what broke, and the Monday action. You still record the what-broke beat and keep numbers you can defend.
You are a podcast scriptwriter who turns one case into a solo episode that does not sound like an advert. <context> I need a spoken solo rundown of [CASE]: before, decision, what broke, numbers I can say, Monday action. Not a customer interview and not HTML. </context> <inputs> - Case I can tell: [CASE] - Before state: [BEFORE] - Decision and tradeoff: [DECISION] - What broke: [WHAT BROKE] - Numbers I can say, or NONE: [NUMBERS OR NONE] - Who this helps: [AUDIENCE] - Target length: [MINUTES] - Voice: [PLAIN / DRY] </inputs> <task> Write a [MINUTES] spoken rundown. Beats: before scene, trigger, [DECISION], [WHAT BROKE] for at least 4 minutes if length allows, [NUMBERS OR NONE], what I would do differently, Monday action for [AUDIENCE]. If numbers are NONE, write the exact line I say instead of inventing a metric. </task> <constraints> - Do not invent a result or a quote. - The what-broke beat is mandatory. - Do not turn this into a sponsor read. - Solo podcast rundown. Not show notes. Not a webinar case slide. Not HTML. </constraints> <format> Return timed spoken rundown, the fallback line if numbers stay private, and the beat I should record twice. </format>
Pro tip: Force the what-broke beat. A case study with no failure is the episode listeners skip.
Twenty-Minute Tight Cut
10/30โจ What it does
Claude writes a 20-minute spoken solo cut of [SOLO TOPIC] that keeps one promise and drops the extra segments. You still record the tight cut on a timer and publish it when the long version will slip.
You are a podcast scriptwriter who writes the 20-minute solo that still sounds like the show, not a leftover. <context> I need a spoken 20-minute rundown of [SOLO TOPIC] that keeps one promise. Not a 50-minute dump compressed by talking faster. Not show notes. Not HTML. </context> <inputs> - Topic and the one promise: [SOLO TOPIC] / [PROMISE] - Segments I would record in a full week: [FULL SEGMENT LIST] - The one segment I must keep: [KEEP] - Story I can tell in 90 seconds: [STORY I HAVE] - Voice: [VOICE] - CTA: [CTA] </inputs> <task> Write a 20-minute spoken rundown: 30-second open on [PROMISE], [KEEP] as the body, [STORY I HAVE] as the only example, 25-second recap, [CTA]. List the segments from [FULL SEGMENT LIST] you dropped and why. Mark a 16-minute cut if I run long. Do not write an ad. </task> <constraints> - Do not keep two frameworks. - Do not invent a story. - Must sound finished, not like a downgrade. - Solo podcast rundown. Not show notes. Not a Shorts script. Not HTML. </constraints> <format> Return the 20-minute table, the 16-minute cut mark, dropped segments, and the minute I should record first. </format>
Pro tip: The tight cut is the show that ships on a bad week. If it needs a second framework, it is not a tight cut.
Interview
5 promptsSpoken Guest Intro
11/30โจ What it does
Claude writes five spoken guest intros for [GUEST NAME] that lead with why they are on this episode, not a resume. You still record the intro after you check the name, title, and pronunciation.
You are a podcast scriptwriter who writes a spoken guest intro a host can say on tape, not a bio page and not an outreach email. <context> I need spoken intros for [GUEST NAME]. Lead with why they are on this episode. Not a question ladder. Not show notes. Not HTML. </context> <inputs> - Guest name and how to say it: [GUEST NAME] / [PRONUNCIATION] - Why they are on this episode: [WHY THIS EPISODE] - Role I can defend: [ROLE] - One proof I can name: [PROOF I HAVE] - Show name: [SHOW NAME] - Seconds I can spend: [20-40] - Voice: [WARM / DIRECT] </inputs> <task> Write 5 spoken intros that fit [20-40] seconds. Each: [GUEST NAME] with [PRONUNCIATION] cue, [WHY THIS EPISODE] in the first sentence, [ROLE] in one clause, [PROOF I HAVE] in one clause, then a 5-second handoff into the first question I will ask (write the handoff, not the question bank). Rank 3 that do not sound like a LinkedIn summary. </task> <constraints> - Do not invent a company, title, book, or result. - Do not write 18 interview questions. - Do not write a booking email. - Spoken guest intro. Not show notes. Not a webinar speaker intro. Not HTML. </constraints> <format> Return spoken intro, seconds, pronunciation cue, handoff. Star two I should record. </format>
Pro tip: Lead with the reason this hour exists. A job-title stack is what every other host records.
Open Then First Handoff
12/30โจ What it does
Claude writes a spoken interview open for [GUEST NAME] that does the cold open, the intro, and the first handoff line. You still record the handoff and wait after it instead of stacking a second question.
You are a podcast scriptwriter who writes the spoken top of an interview, not a question ladder. <context> I need the first 60 to 90 seconds on tape: cold open or house ID, guest intro, first handoff. Spoken script. Not 18 questions. Not show notes. Not HTML. </context> <inputs> - Guest: [GUEST NAME] - Episode topic: [EPISODE TOPIC] - Why them: [WHY THIS EPISODE] - First thing I want them talking about: [FIRST BEAT] - Cold open I already chose, or NONE: [COLD OPEN OR NONE] - Voice: [WARM / DIRECT] </inputs> <task> Write 4 spoken tops (60 to 90 seconds). Each: if [COLD OPEN OR NONE] exists, use it in under 25 seconds; then the intro; then one handoff line into [FIRST BEAT]. Write a 3-second pause mark after the handoff. Do not write the rest of the interview. Rank 2 that sound like a host, not a conference MC. </task> <constraints> - Do not invent a guest quote or credential. - Do not write a full question bank. - Do not write a booking email or a prep pack. - Spoken interview open. Not show notes. Not HTML. </constraints> <format> Return spoken top, seconds, handoff line, pause mark. Star two I should record. </format>
Pro tip: Stop after the handoff and wait. If you stack a second question, you taught them to give a press answer.
Block Transition Lines
13/30โจ What it does
Claude writes spoken transition lines between [BLOCK LIST] so each interview block lands one point before you move. You still record the transitions on a card and say them when a block goes soft.
You are a podcast scriptwriter who writes spoken transitions between interview blocks, not the questions themselves. <context> I already have [BLOCK LIST]. I need the lines I say to leave a block and enter the next. Spoken. Not a question ladder. Not show notes. Not HTML. </context> <inputs> - Ordered blocks and the one point each must land: [BLOCK LIST] - Guest name: [GUEST NAME] - Episode promise: [PROMISE] - How I talk when I interrupt: [POLITE / FIRM] - Voice: [PLAIN / WARM] </inputs> <task> For each block in [BLOCK LIST], write: a 10-second landing line that restates the must-land point in my words, a 8-second transition into the next block, and a 6-second circle-back line if the point was missed. Then write two interrupt lines I can say out loud without sounding rude. Do not write the questions inside the blocks. </task> <constraints> - Do not invent a block I did not list. - Do not write 18 questions. - Do not write show notes or timestamps. - Spoken interview rundown lines. Not a webinar poll. Not HTML. </constraints> <format> Return a table: block, landing line, transition, circle-back, then the two interrupt lines I should keep on a card while I record. </format>
Pro tip: Write the out-line before you record. If a block ends without its point, the transition is how you circle back.
Mid-Tape Recap Redirect
14/30โจ What it does
Claude writes five spoken mid-tape recaps for [EPISODE PROMISE] that name what landed and point at the next block. You still record the recap only if the first half drifted, then keep the take that does not lecture the guest.
You are a podcast scriptwriter who writes a mid-episode spoken recap a host can drop in live, not an edit note. <context> Halfway through an interview I need a 20 to 35 second spoken recap of [EPISODE PROMISE], then a redirect into the next block. Not show notes. Not a question bank. Not HTML. </context> <inputs> - Episode promise: [EPISODE PROMISE] - What I think we already landed: [LANDED SO FAR] - Next block: [NEXT BLOCK] - Guest name: [GUEST NAME] - Voice: [CALM / DIRECT] </inputs> <task> Write 5 spoken mid-tape recaps (20 to 35 seconds). Each names [LANDED SO FAR] in the guest's work, not a topic label, then points at [NEXT BLOCK]. Include a version if [LANDED SO FAR] is thin (do not invent a win). Rank 3 that would not make a guest feel lectured. </task> <constraints> - Do not invent a point they did not make. - Do not write the next block's questions. - Do not write post-tape show notes. - Spoken interview rundown. Not HTML. </constraints> <format> Return spoken recap, seconds, redirect line, lecture-risk note. Star two I should keep on a card while I record. </format>
Pro tip: Recap in one breath, then the next block. If you recap for a minute, you stole the guest's air.
Co-Host Two-Voice Rundown
15/30โจ What it does
Claude writes a two-voice spoken rundown for [CO-HOST NAME] and you, with who opens, who intros the guest, and who takes the close. You still record a 3-minute table-read and keep the split you can do without talking over each other.
You are a podcast scriptwriter who writes a two-host spoken rundown, not two overlapping monologues. <context> [CO-HOST NAME] and I record together. I need spoken assignments: who opens, who intros [GUEST NAME OR SOLO], who takes ads, who closes. Spoken lines. Not a show bible. Not HTML. </context> <inputs> - Co-host name and how they talk: [CO-HOST NAME] / [THEIR VOICE] - My voice: [MY VOICE] - Guest or solo: [GUEST NAME OR SOLO] - Episode topic: [EPISODE TOPIC] - Target length: [MINUTES] - Who is better at ads: [AD OWNER] </inputs> <task> Write a spoken two-voice rundown for [MINUTES]: open (who says the first 20 seconds), guest intro or solo stake, three block labels with who leads each, ad hole owner, close owner. Give each host their exact first line and last line. Add two toss lines so we do not overlap. Do not write a full question bank. </task> <constraints> - Do not invent a third host. - Do not write show notes or a clip list. - Lines must sound like [MY VOICE] and [THEIR VOICE], not one blended brand voice. - Spoken interview or duo rundown. Not HTML. </constraints> <format> Return the two-column rundown (me / them), toss lines, and the 3-minute table-read order we should record first. </format>
Pro tip: Assign the first line and the last line before you hit record. If both of you open, the guest waits in silence.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Ads
5 promptsMid-Roll Host Read
16/30โจ What it does
Claude writes four spoken mid-roll host reads for [SPONSOR] that sound like the show, with a 60-second and a 30-second cut. You still record both cuts and keep the take that uses only claims the sponsor approved.
You are a podcast scriptwriter who writes a mid-roll host-read a host can say on tape, not a landing-page ad and not HTML. <context> I need spoken mid-roll reads for [SPONSOR]. Host voice. Timed. Not a pre-roll only. Not show notes. Not a Google ad. </context> <inputs> - Sponsor and what they sell: [SPONSOR] / [OFFER] - Claims I may say (approved): [APPROVED CLAIMS] - Claims I must not say: [OFF LIMITS] - URL or code: [URL OR CODE] - Show name and audience: [SHOW NAME] / [AUDIENCE] - Voice: [HOW I TALK] - Legal or disclosure I must say: [DISCLOSURE OR NONE] </inputs> <task> Write 4 mid-roll reads: two at 55 to 65 seconds, two at 25 to 35 seconds. Each: one-sentence bridge out of the last segment, the read using only [APPROVED CLAIMS], [URL OR CODE] said twice slowly, [DISCLOSURE OR NONE], then a one-sentence bridge back. Rank 2 that sound like me, not a brochure. </task> <constraints> - Do not invent a discount, a result, or a testimonial. - Honor [OFF LIMITS]. - Do not write a 3-minute brand story. - Spoken podcast ad. Not Facebook ad copy. Not a webinar offer. Not HTML. </constraints> <format> Return each read with seconds, URL pass count, disclosure line, and the two I should record first. </format>
Pro tip: Read the legal line once in rehearsal. If you stumble on the URL, write a slower sentence, do not mumble it.
Pre-Roll Twenty Second
17/30โจ What it does
Claude writes eight spoken 20-second pre-roll reads for [SPONSOR] that fit before the house intro. You still record three on a timer and keep the one that says the URL without rushing.
You are a podcast scriptwriter who writes a 20-second pre-roll a host can say before the intro, not a mid-roll essay. <context> I need spoken pre-rolls for [SPONSOR] that fit 18 to 22 seconds. Host voice. Not a 60-second mid-roll. Not HTML. </context> <inputs> - Sponsor and offer: [SPONSOR] / [OFFER] - Approved claims: [APPROVED CLAIMS] - URL or code: [URL OR CODE] - Show name: [SHOW NAME] - Voice: [HOW I TALK] - Disclosure: [DISCLOSURE OR NONE] </inputs> <task> Write 8 pre-roll reads (18 to 22 seconds, about 40 to 50 words). Each names [SPONSOR] in the first sentence, uses only [APPROVED CLAIMS], says [URL OR CODE] once clearly, includes [DISCLOSURE OR NONE] if required. Give a 12-second cut. Rank 3 I can record in one session. </task> <constraints> - Do not invent a claim. - Do not write a mid-roll. - No this episode is brought to you by as the only idea on every line. - Spoken podcast pre-roll. Not show notes. Not YouTube pre-roll. Not HTML. </constraints> <format> Return each read with word count, seconds, 12-second cut. Star three I should record. </format>
Pro tip: Twenty seconds is about 45 words. If the brand name is long, cut a clause, do not talk faster.
Host Voice Ad Not Brochure
18/30โจ What it does
Claude rewrites [SPONSOR BRIEF] into a spoken host-voice ad that uses your phrases and drops brochure words. You still record the rewrite and cut any line you would not say to a friend.
You are a podcast scriptwriter who turns a sponsor brief into host voice, not a press release read aloud. <context> I have [SPONSOR BRIEF]. I need a spoken ad that sounds like [HOW I TALK]. Mid-roll length. Not the brief copied. Not HTML. </context> <inputs> - Sponsor brief, pasted: [SPONSOR BRIEF] - How I talk, with sample lines: [HOW I TALK] / [SAMPLE LINES] - Words I never say: [BANNED PHRASES] - Approved claims I can keep: [APPROVED CLAIMS] - URL or code: [URL OR CODE] - Length: [30 / 60] </inputs> <task> Rewrite [SPONSOR BRIEF] into 3 spoken ads at [30 / 60] seconds. Keep only [APPROVED CLAIMS]. Use [SAMPLE LINES] as the voice test. Strike [BANNED PHRASES] and brochure words (leverage, seamless, cutting-edge). Say [URL OR CODE] clearly. Flag any claim in the brief I should not say. </task> <constraints> - Do not add a claim that is not in [APPROVED CLAIMS] or the brief. - Do not keep a sentence I would not say. - Do not write display ad copy. - Spoken podcast host-read. Not show notes. Not HTML. </constraints> <format> Return 3 timed reads, a banned-word strike list, and the one I should record first. </format>
Pro tip: Read the brief out loud once. Any sentence you would not say at dinner is the sentence to kill.
Two Reads Same Sponsor
19/30โจ What it does
Claude writes two different spoken reads for [SPONSOR] so episode A and episode B do not share a first sentence. You still record both in one session and rotate them so the mid-roll does not feel cloned.
You are a podcast scriptwriter who writes two distinct host-reads for the same sponsor, not one read with a swapped adjective. <context> I run [SPONSOR] on more than one episode. I need Read A and Read B that do not share a first sentence or the same example. Spoken. Not HTML. </context> <inputs> - Sponsor and offer: [SPONSOR] / [OFFER] - Approved claims: [APPROVED CLAIMS] - Two real examples I can tell: [EXAMPLE A] / [EXAMPLE B] - URL or code: [URL OR CODE] - Length: [30 / 60] - Voice: [HOW I TALK] </inputs> <task> Write Read A and Read B at [30 / 60] seconds. Different first sentence. Different example ([EXAMPLE A] vs [EXAMPLE B]). Same [URL OR CODE] and same legal claims. Then write a 15-second bumper if I already ran a read earlier in the episode. Mark any overlap you could not avoid. </task> <constraints> - Do not invent a third example. - Do not reuse the first sentence. - Do not write a landing page. - Spoken podcast ads. Not show notes. Not HTML. </constraints> <format> Return Read A, Read B, bumper, overlap note. Tell me which to record for this week's episode. </format>
Pro tip: Change the bridge and the example, not just the first adjective. Listeners hear a cloned mid-roll by week three.
Back From Break Rehook
20/30โจ What it does
Claude writes six spoken back-from-break rehooks for [NEXT SEGMENT] that earn the listen after the ad. You still record the rehook in the same session as the ad and keep the line that names a new reason to stay.
You are a podcast scriptwriter who writes the spoken rehook after a mid-roll, not another welcome. <context> The ad just ended. I need 8 to 15 second spoken rehooks that point at [NEXT SEGMENT] with a new reason to stay. Not the ad itself. Not show notes. Not HTML. </context> <inputs> - Next segment and the point it must land: [NEXT SEGMENT] - Episode promise: [PROMISE] - Guest or solo: [GUEST NAME OR SOLO] - Voice: [DIRECT / WARM] - I already said a recap before the ad: [YES / NO] </inputs> <task> Write 6 rehooks (8 to 15 seconds). Each names a new reason to stay that [NEXT SEGMENT] will pay. If [YES], do not repeat the pre-ad recap. If SOLO, do not invent a guest. Rank 3 that are not we are back, welcome back, or anyway. Give a 5-second cut. </task> <constraints> - No we are back as the whole line. - Do not resolve the next segment in the rehook. - Do not rewrite the ad. - Spoken podcast rundown. Not a YouTube mid-roll cliff. Not HTML. </constraints> <format> Return rehook, seconds, paying point, 5-second cut. Star two I should record after the ad take. </format>
Pro tip: A rehook is a new reason to stay, not we are back. If you only raise volume after the ad, people still skip.
Close
5 promptsRecap Then Subscribe Close
21/30โจ What it does
Claude writes five spoken closes for [EPISODE TOPIC] that recap one claim, then ask for a subscribe in one sentence. You still record the close in one take and keep the recap that matches what you actually said on tape.
You are a podcast scriptwriter who writes a spoken close a host can record, not show notes and not a directory blurb. <context> I need spoken closes: one-claim recap, then a subscribe ask. 25 to 45 seconds. Not a newsletter cut. Not HTML. </context> <inputs> - Episode topic: [EPISODE TOPIC] - The one claim I actually made or will make: [CLAIM] - Show name and where they subscribe: [SHOW NAME] / [APPS] - Voice: [WARM / DIRECT] - Extra ask I may add: [EXTRA ASK OR NONE] </inputs> <task> Write 5 spoken closes (25 to 45 seconds). Each restates [CLAIM] in one sentence, does not list every segment, then asks them to subscribe to [SHOW NAME] on [APPS] in one sentence. If [EXTRA ASK OR NONE] exists, put it after subscribe, not before. Rank 3 that do not sound like a YouTube end screen. </task> <constraints> - Do not invent a second claim. - Do not write show-notes summary paragraphs. - Do not write a 90-second trailer. - Spoken podcast close. Not HTML. </constraints> <format> Return spoken close, seconds, subscribe sentence. Star two I should record. </format>
Pro tip: Recap one claim, not the syllabus. If the close lists every segment, people leave before the ask.
Next Episode Tease Close
22/30โจ What it does
Claude writes six spoken next-episode teases for [NEXT EPISODE] that promise a real beat without giving the ending. You still record the tease only if that episode is booked, then keep the line you can pay next week.
You are a podcast scriptwriter who writes a spoken next-episode tease, not a season bible. <context> I need 15 to 25 second spoken teases for [NEXT EPISODE] at the end of this episode. Honest. Not show notes. Not HTML. </context> <inputs> - Next episode topic or guest: [NEXT EPISODE] - The one beat I can promise: [PROMISE I CAN PAY] - Status: [BOOKED / LIKELY / NOT BOOKED] - Show name: [SHOW NAME] - Voice: [WARM / DRY] </inputs> <task> If [NOT BOOKED], write 3 teases that do not name a guest or a date, plus a no-tease close I should use instead. If BOOKED or LIKELY, write 6 teases (15 to 25 seconds) that name [PROMISE I CAN PAY] without paying it. Mark LIKELY lines that should not use a date. Rank 2 I should record. </task> <constraints> - Do not invent a guest, a date, or a cliff the next episode cannot pay. - Do not write the next episode's full script. - Do not write a clip list. - Spoken podcast close. Not show notes. Not HTML. </constraints> <format> Return teases or the no-tease close, status flags, and the two I should record if the next episode is real. </format>
Pro tip: Tease a beat you can pay. A fake next week we go deep trains people to ignore the close.
Single CTA Close
23/30โจ What it does
Claude writes seven spoken single-CTA closes for [CTA] so the last 30 seconds ask one thing. You still record two closes and keep the one that does not stack a second ask.
You are a podcast scriptwriter who writes a spoken close with one ask, not a link dump. <context> I need spoken closes that do [CTA] and nothing else. 20 to 35 seconds. Not show notes with five URLs. Not HTML. </context> <inputs> - The one ask: [CTA] - Where to do it, in words I can say: [WHERE] - Episode claim I can recap: [CLAIM] - Asks I will not make in this close: [OTHER ASKS] - Voice: [PLAIN / WARM] </inputs> <task> Write 7 spoken closes (20 to 35 seconds). Each recaps [CLAIM] in one clause, then [CTA] at [WHERE] as a full sentence said twice if needed. Do not include [OTHER ASKS]. Give a 12-second CTA-only cut. Rank 3 that sound like a person, not a read of the show notes. </task> <constraints> - One ask. Do not sneak a second. - Do not invent a URL I did not put in [WHERE]. - Do not write the newsletter issue. - Spoken podcast close. Not a YouTube end screen. Not HTML. </constraints> <format> Return spoken close, seconds, 12-second cut. Star two I should record. </format>
Pro tip: One ask. If you stack subscribe, review, newsletter, and Slack, they will do none.
Guest Thanks Then Outro
24/30โจ What it does
Claude writes a spoken guest-thanks-then-outro for [GUEST NAME] with where to find them and the house close. You still record the thanks after you confirm the URL they want said on tape.
You are a podcast scriptwriter who writes the spoken thank-you and house outro, not a guest bio and not show notes. <context> I need 30 to 50 seconds: thanks to [GUEST NAME], where to find them, house outro. Spoken. Not a booking follow-up email. Not HTML. </context> <inputs> - Guest name and pronunciation: [GUEST NAME] / [PRONUNCIATION] - Where they asked to be sent: [THEIR URL OR HANDLE] - One thing they said I may thank them for: [THANKS FOR] - Show name and house outro I already use: [SHOW NAME] / [HOUSE OUTRO OR NONE] - Voice: [WARM / PLAIN] </inputs> <task> Write 5 spoken thank-you-plus-outros (30 to 50 seconds). Each: thanks tied to [THANKS FOR], [GUEST NAME] said correctly, [THEIR URL OR HANDLE] said slowly once, then [HOUSE OUTRO OR NONE] or a 10-second house close if NONE. Do not recap the whole interview. Rank 2 that do not sound like a conference MC. </task> <constraints> - Do not invent a handle, book, or company. - Do not write show-notes resource lists. - Do not write a follow-up email to the guest. - Spoken podcast close. Not HTML. </constraints> <format> Return spoken close, seconds, handle pass, house outro. Star two I should record after I confirm the URL. </format>
Pro tip: Confirm the handle they want said. A wrong URL in the outro is the clip they will remember.
Credits And Bed Close
25/30โจ What it does
Claude writes a spoken credits-and-bed close for [SHOW NAME] with names you can say and a music-out cue. You still record the credits in one take and drop the bed under the last line in the edit.
You are a podcast scriptwriter who writes a spoken credits close with a music-bed cue, not a YouTube end screen and not show notes. <context> I need 20 to 40 seconds of spoken credits for [SHOW NAME], then a bed-out. Spoken names only if I listed them. Not HTML. </context> <inputs> - Show name: [SHOW NAME] - Names I may credit on tape: [CREDIT NAMES] - Roles in words I use: [ROLES] - Music bed I have: [BED OR NONE] - Legal line I must say: [LEGAL OR NONE] - Voice: [PLAIN / WARM] </inputs> <task> Write 4 spoken credits closes (20 to 40 seconds). Use only [CREDIT NAMES] and [ROLES]. If a name is missing, write [CREDIT LATER] and do not invent a person. Mark the second the bed should rise. Include [LEGAL OR NONE]. Give a 12-second credits-only cut. Do not write show-notes credits. </task> <constraints> - Do not invent a producer, editor, or sponsor. - Do not write a subscribe paragraph here unless I put it in [LEGAL]. - Do not write YouTube end-screen copy. - Spoken podcast close. Not HTML. </constraints> <format> Return spoken credits, seconds, bed-rise cue, 12-second cut. Star the one I should record. </format>
Pro tip: Say names you can pronounce today. If a credit is a logo wall, skip it on tape and put it in the host notes later.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Series Arc
5 promptsSeason Premiere Spoken Open
26/30โจ What it does
Claude writes a spoken season-premiere open for [SEASON THEME] that names the through-line the later episodes must pay. You still record the premiere open and keep the through-line you can still say in episode six.
You are a podcast scriptwriter who writes the spoken open of a season premiere, not a 12-episode planning table. <context> I need a spoken season-premiere open for [SEASON THEME]: what this season is, who it is for, the through-line later episodes will pay. 45 to 75 seconds. Not a season roadmap memo. Not show notes. Not HTML. </context> <inputs> - Season theme: [SEASON THEME] - Through-line I will stand behind: [THROUGH LINE] - Show name: [SHOW NAME] - Who this season is for: [AUDIENCE] - Episodes I can already record: [EPISODE LIST] - Voice: [WARM / DIRECT] </inputs> <task> Write 5 spoken premiere opens (45 to 75 seconds). Each names [SEASON THEME] and [THROUGH LINE] before second 25, names [AUDIENCE], and teases one upcoming beat from [EPISODE LIST] without dumping the season. Give a 30-second cut. Rank 2 that sound like tape, not a manifesto. </task> <constraints> - Do not invent episodes I did not list. - Do not write the season grid or guest outreach. - Do not write show notes. - Spoken series-arc script. Not a YouTube season trailer with B-roll. Not HTML. </constraints> <format> Return spoken open, seconds, through-line sentence, 30-second cut. Star two I should record for episode one. </format>
Pro tip: Name a through-line you can pay by episode six. A season of conversations is not a through-line.
Mid-Season Bridge Recap
27/30โจ What it does
Claude writes a spoken mid-season bridge for [SEASON THEME] that recaps what already shipped and points at the next episode. You still record the bridge at the top of this week's tape and keep claims that match published episodes only.
You are a podcast scriptwriter who writes a spoken mid-season bridge, not a recap blog and not show notes. <context> I am in the middle of [SEASON THEME]. I need 30 to 50 spoken seconds that recap what already shipped and point at [NEXT EPISODE]. Not a season plan table. Not HTML. </context> <inputs> - Season theme and through-line: [SEASON THEME] / [THROUGH LINE] - Episodes that already published: [SHIPPED LIST] - Claims I can still stand behind: [CLAIMS SHIPPED] - Next episode I will record: [NEXT EPISODE] - Show name: [SHOW NAME] - Voice: [PLAIN / WARM] </inputs> <task> Write 5 spoken mid-season bridges (30 to 50 seconds). Use only [SHIPPED LIST] and [CLAIMS SHIPPED]. Point at [NEXT EPISODE] without paying it. If a planned episode is not in [SHIPPED LIST], do not recap it. Rank 3 that help a new listener join mid-season. </task> <constraints> - Do not invent an episode or a guest result. - Do not write show notes for the shipped episodes. - Do not write the next episode's full rundown. - Spoken series-arc script. Not HTML. </constraints> <format> Return spoken bridge, seconds, shipped claims used, next-episode tease. Star two I should record at the top of this week's episode. </format>
Pro tip: Recap shipped episodes, not the plan. If episode four slipped, do not tease it as if it aired.
Multi-Part Cliff Close
28/30โจ What it does
Claude writes a spoken cliff close for [PART NUMBER] that ends on a real unpaid beat in [NEXT PART]. You still record the cliff only if part two is booked, then keep the line you can pay on the next tape.
You are a podcast scriptwriter who writes a spoken multi-part cliff, not a binge-trailer and not show notes. <context> This episode is [PART NUMBER] of a set. I need a 20 to 35 second spoken close that ends on a beat [NEXT PART] will pay. Honest. Not HTML. </context> <inputs> - This part label: [PART NUMBER] - What this part actually covered: [COVERED] - Next part topic and status: [NEXT PART] / [BOOKED / NOT BOOKED] - The unpaid beat I can pay next: [UNPAID BEAT] - Show name: [SHOW NAME] - Voice: [DIRECT / WARM] </inputs> <task> If [NOT BOOKED], write a close that does not promise a part two, plus a line I can add later when it is booked. If BOOKED, write 6 cliff closes (20 to 35 seconds) that name [UNPAID BEAT] without paying it, and tell them [NEXT PART] is coming. Do not recap all of [COVERED]. Rank 2 I should record. </task> <constraints> - Do not invent a part two if it is not booked. - Do not write the next part's full script. - Do not write YouTube part-two end-screen copy. - Spoken series-arc close. Not show notes. Not HTML. </constraints> <format> Return cliffs or the no-promise close, status flags, and the two I should record if part two is real. </format>
Pro tip: The unpaid beat has to exist in part two. A fake we will finish this next time with no booking is a broken promise.
Season Finale Spoken Close
29/30โจ What it does
Claude writes a spoken season-finale close for [SEASON THEME] that lands the through-line, thanks the room, and leaves one honest next step. You still record the finale close after the last segment and keep the through-line you actually paid.
You are a podcast scriptwriter who writes a spoken season-finale close, not a year-in-review blog and not show notes. <context> I need 40 to 70 seconds at the end of the last episode of [SEASON THEME]: through-line landing, thanks, one next step. Spoken. Not a 12-episode recap essay. Not HTML. </context> <inputs> - Season theme and through-line: [SEASON THEME] / [THROUGH LINE] - What I actually paid on tape this season: [PAID CLAIMS] - What I did not get to: [UNPAID] - Thanks I can name: [THANKS NAMES OR LISTENERS] - Next step (off-season, next season, or none): [NEXT STEP] - Voice: [WARM / PLAIN] </inputs> <task> Write 5 spoken finale closes (40 to 70 seconds). Land [THROUGH LINE] using only [PAID CLAIMS]. Name [UNPAID] in one honest clause without promising a date unless [NEXT STEP] has one. Thank [THANKS NAMES OR LISTENERS] without a 20-name list. Rank 2 that sound finished, not like a cliff I cannot pay. </task> <constraints> - Do not invent a result or a guest I did not list. - Do not recap every episode. - Do not write the next season's premiere yet unless [NEXT STEP] is that script, and even then keep it to one sentence. - Spoken series-arc close. Not show notes. Not HTML. </constraints> <format> Return spoken close, seconds, paid through-line sentence, unpaid clause. Star two I should record after the last segment. </format>
Pro tip: Close the through-line you paid, not the one you hoped to pay. If episode nine drifted, say what you did pay.
Next Season Trailer Script
30/30โจ What it does
Claude writes a spoken next-season trailer for [NEXT SEASON THEME] with a 90-second and a 30-second cut. You still record the trailer after you lock three recordable episodes, then keep the cut that does not overclaim the slate.
You are a podcast scriptwriter who writes a spoken next-season trailer, not a positioning brief and not directory copy. <context> I need a spoken trailer for [NEXT SEASON THEME]: 90 seconds and a 30-second cut. Lines a host can record. Not a season grid. Not show notes. Not HTML. </context> <inputs> - Next season theme: [NEXT SEASON THEME] - Who it is for: [AUDIENCE] - Payoff every episode should keep: [PAYOFF] - Episodes or guests I can actually record: [RECORDABLE LIST] - Proof I can say: [PROOF I HAVE] - Show name and cadence: [SHOW NAME] / [CADENCE] - Voice: [WARM / DIRECT] </inputs> <task> Write a 90-second spoken trailer: hook in 8 seconds, [NEXT SEASON THEME], [AUDIENCE], [PAYOFF], one proof from [PROOF I HAVE], one tease from [RECORDABLE LIST], subscribe ask. Then a 30-second cut. Mark music cues. Flag any line that overclaims [RECORDABLE LIST]. Do not write the season table. </task> <constraints> - Do not invent a guest or a date. - First 8 seconds must work with no music. - Sentences short enough to say in one breath. - Spoken series-arc trailer. Not the hub positioning brief. Not HTML. </constraints> <format> Return 90-second script with timings, 30-second cut, music cues, overclaim flags. Name the cut I should record first. </format>
Pro tip: Record the trailer after three episodes are actually bookable. A trailer full of hoped guests is a promise you will break.
Free tool
Transcript Summarizer
Turn a meeting or video transcript into a summary with action items.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides