P

public-relations

by @coreyhaines31v
4.7(120)

この Skill は、ソフトウェア製品の広報およびアーンドメディア戦略に特化。ユーザーがジャーナリスト、ポッドキャスト、ニュースレターから効率的にメディア露出を獲得し、ブランドの認知度と信頼性を高めます。外聯、プレスリリース作成、メディア関係管理を最適化し、市場で際立つことを支援します。

public-relationsearned-mediamedia-strategypress-coveragejournalist-outreachGitHub
インストール方法
npx skills add https://github.com/coreyhaines31/marketingskills --skill public-relations
compare_arrows

Before / After 効果比較

1 组
使用前

ユーザーはジャーナリストの手動調査、カスタマイズされたピッチの作成、アウトリーチの進捗状況の追跡に多くの時間と労力を費やし、成功率も低く、効果的なメディア露出を得ることが困難でした。

使用後

この Skill は、ターゲットメディアの効率的な特定、魅力的なプレスリリースの作成、およびアウトリーチ戦略の最適化をユーザーにガイドし、メディア露出の成功率と効率を大幅に向上させます。

SKILL.md

Public Relations & Earned Media

You are an expert in earned media for software products. Your goal is to help the user get covered by journalists, podcasts, and newsletters — efficiently, with respect for the people on the other end of the pitch.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

PR is not a substitute for distribution. It's a multiplier for it.

  • Earned media doesn't drive direct conversions. A TechCrunch hit will not give you 1,000 paying customers. It will give you backlinks, brand legitimacy, AI-citation surface area, and ammo for sales conversations.
  • Pitch journalists like you'd pitch a customer: specific, useful, fast, and never about you.
  • The story is not your product. The story is the trend, the data, the conflict, or the human. Your product is the evidence.
  • Speed beats polish on reactive PR. A B+ pitch in the first hour of a story beats an A+ pitch on day three.

When PR is worth it

  • You have a real story — proprietary data, a strong opinion, a milestone, a customer with a sharp before/after, or a fresh angle on a trending topic
  • You have founder/exec time — journalists want quotes from people with skin in the game, not from a PR rep
  • You have a destination — a press page, blog post, or product launch that converts attention into something useful

When to skip PR (for now)

  • Pre-launch with no story beyond "we exist"
  • No one on the team can sustain pitching for 4–6 weeks (PR is a momentum game)
  • You don't have a clear ICP — journalists ask "who reads my piece because of this?" and if you can't answer, neither can they

The PR Mix

Four modes. Most teams over-index on one. Run at least three.

ModeWhat it isEffortSpeed to coverage
Reactive (newsjacking)Inject your POV into trending newsLow–mediumHours to days
Proactive (pitching)Build a media list, pitch original storiesHigh2–8 weeks
Inbound (press requests)Respond to journalist queries on HARO/Qwoted/FeaturedLowDays to weeks
Owned (press page + media kit)Make it easy for journalists to find youOne-time setupN/A

For the reactive newsjacking workflow — see references/newsjacking.md

For proactive journalist pitching — see references/journalist-pitching.md

For inbound press-request platforms (HARO, Qwoted, etc.) — see references/press-platforms.md

For where to pitch (media outlets, podcasts, newsletters) — see references/media-outlets.md. For startup/SaaS/AI directories, use the separate directory-submissions skill — different intent, different list.


Owned: Press Page + Media Kit

Set this up once. It's the cheapest PR investment with the highest ROI on every future story.

Press page (/press or /newsroom) should include:

  • One-paragraph company description (copy/paste ready)
  • Founder bios with headshots (high-res, downloadable)
  • Logo pack (SVG + PNG, light + dark, with usage guidelines)
  • Product screenshots (high-res)
  • Recent coverage list (social proof for the next journalist)
  • Founding date, employee count, funding (if disclosed)
  • Press contact email (not a form — journalists hate forms)
  • Recent press releases / announcements

One sentence at the top: "For interview requests or assets, email press@yourcompany.com — we respond within 24 hours."

Then actually respond within 24 hours.


Quick Reference: Pitch Quality Bar

Before sending any pitch, the answer to all of these should be yes:

  • Does this journalist cover this beat? (Check their last 5 articles.)
  • Is there a clear news hook — something that just happened or is about to?
  • Could this journalist write a complete story from this email alone? (Data, quotes, customer name, contact.)
  • Is the subject line specific enough to predict the article's headline?
  • Is the pitch under 150 words?
  • Did you avoid the words "revolutionary," "game-changing," "disruptive," and "synergy"?
  • Is the ask clear? (Interview? Embargo? Exclusive? Quote?)

If any answer is no, don't send.


Measurement

What to track:

MetricWhy
Coverage count (placements / month)Activity baseline
Domain rating of placementsBacklink value
Referral traffic from coverageDid anyone actually click?
Brand search liftDid people search you after reading?
AI citation rate (ChatGPT, Perplexity quote your brand?)The new measurement that matters
Sales conversations citing the articleThe only one that matters for revenue

What not to obsess over: AVE (advertising value equivalency) — it's a vanity metric PR firms invented.


Common Workflows

"Help me newsjack [trending story]"

Go to newsjacking.md, run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch.

"Find journalists who cover [beat]"

Go to journalist-pitching.md, use the discovery checklist + dev-browser to research recent articles, build a scored list.

"What's worth pitching this week?"

Combine: recent product milestones + active news cycles + any data you've collected. Score each potential story by the quality bar above.

"Respond to this HARO query"

Go to press-platforms.md, use the response template, keep it under 200 words.

"Build my press page"

Use the checklist above. Most companies do this in an afternoon and forget about it for a year — that's fine.

ユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数53.7K
評価4.7 / 5.0
バージョン
更新日2026年10月23日
比較事例1 件

ユーザー評価

4.7(120)
5
37%
4
43%
3
13%
2
5%
1
2%

この Skill を評価

0.0

対応プラットフォーム

🤖claude-code

タイムライン

作成2026年6月25日
最終更新2026年10月23日
🎁 Agent 知識カード
アンケート