Skip to content

JasonColapietro/suede-creator-skills / skills/suede-public-relations

suede-public-relations

Verified

Build earned-media angles, sourced media lists, journalist and podcast pitches, reporter replies, and press kits with consistent entity facts. Use when asked to "draft a journalist pitch", assess newsjacking, or prepare third-party coverage for search and AI citations. Returns review-ready drafts and measurement steps. NOT FOR: directory submissions (use suede-directory-submissions), release packaging (use suede-launch-packaging), social posts (use suede-social), or sending without approval.

FileKindSize
CARD.mdmarkdown4.3 KB
SKILL.mdskill md11.8 KB
agents/openai.yamlconfig590 B
evals/evals.jsonconfig2.8 KB
references/journalist-pitching.mdmarkdown12.6 KB
references/media-outlets.mdmarkdown6.3 KB
references/newsjacking.mdmarkdown9.3 KB
references/press-platforms.mdmarkdown7.3 KB
references/worked-handoff.mdmarkdown1.6 KB

references/press-platforms.md

View on GitHub
# Press Request Platforms: Inbound PR

Journalists post source requests and may select a useful response. This reference
produces research-backed drafts only. Every platform submission runs the
send-approval handover in SKILL.md ("Quick Reference: Pitch Quality Bar") before
any external action.

## 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

Status checked October 2026. Plans, prices, and ownership change; confirm on each site before recommending a paid tier.

| Platform | What it is | Notes |
|----------|-----------|-------|
| **[HARO](https://www.helpareporter.com)** | Journalist query digest | Cision shut down its Connectively rebrand in December 2024; Featured bought HARO and relaunched it in April 2025. Expect high volume; filter hard. |
| **[Qwoted](https://www.qwoted.com)** | Web app with journalist requests | Free and paid tiers; tends toward better-known outlets |
| **[Featured](https://featured.com)** | Expert profiles and journalist questions | Formerly Terkel (rebranded 2023); roundup-style answers, also operates HARO |
| **[Help A B2B Writer](https://helpab2bwriter.com)** | Email of B2B writer queries | B2B-focused |
| **[SourceBottle](https://www.sourcebottle.com)** | Query digest | Australia-focused with global requests |
| **#JournoRequest** (X and other social platforms) | Live journalist requests | Real-time, UK-skewed |

**Starter set:** Qwoted and Help A B2B Writer for B2B, HARO or Featured for volume, plus a saved search for `#JournoRequest`. Prefer requests from outlets that AI assistants already cite for your category (see "PR as Citation and Entity Building" in SKILL.md).

---

## Daily Triage Workflow

Treat platform volume, deadline pressure, and match rate as current-account
variables. Review only the authorized feed and size the triage pass to the
user's capacity.

### 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**

Record the current feed volume and match rate; do not import a universal
conversion assumption.

### Step 2: Draft a response

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](#response-template))
- Record the stated deadline and return the exact response draft for approval

### Step 3: Log

Track in a spreadsheet:
- Date
- Platform
- Journalist + outlet
- Topic
- Response sent (yes/no)
- Outcome (no response / passed / quoted / linked)

Review a predeclared, capacity-bounded cohort and report uncertainty; expand
only when another cohort is justified.

---

## Response Template

Follow the current request or outlet limit. If none is published, start concise
and preserve the evidence needed to answer the question completely.

```
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:**
1. One-sentence intro
2. One-sentence credential
3. Two-sentence answer
4. Specific example (the quotable part)
5. Optional: differentiator
6. Clear offer
7. Pre-written attribution (saves them 30 seconds)
8. Contact info

---

## What Makes a Response Get Selected

Use these as drafting hypotheses, then compare them with current outlet
instructions and the user's observed results:

### 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
Use the actual stated deadline, request timestamp, story velocity, and
current-account results to prioritize drafts. Never invent an earlier deadline,
and let no deadline shortcut the send-approval handover in SKILL.md.

---

## 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:

| Test effort | Outcome to measure |
|--------|----------------------------|
| Capacity-approved custom drafts | Qualified responses, quotes, links, and time cost |
| Lower-capacity draft cohort | Same measures, reported with sample size |
| 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:** define an approved effort cap and evaluation window, then
compare qualified outcomes and opportunity cost with proactive pitching. Do not
use a fixed weekly-hour or 90-day threshold as a universal rule.

---

## 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 a bounded set of verified stories or data points appropriate to
      the selected requests
- [ ] You've selected only the currently authorized platforms that fit the
      audience and review capacity
- [ ] You've approved a triage timebox derived from current feed volume
- [ ] You're logging responses in a tracker

Without these, you're spamming and wasting their time and yours.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall