podcast-pitch
Writes cold pitch emails that get a guest booked on podcasts - a specific subject line, an unfakeable personalized opener referencing a real episode, audience-first framing, brief credibility, two or three episode-ready talking angles, and a low-friction CTA, all under 150 words with a follow-up included. Use when someone asks "pitch me as a podcast guest", "write an email to this podcast host", "why are my podcast pitches getting ignored", or is promoting a book or launch through shows. Do NOT use for cold sales outreach - use cold-email-craft instead; for pitching investors by email, use vc-pitch-email.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- podcast-pitch
- metadata
- { "title": "Podcast Pitch" }
- description
- Writes cold pitch emails that get a guest booked on podcasts - a specific subject line, an unfakeable personalized opener referencing a real episode, audience-first framing, brief credibility, two or three episode-ready talking angles, and a low-friction CTA, all under 150 words with a follow-up included. Use when someone asks "pitch me as a podcast guest", "write an email to this podcast host", "why are my podcast pitches getting ignored", or is promoting a book or launch through shows. Do NOT use for cold sales outreach - use cold-email-craft instead; for pitching investors by email, use vc-pitch-email.
03 SKILL.md 正文
Podcast Pitch
You write cold pitch emails to podcast hosts to book a guest appearance. Hosts get many pitches; most are generic and ignored. Yours proves you've listened and offers their audience real value.
Process
- Gather: who's pitching, their expertise/credentials, the show name, the host, and (critically) specifics about the show - recent episodes, the audience, the host's interests.
- Identify the angle: what fresh, specific value can this guest give THIS audience.
- Write a short, personalized email.
Structure (keep it under ~150 words)
- Subject: specific and intriguing. Reference the show or a topic, not "Podcast guest request." e.g., "Episode idea: why most onboarding fails (and the fix)."
- Personalized opener: prove you listen. Reference a SPECIFIC recent episode and a genuine reaction - one real sentence. This single line separates you from 90% of pitches.
- Why their audience: connect your topic to what their listeners care about. Show you understand the show's focus.
- Who you are: one or two lines of relevant credibility - why you're worth an hour. Specific proof, not adjectives.
- What you'll talk about: 2-3 concrete episode angles or talking points. Make it easy for the host to picture the episode. Give them the value, ready to use.
- Easy CTA: low-friction next step. "Happy to send more topic ideas or hop on a quick call - does this fit your show?"
Rules
- Personalize or don't send. A generic pitch is instant delete. The opener must be unfakeable.
- Lead with their audience's benefit, not your book/product. Hosts care about a great episode, not your launch.
- Offer specific angles, not "I can talk about marketing." Hand them episode-ready ideas.
- Brevity. Hosts skim. Under 150 words, scannable.
- Credibility, briefly. Enough to establish you're qualified; link to a bio or past appearance rather than listing everything.
- No attachments in the first email; offer them.
- Make booking effortless - mention you have talking points, audio quality is good, you're flexible on scheduling.
Proof of value
- If you've guested before, link a clip or episode - it removes the host's risk.
- Mention if you'll promote the episode to your audience (a real perk to hosts).
Anti-patterns
- "I came across your podcast and thought..." (you didn't listen).
- Pitching yourself/your product instead of an episode.
- Vague topics with no hook.
- A long wall of credentials.
Output
Deliver: 3 subject-line options and 1 email body (word count noted), plus a short follow-up to send if no reply after a week. If you lack real show specifics, tell the user what to look up so the personalization is genuine, not faked.
04 同仓库更多 Skills
zone-2-cardio-plan
Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.