SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsread-podcast-script-generator

read-podcast-script-generator

Writing & research

View repository

Updated 10-16 08:52

About this skill

Podcast Script Generator

Transform structured podcast notes into engaging, presenter-style video scripts.

When to Use

Use this skill when the user wants to:

  • Convert structured notes into presenter-style video scripts
  • Rewrite podcast summaries for short video content
  • Create conversational broadcast content from formal notes
  • Generate scripts with strong personal voice and recommendations

Workflow

Step 1: Get Source Material

Ask the user for the content source:

  1. Direct paste: User pastes text directly
  2. Daily podcast file: File from /Users/ugreen/Documents/obsidian/每日播客/
  3. Other file path: Any other markdown file

If user provides a file path, read it with Read tool.

Step 2: Analyze Content Structure

Identify:

  • Title & Guest: Podcast name and main speaker
  • Core Theme: Main topic discussed
  • Key Points: Numbered list of insights (usually 3-12 points)
  • Highlights: Dialogue excerpts or quotes
  • Data/Examples: Statistics, case studies, comparisons

Step 3: Apply Broadcasting Style

Read references/style-reference.md and references/example-conversions.md to internalize the target style.

Opening (Varied, Natural)

Avoid the fixed template. Instead, choose from these natural openings based on content:

  • "Today I want to recommend a podcast episode to you..."
  • "Recently I heard a particularly interesting episode..."
  • "This is the episode I've heard recently with the most non-consensus views on [field]..."
  • "The most rewarding podcast episode I heard this month..."
  • "If you follow [topic], you definitely have to listen to this podcast episode..."

Then introduce the guest naturally:

  • "The guest is [name], [one-sentence identity]..."
  • "Let me introduce [name], [achievements/background]..."

Add a hook specific to the content:

  • "A few months ago she said in a talk, 'Don't trust design processes,' and 3 months later she herself felt it was outdated..."
  • "He may be the only person on Wall Street who can both read financial statements and understand rocket engines..."

Content Transformation Rules

Rule 1: No "speaker" markers

  • Direct output without speaker labels
  • Use paragraph breaks to indicate natural pauses

Rule 2: Banned sentence patterns

DO NOT use these rigid contrasting patterns:

  • ❌ "not... but..."
  • ❌ "is... not..."
  • ❌ "forced by... to..."
  • ❌ "from... to..., from... to..." (overly structured parallel)

Instead, express contrast naturally:

  • ✅ "Design isn't actively wanting to change; it's changes on the engineering side forcing you to change"
  • ✅ "People used to treat this process as truth, but now it's basically dead"
  • ✅ "Engineers have already shifted to the command line and agent mode, while designers have started using IDEs"

Rule 3: Use conversational connectors SPARINGLY

Limit these phrases (max 1-2 per section):

  • "to put it plainly" → use "meaning" or just omit
  • "what does this mean" → use "why?" or just explain directly
  • "so you see" → use "the result is" or just show the result

Rule 4: Natural transitions

Instead of rigid structure markers, use:

  • "The first thing that surprised me was..."
  • "There's also a particularly counterintuitive finding..."
  • "There's a particularly interesting point here..."
  • "Even more exaggerated is..."
  • "Speaking of this, I can't help but mention..."

Rule 5: Personal commentary

Insert reactions naturally:

  • "I think this point is particularly worth thinking about"
  • "particularly counterintuitive"
  • "particularly interesting"
  • "surprised me particularly"

Rule 6: Explain concepts conversationally

When explaining complex ideas:

  • Start with the problem or context
  • Walk through the logic step by step
  • Use "for example" for analogies when needed
  • End with "that is to say" or just the conclusion

Closing

End naturally:

  • "Alright, that's all for today..."
  • "That's all for today's sharing..."
  • "That's all for today. If you also [related topic], I strongly recommend going to listen to the full podcast..."
  • "I'm [nickname], see you next time"

Step 4: Output Format

Produce:

  1. Full script without speaker markers, with natural paragraph breaks
  2. Estimated duration (250 words ≈ 1 minute)
  3. 3-5 suggested titles for the video
  4. Recommended hashtags/topics

Style Guidelines

Paragraph Structure

  • Each paragraph: 2-4 short sentences
  • Use empty lines between paragraphs for pacing
  • One idea per paragraph
  • Key data/quotes can stand alone

Tone

  • Conversational, like talking to a friend
  • First person "I" perspective
  • Natural enthusiasm without exaggeration
  • Occasional rhetorical questions

Language

  • Avoid written-style transitions
  • Prefer short sentences
  • Use spoken Chinese patterns
  • Keep technical terms but explain them naturally

Reference Materials

  • references/style-reference.md - Full example of target style
  • references/example-conversions.md - Before/after conversion examples with techniques

Constraints

  1. Preserve all factual information - change style, not substance
  2. Maintain accuracy of data, quotes, and attributions
  3. Target length: 750-1500 words (3-6 minutes of video)
  4. If source is too long, ask user which points to prioritize
  5. NO "speaker" markers
  6. NO rigid "not... but" patterns
  7. Use "to put it plainly" max 1-2 times in entire script