agentsclimarketplace

Podcast writing

Skill DeltaCorvi/Claude-Skills-for-Smart-Crows/podcast-writing

A collection of reusable skills for Claude and other LLMs. Skills can be imported into Claude and other LLMs that use projects, or copy/pasted into any chatbot window.

Install
npx -y skills add DeltaCorvi/Claude-Skills-for-Smart-Crows --skill podcast-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guidance for writing content meant to be heard rather than read. Use this skill whenever the user asks for a podcast script, episode outline, audio narration, voiceover copy, radio segment, or any writing that will be spoken aloud to listeners, even if they don't use the word "podcast." Also use when reviewing or revising spoken-word content for clarity, pacing, or natural delivery.

SKILL.md

5.7 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Writing for Podcasts

Podcast writing is fundamentally different from writing for the page. Readers can pause, reread, skim ahead, and absorb information at their own pace. Listeners get only one pass. Every sentence must be understandable the first time it is heard.

The goal is not to sound simpler. The goal is to sound natural, clear, and engaging when spoken aloud.

Write for the Ear

This is the foundational principle. Sentences that look elegant on the page can sound awkward when spoken.

Prioritize clarity, rhythm, and flow over formal writing conventions. Use language that sounds natural in conversation. If a sentence feels uncomfortable to say out loud, rewrite it.

Use Conversational Language

Write how an informed person would explain a topic to a curious colleague.

Use contractions. Favor plain language over unnecessarily complex wording. Avoid phrases that sound academic, corporate, or overly formal unless the audience expects them.

The goal is to sound knowledgeable, not scripted.

Write for a Person, Not a Crowd

Podcasts are often most effective when they feel like a conversation rather than a presentation.

Address the listener directly when appropriate. Use "you" more often than "the audience" or "listeners." Imagine explaining the topic to one intelligent person rather than speaking to a room full of strangers.

Favor Natural Speech Rhythms

Short sentences improve clarity, but too many in a row can make the script feel robotic or simplistic.

Mix short, medium, and occasional longer sentences. Let related ideas stay together when it improves the flow. Break sentences apart when comprehension would benefit, not simply to make them shorter.

Aim for the cadence of thoughtful conversation rather than a series of bullet points.

Build in Signposting

Listeners cannot glance back at previous paragraphs or skim ahead to see where a discussion is going.

Help them navigate the content with clear transitions and structure.

Use phrases such as:

  • "Let's start with..."
  • "Now that we've covered that..."
  • "The next piece is..."
  • "This matters because..."

Good signposting reduces cognitive load and helps listeners stay oriented.

Lead with the Interesting Part

Podcast audiences are quick to disengage if the payoff takes too long.

Start with the question, observation, story, or conclusion that makes the topic worth hearing. Provide supporting details and context afterward.

Avoid lengthy introductions that delay the point.

Use Examples Generously

Listeners tend to retain stories, analogies, and examples more easily than abstract explanations.

When introducing a complex concept, follow it with a concrete example that illustrates the idea in practice.

If a listener can picture it, they are more likely to remember it.

One Idea at a Time

Avoid stacking multiple concepts into a single explanation.

Introduce a concept, explain it, provide an example if needed, and then move on. This is especially important when discussing technical subjects.

Listeners need time to process information before adding more.

Avoid Information Dumps

Dense blocks of facts, statistics, or terminology can overwhelm listeners.

Break complex information into smaller segments. Alternate explanation with examples, stories, questions, or observations that allow listeners to absorb what they have just heard.

Embrace Repetition Strategically

Readers can revisit earlier sections. Listeners cannot.

Important concepts can and should be reinforced throughout an episode. Repeating key ideas, phrases, or themes helps retention and comprehension.

Use repetition intentionally, not accidentally.

Write for the Host's Voice

A podcast script is performance material.

Consider the vocabulary, pacing, personality, and speaking style of the host. If a sentence sounds unnatural coming from their mouth, rewrite it.

The best podcast writing often feels as though the host is speaking spontaneously, even when every word was planned.

Consider Production Elements

Think beyond the words on the page.

Pauses, music, sound effects, clips, and multiple speakers can all influence pacing and emphasis. Write with awareness of how production choices may support the story being told.

Read Everything Aloud

Always read a script out loud before considering it finished.

This is the fastest way to identify awkward phrasing, unnatural transitions, tongue twisters, pacing problems, and sections that contain too much information.

If it sounds good when spoken, it will usually work well in a podcast.

Cut Ruthlessly

Every sentence should contribute something valuable.

Remove unnecessary qualifiers, repetitive explanations, tangents, and details that do not support the story or discussion. Tight writing creates better pacing and makes episodes easier to follow.

Remove Em Dashes

Before finalizing, remove any inline em dashes (—) from the script.

Em dashes are a page convention and don't correspond to any spoken pause a host would naturally make. Rephrase with a period, comma, or conjunction instead.

The Final Test

A well-written podcast script should sound like a knowledgeable person speaking naturally, not an essay being read aloud.

If the listener can follow the discussion without effort, stay engaged throughout the episode, and remember the key points afterward, the writing has done its job.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.