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]>
8.3 KiB
Newsjacking — Reactive PR Workflow
Injecting your POV into a story that's already trending. Done well: free distribution off a wave of attention. Done badly: cringe at best, brand damage at worst.
Contents
- When newsjacking works (and when it doesn't)
- The detect → score → angle → pitch loop
- Newsworthiness scoring rubric
- Story angle library
- Speed: the only thing that matters
- Sources & tooling
- Failure modes
When Newsjacking Works
- Tech/regulatory news in your category — new law, new platform launch, competitor pivot, big acquisition
- Industry data drops — a major report drops, you have a sharper take or contradicting data
- Public conversation — a debate or controversy where your expertise is genuinely relevant
- Seasonal/cyclical moments — earnings season, year-end reviews, conference weeks
When to Skip
- Tragedies, accidents, deaths — no exceptions. Don't.
- Politically charged stories unless your brand explicitly takes political stances
- You have no genuine expertise in the area
- The window is already closed — if a story is 48h+ old and you weren't first, you're late
- The angle is "we have a product for this" — that's marketing, not journalism
The Loop
A repeatable workflow Claude can run on demand or daily.
- Detect — surface trending stories in your category (see Sources & Tooling)
- Score — apply the newsworthiness rubric; drop anything below threshold
- Angle — generate 2–3 angles per story using the angle library
- Validate — sanity-check: do you actually have the expertise/data to back this angle?
- Pitch — draft a tight pitch to 3–5 journalists who cover this beat (see journalist-pitching.md)
- Post — also publish on your blog, LinkedIn, X — it builds the trail journalists check before quoting you
Output format Claude should produce:
NEWSJACK CANDIDATE — 2026-06-10
Story: "EU passes AI Act amendment requiring agent registration"
Source: TechCrunch, 3h ago
Score: 8/10 (high relevance, fresh, you have proprietary data)
Angles:
1. Data hot take: "Our analysis of 12,000 agent deployments shows 73% would fail this requirement"
2. Contrarian: "Why the registration rule will hurt safety, not improve it"
3. Customer story: "How [customer] is preparing — interview offer"
Recommended: #1 (you have unique data, strongest hook)
Pitch draft: [see journalist-pitching.md for template]
Target journalists: [list with rationale]
Newsworthiness Scoring Rubric
Score each candidate 1–10 on five dimensions, multiply by the weight, then sum. Max possible: 80 (10 × the 8x weight total).
| Dimension | What it measures | Weight |
|---|---|---|
| Timeliness | Story <24h old? Window still open? | 2x |
| Relevance | Genuinely in your expertise area? | 2x |
| Angle uniqueness | Can you say something no one else is saying? | 2x |
| Authority | Do you have data, customers, or experience to back it? | 1x |
| Reach potential | Will this story keep growing or has it peaked? | 1x |
Threshold: weighted total ≥ 50/80. Below that, skip.
Auto-disqualify if:
- The story is about something tragic
- Your angle is "I disagree" with nothing to back it
- You haven't actually formed an opinion — you just want to be quoted
Story Angle Library
Use these templates to generate angles fast.
1. Data hot take
"We analyzed [N] [things] after [event]. Here's what we found."
Best when you have proprietary data. The journalist gets a stat, you get the citation.
2. Contrarian
"Everyone says [popular take]. Here's why they're wrong."
Best when you can defend the position with specifics. Weak when it's just contrarianism for attention.
3. "We predicted this"
"Six months ago we wrote [thing] — here's what's happening now and what's next."
Best when you actually did predict it. Lethal to your credibility if you didn't.
4. Customer impact
"Here's a [customer type] who's directly affected. We can put you in touch."
Best for B2B. Reporters love named customers willing to talk.
5. Insider explainer
"This story is complicated. Here's what's actually happening."
Best when most coverage is missing nuance. You're not arguing — you're educating.
6. Trend connector
"This isn't isolated — it's part of a bigger shift we're seeing in [pattern]."
Best when you have several data points or examples to connect.
7. Founder POV
"As someone who's built in this space for [X years], here's the part most people are missing."
Best for opinion pieces / op-eds. Weak as a soundbite pitch.
Speed: The Only Thing That Matters
Newsjacking decays fast. Approximate windows:
| Story type | Effective window |
|---|---|
| Breaking tech news | 4–12 hours |
| Major regulation / policy | 24–48 hours |
| Industry report / data drop | 24–72 hours |
| Conference announcement | Same day |
| Acquisition / funding news | 12–24 hours |
Implication: if you can't draft and send within the window, don't bother. Set up the loop so detection → pitch takes <2 hours.
Sources & Tooling
Reuses tooling from the social skill's listening workflow. Same install: brew install jq.
Google News RSS (no auth)
# Replace QUERY with topic (use + for spaces, %22 for quotes)
curl -s "https://news.google.com/rss/search?q=QUERY&hl=en-US&gl=US&ceid=US:en" \
| xmllint --xpath "//item[position()<11]" - 2>/dev/null
Hacker News (Algolia) for tech stories
SINCE=$(($(date +%s) - 86400))
curl -s "https://hn.algolia.com/api/v1/search_by_date?query=QUERY&tags=story&numericFilters=created_at_i>${SINCE}" \
| jq '.hits[] | {title, url, points, num_comments, created_at, hn_url: ("https://news.ycombinator.com/item?id="+.objectID)}'
Reddit (for category-specific subs)
curl -s -A "newsjack/1.0" \
"https://www.reddit.com/r/SUBREDDIT/top.json?t=day&limit=15" \
| jq '.data.children[].data | {title, url, score, num_comments, created_utc}'
Journalist research (browser-driven)
For finding which journalists are covering the story right now:
- dev-browser → Google News search for the story → click through to articles → note the bylines
- Then go to those journalists' X / LinkedIn / Muck Rack profile to confirm beat and recent coverage
See also journalist-pitching.md for the full discovery workflow.
Source list
For repeatable monitoring, add a "Newsjacking topics" section to .agents/listening-sources.md (template in the social skill's references):
## Newsjacking topics (Google News RSS)
- "AI agent regulation"
- "[your category] funding"
- "[your competitors] OR [adjacent competitors]"
## Industry data drops (RSS / manual)
- Pitchbook reports
- a16z state of [industry] reports
- [your category] benchmark reports
Failure Modes
Things that have ended careers and brands.
- Tragedy-jacking — Oreo's 2013 Super Bowl tweet worked. Most attempts since have not. Wartime, disasters, deaths: don't.
- The forced fit — "Here's our take on [trending story] — it's actually about [our product]." Journalists see through this instantly.
- The empty take — pitching "we have an opinion" without specifics. Journalists need a quote-worthy line, not "we're closely watching this."
- Speed without judgment — being first with a bad take is worse than being late with a good one. The 30-minute "is this brand-appropriate?" gut check exists for a reason.
- Pitching the same angle to 50 journalists — they talk. Get caught once, lose the relationships.
- No follow-through — pitch goes out, journalist responds in 20 minutes, founder takes 6 hours to reply. Story moves on.
Companion Practice: The Public Trail
Every newsjack pitch is stronger if the journalist can find evidence you've been thinking about this publicly. Before pitching:
- Publish a short post (blog, LinkedIn, X thread) with your take
- Reference it in the pitch ("more thinking here: [link]")
- This signals you're not opportunistic — you're an actual voice in the space
If you don't have time to publish, you're probably not ready to pitch.