Four MIT collections ported — growthOS, openclaw-marketing-skills, Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45 commands, each naming its origin in its own frontmatter so the tree can be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names appeared in more than one collection and none of the copies were identical; the longest wins, which lands on the more developed text where they genuinely diverge. A fifth collection is deliberately absent. awesome-growth-hacking-skills carries NO licence, which leaves its author every right by default — and it is a list of links rather than a collection of skills, so there is nothing in it to port and no permission to port it with. It is cited as a directory to read. THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing vendor SDKs, running OAuth flows of their own, and ending with long-lived credentials in JSON files under .agents/ and ~/.growthos/ at mode 600. That is a secret on a disk with no rotation path, protected from other users and not from the agent — and one auth implementation per skill. Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect` is the one home for the flow and the platform skills defer to it by provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a tool and a curl cannot disagree. Two had nothing real behind them and now say so. There is no search_console provider, so that skill names what does answer the same questions (google_analytics, google_bigquery) and states that the remedy is a provider in hanzoai/cloud rather than a vendor SDK here. And getxapi-connect was a wrapper around a paid reseller of X's public data with the vendor's key in an env var; it is `listen` now, on our own x connector — a skill named after a vendor makes the vendor the capability and dies with it. The skills referenced paths that only existed inside the source repo, so the shared material they read is ported to reference/ and the paths rewritten. Three skills need the growthOS APPLICATION rather than its data; per the estate's own split an application belongs in hanzoai/ads, social, email or sms as a cloud plugin, so those three say what they need instead of carrying an import that resolves to nothing. Third-party product names are out of our prose and kept in the notices, which is where the licence requires them and the only place they belong. A skill's persona names a role, not somebody else's product. Co-authored-by: Hanzo Dev <[email protected]>
6.7 KiB
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.