Public Relations
Corey HainesCommunityCreated by Corey Haines
- Skill
- Workflow
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to public relations for software products, focusing on earned media as a multiplier for distribution rather than a primary conversion driver. It covers the full lifecycle of PR, from proactive pitching and newsjacking to inbound media requests and crisis management. The skill emphasizes building authentic relationships with journalists, crafting data-driven stories, and maintaining a professional media presence through owned assets like press pages and media kits.
What it does
- Guides users through proactive journalist pitching and media list building.
- Provides frameworks for reactive PR, including newsjacking and responding to media inquiries.
- Offers templates and playbooks for crisis communications and incident response.
- Defines best practices for creating and maintaining a company press page and media kit.
- Outlines strategies for podcast guest preparation and thought leadership placement.
- Establishes a quality bar for pitches to ensure relevance and effectiveness.
When to use it
- When you have a compelling story, such as proprietary data, a unique opinion, or a significant milestone.
- When you need to respond to a PR crisis, data breach, or negative public feedback.
- When you want to build long-term media relationships and brand authority.
- When you are preparing for a podcast appearance or an op-ed submission.
- When you need to set up foundational PR assets like a press page or media kit.
Advantages
- Focuses on high-impact, sustainable PR strategies rather than vanity metrics.
- Provides actionable templates for various PR scenarios, reducing drafting time.
- Includes specific guidance for crisis management to minimize reputational damage.
- Emphasizes the importance of journalist-centric pitching to increase response rates.
- Integrates PR into the broader marketing and distribution strategy.
Usage examples
- “I have a new data set about AI adoption in finance. How do I pitch this to a journalist?”
- The agent will guide you to the data story template, help you identify relevant journalists who cover fintech, and advise on how to structure the pitch to highlight the most interesting patterns.
- “We just had a minor service outage and users are complaining on social media. What should I do?”
- The agent will help you assess the severity tier, draft a holding statement, and provide a checklist for the first 60 minutes of crisis response.
- “How do I build a media list for my SaaS product?”
- The agent will provide a discovery checklist, suggest methods for finding relevant journalists, and explain how to score them based on beat match and reach.
- “I'm going to be a guest on a popular tech podcast next week. How should I prepare?”
- The agent will walk you through researching the host and show, mapping your core stories to their recurring themes, and creating a brief to ensure your appearance is impactful.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/coreyhaines31/public-relations/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip public-relations.zip -d .agents/skills
Documentation by Corey Haines
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. Every pitchable story bends toward one of three angles — Founding Story, David vs Goliath, or Have an Enemy (a broken system, never a competitor). See references/story-angles.md.
Chase press for the compound effect, not the traffic bump. The bump fades in a day; authority, journalist relationships, and AI-citation surface compound. Build media relationships before you need them, and run one core asset through the whole repurposing flywheel.
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.
| Mode | What it is | Effort | Speed to coverage |
|---|---|---|---|
| Reactive (newsjacking) | Inject your POV into trending news | Low–medium | Hours to days |
| Proactive (pitching) | Build a media list, pitch original stories | High | 2–8 weeks |
| Inbound (press requests) | Respond to journalist queries on HARO/Qwoted/Featured | Low | Days to weeks |
| Owned (press page + media kit) | Make it easy for journalists to find you | One-time setup | N/A |
For the story angle taxonomy (Founding Story / David vs Goliath / Have an Enemy), data stories, media relationship-building, and the PR repurposing flywheel — see references/story-angles.md
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.
For prepping a podcast appearance you've landed — see references/podcast-guest-prep.md. Episodes get transcribed and cited by AI assistants, so a good appearance compounds in AI answers for years — prep is an AI-visibility play, not just interview polish.
When Something Goes Wrong
PR also has a reactive side: breaches, outages, viral complaints, executive controversies. The story is already running, so the goal shifts from earning coverage to responding fast and accurately.
Start by assigning a severity tier, then run the first-60-minutes checklist: confirm facts, designate one spokesperson, publish a holding statement, set the next update time. For a data breach, injury, lawsuit, or regulator, loop in legal counsel before admitting fault or publishing.
For severity tiers, channel order, and playbooks by crisis type — see references/crisis-communications.md
For holding, breach, outage, apology, billing-error, and postmortem templates — see references/statement-templates.md
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 [email protected] — 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:
| Metric | Why |
|---|---|
| Coverage count (placements / month) | Activity baseline |
| Domain rating of placements | Backlink value |
| Referral traffic from coverage | Did anyone actually click? |
| Brand search lift | Did people search you after reading? |
| AI citation rate (ChatGPT, Perplexity quote your brand?) | The new measurement that matters |
| Sales conversations citing the article | The 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.
"What's my story angle?" / "How do I get press with no news?"
Go to story-angles.md. Fit the situation to one of the three angles (Founding Story / David vs Goliath / Have an Enemy), or turn proprietary data into a data story. Remember: a milestone alone isn't a story — milestone with narrative is.
"Respond to this HARO query"
Go to press-platforms.md, use the response template, keep it under 200 words.
"I'm going on [podcast] next week — help me prep"
Go to podcast-guest-prep.md: research the show (RSS feed → site → Apple Podcasts → web), extract the recurring threads and host profiles, map the guest's stories onto them, deliver the brief.
"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.
"Get us more backlinks"
PR earns the highest-ceiling links but takes the most effort. For reclamation, partner pages, best-X lists, and the rest of a link program, use the link-building skill and treat PR as one of its tactics.
Files
- ATTRIBUTION.mdAdded by AutoGineer893 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md9.6 KiB
- evals/evals.json3.7 KiB
- references/crisis-communications.md8.4 KiB
- references/journalist-pitching.md10.8 KiB
- references/media-outlets.md9.1 KiB
- references/newsjacking.md8.4 KiB
- references/podcast-guest-prep.md5.5 KiB
- references/press-platforms.md6.7 KiB
- references/statement-templates.md5.5 KiB
- references/story-angles.md6.4 KiB
references/press-platforms.md
Press Request Platforms — Inbound PR
Journalists posting "I need a source for X" — you respond, sometimes you get quoted, sometimes you don't. The cheapest PR play available, but only if you treat it seriously.
Contents
The major platforms
Daily triage workflow
Response template
What makes a response get selected
What kills a response
ROI reality check
The Major Platforms
| Platform | What it is | Cost | Quality |
|---|---|---|---|
| Connectively (formerly HARO) | Daily email digest of journalist queries | Free tier; paid for filters | Mixed — high volume, lots of noise |
| Qwoted | Web app with journalist requests | Free; paid for outreach | Good — better-quality outlets |
| Featured | Web app, expert profiles, journalist requests | Free tier; paid pro | Good for thought-leadership snippets |
| Help A B2B Writer | Twice-weekly email of B2B queries | Free | High — B2B-focused, low spam |
| SourceBottle | Australia-focused but global queries | Free | Variable |
| Terkel | Roundup-style ("we asked 50 experts…") | Free | Volume-heavy, low effort |
| JournoRequests | X account aggregating tweets | Free | UK-skewed, real-time |
| #JournoRequest (X hashtag) | Live journalist requests | Free | Real-time, fast-moving |
Recommended starter set: Connectively + Qwoted + Help A B2B Writer + monitoring #JournoRequest on X.
Daily Triage Workflow
These platforms generate volume. Treat it like email triage — fast pass, deep response on the rare matches.
Step 1 — Filter (5 min)
For each digest / request feed:
Drop everything where you don't have direct experience or data
Drop everything from outlets your ICP doesn't read
Drop everything with a deadline you can't meet
Keep only requests where you can give a complete, named, on-the-record answer
Realistic conversion: 50 daily requests → 2–4 worth answering.
Step 2 — Deep response (15 min per request)
For each keeper:
Read the request 3 times — what's the actual angle?
Look up the journalist if possible — recent coverage, beat
Write a custom response (see template)
Send within their stated deadline (early > late)
Step 3 — Log
Track in a spreadsheet:
Date
Platform
Journalist + outlet
Topic
Response sent (yes/no)
Outcome (no response / passed / quoted / linked)
After 30 responses, you'll see which topics/platforms convert.
Response Template
Keep responses under 200 words. Journalists are scanning 50+ replies for one quote.
Hi [name],
Quick response to your request about [topic].
[Specific credential — 1 sentence. "Built X for 5 years" / "Led marketing at Y" / "Have analyzed N companies in space"]
The most important thing about [topic]: [your actual point in 2 sentences].
[A specific example, story, or data point — this is what gets quoted.]
[If applicable: a contrarian or surprising angle that differentiates from typical answers.]
Happy to expand on any of this, share data, or be quoted directly.
Feel free to use this attribution:
[Your name], [your title], [your company]
Contact for follow-up: [email + phone]Note the structure:
One-sentence intro
One-sentence credential
Two-sentence answer
Specific example (the quotable part)
Optional: differentiator
Clear offer
Pre-written attribution (saves them 30 seconds)
Contact info
What Makes a Response Get Selected
After analyzing hundreds of quoted responses, the patterns:
Quotable specificity
Bad: "Companies should focus on customer experience." Good: "When we A/B tested 47 onboarding flows, the version with a 30-second video at step 3 increased activation by 41%."
The good version is a quote. The bad version is filler.
Concrete credential
Bad: "As a marketing expert..." Good: "I've run growth at three Series B SaaS companies, all in B2B sales tooling."
Specificity beats title-stacking.
Story over advice
Bad: "It's important to track the right metrics." Good: "We almost shut down because we were optimizing for MRR when our real problem was activation. Once we switched to tracking 7-day activation, everything else followed."
Stories make articles. Advice makes filler.
Pre-formatted for their workflow
Pre-written attribution
Multiple quotable lines (let them pick)
High-res headshot link (don't attach)
One-line company description
Time match
Most quotes come from responses sent in the first 6 hours. After 24 hours, your chances drop sharply. Treat deadlines as if they're 24h earlier than stated.
What Kills a Response
Pitching your product when they asked for expert commentary
Generic advice that could come from any expert
Multiple "experts" from your company responding to the same request (looks coordinated, often is)
Hiring a PR firm to spam responses — journalists smell it
Demanding a link back to your site — most can't promise links
Ignoring the deadline by 1+ days
Long bio sections before the actual answer
Asking to "see the article before publication" — you don't get to do that
Asking what other experts said so you can differentiate — they won't tell you
ROI Reality Check
Most teams overinvest in these platforms because they're cheap. Be honest:
| Effort | Realistic outcome (90 days) |
|---|---|
| 5 hr/week, custom responses | 3–10 quoted placements |
| 1 hr/week, template responses | 0–2 placements |
| Outsourced to PR firm | Lots of submissions, few quotes |
A quote in a tier-1 outlet is worth:
A backlink (DR depends on outlet)
A sales-collateral asset ("As featured in...")
AI-citation surface area
Brand legitimacy in the abstract
A quote in a tier-3 outlet is worth:
A backlink, often nofollow
Maybe an Instagram screenshot
Decision rule: if you can sustain 5 hr/week of quality responses for 90 days, this is worth it. If you can only do 1 hr/week, skip it and invest in proactive pitching instead.
Setup Checklist
Before you start responding:
[ ] Press page exists and is current (see main SKILL.md)
[ ] One-line credential is written and rehearsed
[ ] Headshot is high-res and at a public URL
[ ] You have 3–5 specific stories / data points ready to deploy
[ ] You've decided which 2–3 platforms to use (don't try all 7)
[ ] You've blocked a daily 20-min window for triage
[ ] You're logging responses in a tracker
Without these, you're spamming and wasting their time and yours.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Corey Haines
- Publisher
- Corey Haines (Community)
- Source
- coreyhaines31/marketingskills · skills/public-relations · commit 96798cf
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Corey Haines.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download public-relations.zip