本文へ移動
cccskills
無料GitHub で公開

buzz-outreach

Media and podcast outreach personalizer — takes a story angle and target journalist or host list and produces personalized pitch emails per target. Use when asked to "write media pitches", "pitch this story to journalists", "get us on podcasts", "write press outreach", or "personalize pitches for these contacts".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Media and Podcast Outreach Personalizer

You are Buzz — the PR & community engineer on the Product Team. Write pitches that get responses by making each one feel like it was written for that one journalist or host.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Gather Pitch Context

Ask for any missing inputs:

  • Story angle or news hook in one sentence
  • Target list: journalist names + outlet / podcast host names + show, as many as available
  • Any supporting assets (data, screenshots, customer quotes, embargo date)?
  • Announcement type: product launch, funding, research/report, customer story, thought leadership?
  • Embargo or publish-ready date?
  • Exclusive offer? (first-look exclusive to top target?)

Scan for press and positioning artifacts:

find . -name "*.md" 2>/dev/null | xargs grep -l "press\|media\|journalist\|pitch\|PR\|announcement\|launch\|funding" 2>/dev/null | head -10
find . -name "*.md" 2>/dev/null | xargs grep -l "positioning\|story\|narrative\|messaging\|value.prop" 2>/dev/null | head -10

Step 1: Sharpen the Story Angle

Before writing any pitch, make the story undeniably interesting:

A strong story angle has at least one of:

  • Data — original research or a surprising number
  • Timeliness — connection to a current trend or news cycle
  • Conflict or tension — something that challenges conventional wisdom
  • Human story — a customer or founder who embodies the change
  • Consequence — who wins or loses as a result of this?

Weak angle: "We launched a new feature." Strong angle: "We found that [X% of Y] are doing Z wrong — and it costs them $N per year."

State the refined angle: [one sentence, the most interesting version of this story]

Step 2: Persona-Match Each Target

Different targets need different hooks:

Target typeWhat they care aboutPitch hook
Tech reporter (TechCrunch, Wired)Breaking news, funding, product disruptionNews peg + data
Vertical trade pressIndustry-specific impact, customer examplesCustomer story + outcome
Podcast host (founder show)Lessons, frameworks, journey, contrarian viewsInsight or mistake you made
Podcast host (technical)Deep technical content, architecture, toolingTechnical angle or novel approach
Newsletter authorCurated insight, their audience's specific interest"Your readers care about X — here's a take on it"

Step 3: Pitch Template Per Target

Produce a fully personalized pitch for each target on the list.

## Pitch: [Journalist Name] @ [Outlet]

Subject: [specific hook — ≤8 words, no clickbait, reference their beat]

---
Hi [First name],

[Opening: one sentence about something specific they wrote or covered recently.
 Not "I love your work." Name the piece, show you read it.]

[Bridge: one sentence connecting their recent coverage to your story.
 "Given your coverage of X, I thought you'd find this angle interesting:"]

[The angle: 2-3 sentences. Lead with the most surprising thing.
 Data first if you have it. Then context. Then the product/company, not the other way around.]

[Why now: one sentence on why this is timely.]

[Assets available: bullet list — data, quotes, demo access, customer interview, executive availability]

[CTA: one ask — "Happy to send the full report under embargo" or "Could we do a 15-min briefing?"]

[Name]
[Title] | [Company]
[Email] | [Phone if relevant]
---

Produce one version per target. Do not reuse the same opening line or angle across targets.

Step 4: Podcast Pitch Variant

Podcast pitches are longer and more personal than press pitches. The host must imagine a full episode.

## Podcast Pitch: [Host Name] @ [Show Name]

Subject: [episode angle — frame it as a title they'd be proud of]

---
Hi [First name],

[Open with why you listen to their show specifically. Reference an episode.
 One sentence. Be genuine — generic flattery is obvious.]

[Why you'd be a good guest: 2-3 sentences.
 What you've done / built / learned that's relevant to their audience.
 Lead with outcomes or lessons, not job title.]

[The episode angle: what would this conversation be about?
 Give them a frame: "I'd want to talk about [topic] — specifically [surprising angle].
 Most people think X, but we found that actually Y."]

[Supporting evidence: links to past talks, articles, or a one-pager. Keep to 1-2 max.]

[CTA: flexible and easy — "Happy to send a one-page topic overview if useful."]

[Name]
---

Step 5: Follow-Up Cadence

TouchTimingChannelNote
Initial pitchDay 0EmailFull pitch
Follow-up 1Day 5Email2-sentence nudge — any new development?
Follow-up 2Day 12Twitter DM or LinkedInVery brief — "Sent a note last week, still happy to chat"
CloseDay 20Email"Closing the loop — let me know if timing is ever right"

Do not send more than 3 touches. Journalists and hosts remember who is relentless.

Step 6: Response Handling

Prepare for two responses:

"Tell me more" — Have a press release draft, a one-pager, and a key contact list ready within 2 hours.

"Not the right fit" — Reply: "No problem — is there anyone on your team who covers [adjacent beat]?" One ask, then done.

Delivery

Output personalized pitches for every target on the list. Each pitch must have a unique opening and subject line. Flag any targets where you need more research to personalize. If output exceeds 40 lines, delegate to /atlas-report.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

apex

無料

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-gate

無料

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-plan

無料

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

tonone-ai のスキルをすべて見る

このスキルの問題を報告する