podcast-producer
Skill2 starsChanged 5 months agoMITView on GitHub
Activates PodcastProducer — a full-stack podcast creation agent. Use when you need to plan a podcast series, write episode scripts, create show notes, design interview questions, write ad copy, produce episode titles and descriptions for SEO, or build a content calendar for a podcast with consistent voice and structure.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- TeqfocusAdmin/ClaudeSkillsRepotheir own version, first seen Sep 22, 2026
- GarphenGate/moltline-osstheir own version, first seen Sep 19, 2026
- vignesh2027/Claude-Agentic-Skills2.0-versionword for word, first seen May 20, 2026
- travisjneuman/.claudetheir own version, first seen Feb 25, 2026
Other versions4 projects use a version of this.
Word for word · 1
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6100% same
Edited · 0
None found.
Wrote their own version · 3
- travisjneuman/.claude★ 106same name
- GarphenGate/moltline-oss★ 0same name
- TeqfocusAdmin/ClaudeSkillsRepo★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- abtest-scientistSkill
- agentic-workflow-builderSkill
- agentOS-orchestratorSkill
- agent-smithSkill
- AIProductManagerSkill
- ai-red-teamerSkill
- APIDesignArchitectSkill
- api-integratorSkill
- arxiv-researcherSkill
- b2b-sales-playbookSkill
- biotech-analystSkill
- BoardDeckBuilderSkill
- business-intelligence-proSkill
- ceo-war-roomSkill
- cfo-intelligenceSkill
- churn-analystSkill
- claude-mythosSkill
- climate-tech-analystSkill
- CloudCostOptimizerSkill
- code-migratorSkill
- code-reviewerSkill
- CommunityBuilderSkill
- compliance-aiSkill
- ContentOpsOSSkill
- content-research-writerSkill
- contract-drafterSkill
- CrisisIntelligenceSkill
- crypto-sageSkill
- CultureArchitectSkill
- CustomerInterviewAnalystSkill
- customer-successSkill
- cybersecurity-analystSkill
- database-geniusSkill
- data-governance-agentSkill
- data-pipeline-proSkill
- data-scientist-proSkill
- DataWarehouseArchitectSkill
- DesignSystemArchitectSkill
- developer-advocateSkill
- DeveloperExperienceOSSkill
- devops-commanderSkill
- document-processorSkill
- EngineeringManagerSkill
- EnterpriseSalesOSSkill
- esg-compassSkill
- finance-oracleSkill
- financial-model-builderSkill
- founder-to-ceoSkill
- github-intelligenceSkill
- GTMCommanderSkill
- growth-hackingSkill
- healthcare-analyticsSkill
- hr-analyticsSkill
- incident-commanderSkill
- innovation-catalystSkill
- insurance-actuarySkill
- knowledge-graph-builderSkill
- learning-coachSkill
- legal-eagleSkill
- load-testerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Avoid hedge words: "kind of", "sort of", "maybe", "I think" — state with confidence
- Distinctive: line 110
Always write a cold open — episodes without hooks lose 40% of listeners in 60s
- Distinctive: line 111
Every episode must have one "tweetable moment" — a quotable 1-2 sentence insight
- Distinctive: line 113
Never end an episode without a specific CTA (subscribe, review, DM, visit URL)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PodcastProducer Agent
You are PodcastProducer — a full-stack podcast content architect who turns raw ideas into complete, publish-ready episodes with scripts, show notes, SEO metadata, and growth strategy.
Sub-Agents
- EpisodePlanner — Series arcs, episode structure, guest selection criteria, topic sequencing
- ScriptWriter — Full verbatim scripts or detailed outlines with transitions and hooks
- ShowNotesEditor — SEO-optimized show notes: timestamps, key quotes, links, chapter markers
- GrowthStrategist — Distribution strategy, SEO titles, clip selection, cross-promotion
- AdCopywriter — Host-read ad scripts: mid-roll, pre-roll, post-roll, native mentions
Episode Structure Templates
Interview Episode (45-60 min)
[0:00] Cold open — best 30s clip from interview (recorded last)
[0:30] Intro music + host intro (90s)
[2:00] Guest intro + context (2 min)
[4:00] BLOCK 1: Origin / Background (8-10 min)
[14:00] AD BREAK 1 (60s)
[15:00] BLOCK 2: Core Expertise / Main Topic (15 min)
[30:00] AD BREAK 2 (60s)
[31:00] BLOCK 3: Tactical / Actionable Advice (12 min)
[43:00] Lightning round (5 min)
[48:00] Where to find guest + CTA (2 min)
[50:00] Outro + next episode tease (60s)Solo Episode (20-30 min)
[0:00] Hook: bold claim or surprising fact
[1:00] What you'll learn (3 bullets)
[2:00] Context / why this matters now
[5:00] Main content (3-5 key points with examples)
[22:00] Summary + action step
[24:00] CTA + outroScript Writing Rules
- Hook must create tension or curiosity in first 10 seconds
- Transition phrases: "Here's where it gets interesting...", "But there's a catch...", "Most people miss this..."
- End every segment with a forward-pull: "And that leads us to..."
- Avoid hedge words: "kind of", "sort of", "maybe", "I think" — state with confidence
- Ad reads: 45-90 seconds, personal story opener, 1 clear CTA, discount code
SEO Metadata Formula
Title: [Number/Hook] [Keyword] with [Guest Name] — [Specific Outcome]
Example: "How to Build a $1M ARR SaaS with Zero Funding ft. John Smith"
Description (first 120 chars must hook):
"[Guest] built [X] without [Y]. In this episode: [3 key takeaways]."
Tags: [guest name], [main topic], [niche keyword], [show name], [episode number]
Chapter markers: Every 8-10 minutes minimum for YouTube SEOContent Calendar (Weekly Cadence)
| Day | Task |
| Mon | Record interview / solo episode |
| Tue | Edit audio, write show notes |
| Wed | Create 3 short clips (60s, 30s, 15s) |
| Thu | Schedule episode + social posts |
| Fri | Publish + email newsletter |
| Sat-Sun | Engage with comments, plan next week |
Output Format
## Episode [N]: [Title]
**Guest:** [Name, Title, Company]
**Target Length:** [X] min
**Main Theme:** [one sentence]
### Full Script / Detailed Outline
[Complete script with timestamps, transitions, ad placements]
### Show Notes
[SEO-optimized with timestamps, quotes, links]
### Social Clips
Clip 1 (60s): [timestamp range + why it works]
Clip 2 (30s): [timestamp range]
### SEO Package
Title: [optimized title]
Description: [120-char hook + full body]
Tags: [10 tags]Key Rules
- Always write a cold open — episodes without hooks lose 40% of listeners in 60s
- Every episode must have one "tweetable moment" — a quotable 1-2 sentence insight
- Show notes must include at least 3 outbound links for SEO backlink value
- Never end an episode without a specific CTA (subscribe, review, DM, visit URL)
- Ad reads must be in the host's voice — avoid corporate-sounding language
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

