buzz-pitch
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/buzz-pitch && cp -r /tmp/buzz-pitch/plugins/ai-agency/tonone/skills/buzz-pitch ~/.claude/skills/buzz-pitchSKILL.md
# Media Pitching You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored. ## Steps ### Step 0: Identify Pitch Type - **A) Journalist pitch** — outreach to specific journalist/reporter - **B) Press release** — announcement for distribution - **C) Podcast pitch** — outreach to podcast host - **D) Newsletter pitch** — outreach to newsletter author for feature/mention Ask if not clear. ### Step 1: Journalist/Media Research For journalist pitches, research before writing: Use WebSearch: ``` - "[journalist name] recent articles" — what have they covered recently? - "[publication] [your topic]" — what angle does this pub take? - "[journalist] Twitter/X" — what are they currently interested in? ``` A pitch that proves you read the journalist's last 3 articles gets opened. A generic blast gets deleted. ### Step 2: Craft the Hook The hook is the reason a journalist cares — framed for their readers, not for you. Bad hook: "We're excited to announce our new product feature" Good hook: "Every engineering team loses 8 hours a week to meetings that could be automated — here's a study of 500 teams" Hook types: - **Data hook**: surprising statistic or study result - **Trend hook**: "First wave of [X] companies are now doing [Y]" - **Conflict hook**: "The conventional wisdom about [topic] is wrong" - **Character hook**: founder story, customer transformation - **Timeliness hook**: connects to current event or trend ### Step 3: Write the Pitch **A) Journalist pitch (under 200 words):** ``` Subject: [Specific — references their beat or recent article] [Their name], [One sentence why I'm reaching out — reference their recent work to prove you did research.] [The hook — one sentence. The most interesting thing about this story.] [Context — who you are, what the company is, why this story exists. 2-3 sentences.] [Why their readers specifically care. Be specific about the angle.] [Optional: offer an exclusive or first-look if relevant] Happy to send [data / case study / founder for interview]. Let me know if you'd like more. [Your name] ``` **B) Press release:** ```markdown # [Headline — present tense, active voice, news-forward] ## Subhead — [secondary detail that adds context] [City, Date] — [Company name], [one-line description], today announced [what happened]. [First paragraph — the news. Who, what, when, where. 2-3 sentences.] [Second paragraph — why it matters. Context, market size, problem being solved.] [Third paragraph — quote from founder or executive. Specific, not generic.] [Fourth paragraph — product/company context. What it is, who uses it.] [Fifth paragraph — customer quote if available.] **About [Company Name]** [2 sentences. What it is, who it serves, where to learn more.] Media contact: [name, email] ``` **C) Podcast pitch:** ``` Subject: Guest pitch: [topic that fits their show format] [Host name], Big fan of [recent episode title] — [one specific thing you took from it]. I'm [name], [role] at [company]. I've been thinking about [topic relevant to their show] and I think there's a story here your audience would love. The angle: [1-2 sentences on the specific insight or story you'd bring — not your company pitch] Happy to share some talking points if you want to see if there's a fit. [Your name] ``` **D) Newsletter pitch:** ``` Subject: Story idea for [Newsletter name]: [topic] [Author name], [One sentence showing you're a reader — specific issue or topic] Story idea: [Headline-style hook that would work in their format] [2-3 sentences of substance. What's the story? Why does it matter to their readers?] Happy to write a draft or provide assets if the angle fits. [Your name] ``` ### Step 4: Build a Target List For any pitch campaign, produce a prioritized media list: | Publication / Show | Journalist / Host | Beat | Audience fit | Notes | | ------------------ | ----------------- | ------------------- | -------------- | ---------------------------------- | | [Name] | [Name] | [Topics they cover] | [High/Med/Low] | [Recent article / why they'd care] | ### Step 5: Produce All Assets Deliver: 1. The pitch email(s) — ready to send 2. Media list with 10-20 targets (journalist name, publication, contact where available, personalization note) 3. Supporting assets checklist: what to attach/link (product one-pager, data, demo link, founder bio) ## Delivery Pitch must be ready to send. No "insert journalist name here" placeholders — either fill them or note "personalize for each recipient." Provide 3 subject line variations for A/B testing. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|