Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Podcast Distribution

ASecurity

Distribute podcasts effectively — directories, RSS feeds, show notes SEO, clips, and cross-promotion.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoaws

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill podcast-distribution --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Podcast Distribution?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Podcast Distribution
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-podcast-distribution/badge)](https://www.skillsdirectory.com/skills/aicodedecode-podcast-distribution)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: podcast-distribution
description: Distribute podcasts effectively — directories, RSS feeds, show notes SEO, clips, and cross-promotion.
category: enterprise-communication
---

## Overview

Great episodes mean nothing if nobody finds them. Podcast distribution covers the technical and promotional plumbing: RSS feeds, directory submissions, show-notes SEO, audiogram clips, and cross-promotion — the systems that put episodes in front of listeners. (For podcast marketing strategy, see podcast-marketer.)


Podcast distribution gets episodes to every listening app: RSS feeds, directories (Apple, Spotify, YouTube), and the optimization that makes shows discoverable.
Beyond plumbing, distribution strategy covers platform-specific optimization, video podcasts, and the analytics that guide growth.
## When to use

- Launching a podcast's distribution setup
- Submitting to podcast directories
- Improving episode discoverability
- Creating audiograms and clips
- Setting up RSS feeds correctly
- Growing listeners through cross-promotion

- Launching a podcast across platforms
- Optimizing for podcast SEO and discovery
- Expanding into video podcasts (YouTube)
- Understanding podcast analytics
## Core concepts

**RSS feeds.** The backbone: a valid RSS feed with proper enclosure tags, episode metadata (titles, descriptions, durations), artwork specs, and category tags. Validate the feed before launch — broken feeds break every directory listing. Your hosting platform usually generates this; verify it.

**Directory landscape.** Apple Podcasts and Spotify dominate, but distribute everywhere: Google Podcasts/YouTube Music, Amazon Music, Stitcher, Overcast, Pocket Casts, plus regional players. Submit once per directory; use your host's auto-distribution where available. Claim profiles on Spotify for Podcasters and Apple Podcasts Connect for analytics.

**Show notes SEO.** Episode titles (keyword + hook), descriptions (keyword in first 2 lines, timestamps, links), and dedicated web pages per episode. Google indexes show notes — they're a discovery channel most podcasters waste.

**Clips and audiograms.** 30–90 second vertical clips with captions and waveforms for social. Extract 3–5 per episode: the hook, the best insight, the funniest moment. Clips are the top discovery driver for new shows — design episodes with quotable moments.

**Cross-promotion.** Promo swaps with similar-sized shows (30-second trailers), guest appearances (their audience becomes yours), feed drops (full episode swaps), and network joining (when scale justifies it). Promote shows your target listeners already hear.

**Release strategy.** Consistent day/time (trains audience habits), batch-scheduling in your host, launch with 3+ episodes (binge-ability), and seasonal vs. continuous (seasons allow breaks without guilt; continuous builds habit).


**RSS fundamentals.** Your RSS feed is the source of truth: episode titles, descriptions, artwork, and audio files.
Hosting platforms generate the feed; directories poll it.
Validate feeds (podba.se, castfeedvalidator) — broken feeds silently stop updating everywhere.
Own your feed URL — platform lock-in via feeds is a real risk.
**Directory optimization.** Apple Podcasts (categories, ratings, reviews matter), Spotify (playlists, algorithmic recommendations), YouTube (SEO, thumbnails, chapters).
Each platform has distinct discovery mechanics — optimize per platform, not generically.
Submit everywhere listeners are: Apple, Spotify, YouTube, Overcast, Pocket Casts, Amazon.
**Video podcasts.** YouTube is now a top podcast discovery channel.
Record video (even simple static setup), optimize titles/thumbnails for YouTube SEO, add chapters, and link audio versions.
Video doubles production effort — start audio-only, add video when the show proves itself.
**Analytics.** Downloads (directional, not precise), unique listeners, consumption rate (do people finish?), follower growth, and cross-platform comparison.
Podcast metrics are notoriously fuzzy — track trends, not absolutes.
## Practical workflow

1. **Set up hosting.** Choose a host with: reliable RSS, auto-distribution, analytics (downloads, consumption, sources), and embed players. Configure artwork, categories, and descriptions for discoverability.
2. **Validate and submit.** Validate RSS, submit to all major directories, claim analytics profiles, and verify listings render correctly (artwork, descriptions, episode order).
3. **Build the episode template.** Title formula, description template (hook → summary → timestamps → links → CTA), show notes web page, and clip extraction plan. Consistency speeds production.
4. **Produce clips.** Per episode: 3–5 audiograms, 1 trailer-style cut, quote graphics. Post natively per platform (vertical for Reels/Shorts/TikTok, square for feeds). Always caption.
5. **Run cross-promotion.** Identify 20 similar shows, pitch promo swaps, book guest appearances, and track referral sources. One good guest spot can outperform months of organic growth.
6. **Measure.** Downloads per episode (7/30/90-day windows), consumption rate, follower growth, directory chart positions, website visits from show notes, and listener surveys (how did you find us?).

**Launch checklist:** RSS validated → directories submitted → 3 episodes ready → audiograms cut → guest promo scheduled → show notes pages live → analytics claimed → social accounts ready.


**Launch distribution checklist:** hosting configured → RSS validated → submitted to all directories (allow 1–2 weeks for approval) → website episode pages with show notes → YouTube versions → social clip pipeline → newsletter integration.
Directories approve at different speeds — submit early, launch when all are live.
**Ongoing optimization:** monthly analytics review → title/description A/B tests → back-catalog SEO (old episodes compound) → guest cross-promotion → playlist pitching.
Podcast growth is slow then sudden — consistency for 12+ months before judging.
## Common pitfalls

- **Broken RSS.** Invalid feeds silently break listings. Validate before and after any host changes.
- **Directory neglect.** Only on Spotify. Distribute everywhere — listeners have entrenched app habits.
- **Weak titles/descriptions.** "Episode 47" tells nobody anything. Keyword + hook in every title.
- **No clips.** Publishing audio-only and hoping for discovery. Clips are the marketing engine.
- **Inconsistent schedule.** Random drops train nobody. Pick a cadence and keep it.
- **Ignoring analytics.** Not knowing which episodes retain or where listeners come from. Check consumption rates monthly.
- **No web presence.** Episodes only in apps. Show-notes pages capture search traffic and give sharing a home.
- **Platform exclusivity.** Exclusive deals limit reach for unproven shows. Distribute widely until you have leverage to negotiate exclusivity profitably.
- **Neglecting show notes.** Thin descriptions hurt SEO and sharing. Write real show notes: summaries, timestamps, links — they compound in search.
- **Inconsistent audio quality.** Variable levels and background noise. Listeners forgive content flaws; they do not forgive audio flaws — invest in decent mics and editing.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →