Menu
AI podcast production guide covering scripting, voice synthesis, multi-speaker dialogue, and distribution.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create multi-speaker dialogue audio. Use for: podcasts, conversations, audiobook scenes
Translate and dub audio/video to another language. Use for: localization, multilingual
Generate music from text description. Use for: background music, jingles, soundtracks
Generate sound effects from description. Use for: SFX, game audio, video soundscape
Transcribe audio to text, speech recognition. Use for: transcription, subtitles, dictation
Convert text to speech, narrate, voiceover. 32 languages, 22+ voices. Use for: TTS, audio
| name | ai-podcast-creation |
| description | AI podcast production guide covering scripting, voice synthesis, multi-speaker dialogue, and distribution. |
AI handles well:
AI cannot replace:
Use AI to produce what humans would take 5x longer to do, not to simulate what humans do best.
| Episode Format | AI Suitability | Notes |
|---|---|---|
| Solo explainer / educational | Excellent | Full script → voice synthesis works well |
| Scripted dialogue (2 hosts) | Good | Multi-speaker synthesis; needs natural break cadence |
| Interview simulation | Moderate | Requires careful scripting of "guest" lines |
| News roundup / briefing | Excellent | Pull from sources, summarize, synthesize voice |
| Narrative / documentary | Good | Strong for scripted storytelling |
| Live interview (real guest) | Not applicable | AI assists with prep, show notes, editing only |
Before generating any script, define:
Topic: [Specific, not broad]
Audience: [Who is listening, what do they already know]
Episode goal: [Educate / entertain / persuade / update]
Format: [Solo / dialogue / narrative]
Duration target: [5 / 10 / 20 / 45 minutes]
Tone: [Casual / authoritative / storytelling / conversational]
Key points to cover: [3–5 bullet points]
Point of view: [Are we neutral, opinionated, or analytical?]
Call to action: [What should listeners do after?]
Write a [X-minute] podcast script on [topic].
Format: [Solo host / Two hosts named A and B / Narrator-led]
Audience: [Describe]
Tone: [Casual and conversational / Educational and authoritative]
Structure:
1. Cold open (30 seconds): Start mid-thought or with a provocative question
2. Intro (60 seconds): Host intro, episode preview, what listener will get
3. Main content ([X minutes]): Cover these points: [list]
4. Transition bumpers between sections: "Let's talk about..." / "Now here's where it gets interesting..."
5. Outro (60 seconds): Summary, CTA, sign-off
Write in spoken language — contractions, short sentences, natural pauses.
Mark pauses as [PAUSE], emphasis as [EMPHASIS], and section breaks as [MUSIC STING].
Scripts read differently from written text. Follow these rules:
Sentence length: Spoken sentences should be under 20 words. Long sentences cause voice synthesis to lose natural rhythm.
Avoid: Semicolons, em dashes inside sentences, parenthetical asides — these confuse TTS models.
Use instead:
Written: "The results—which surprised even the researchers—showed a 40% improvement."
Spoken: "The results showed a 40% improvement. The researchers were genuinely surprised."
Numbers: Write out numbers in words when they appear mid-sentence.
Avoid: "3 out of 4 founders fail in year 1"
Use: "Three out of four founders fail in their first year"
Technical terms: Spell phonetically in brackets if the TTS model mispronounces:
"The company Xiaomi [shao-mee] announced..."
For two-host formats, write with distinct voice personalities:
Host A: [Analytical, asks clarifying questions, more formal]
Host B: [Conversational, uses analogies, brings it back to the audience]
Dialogue pacing rules:
Sample multi-speaker template:
[HOST A]: The report showed that [X]. What's surprising is [Y].
[HOST B]: Yeah, and if you think about it from [audience perspective], that means [implication].
[HOST A]: Exactly. So the question becomes: [question that leads to next point].
[HOST B]: And I think the answer depends on [nuance]. Let me explain what I mean...
| Tool | Strengths | Best For |
|---|---|---|
| ElevenLabs | High realism, emotion control, voice cloning | Single host, short clips, premium quality |
| Murf | Multiple voices, good for dialogue, team use | Multi-speaker, budget-friendly |
| PlayHT | Voice cloning, API access, multilingual | Developers building pipelines |
| Speechify | Fast generation, mobile-friendly | Quick drafts, newsletter-to-audio |
| Suno / Udio | Music generation for intro/outro | Background music, jingles |
| NotebookLM (Google) | Automatic dialogue from documents | Quick research podcasts |
[MUSIC STING IN]
Welcome to [Podcast Name] — [one-line show description].
I'm [host name/persona].
Today: [3 things the listener will take away, stated as outcomes].
Let's get into it.
[MUSIC FADE]
[MUSIC STING IN]
That's a wrap on today's episode.
The big takeaway: [1-sentence summary of core message].
If this was useful, [subscribe / share / leave a review / follow us].
Next time: [tease next episode topic in 1 sentence].
See you then.
[MUSIC FADE OUT]
Show notes serve SEO and listener convenience. Generate with this prompt:
Write show notes for a podcast episode titled "[title]" about [topic].
Include:
1. Episode summary (3–5 sentences, written for search engines)
2. Key timestamps (format: 00:00 — Topic name)
3. Top 5 takeaways (bullet points)
4. Resources mentioned: [list any if applicable]
5. Guest bio: [if applicable]
6. CTA: subscribe / follow / newsletter / community link
Target length: 300–500 words. Optimize for the keyword: [main topic keyword].
Audio file:
Publishing platforms:
Supporting content: