The Playbook / skills / newsjacking-playbook

newsjacking_playbook v1.0.0

media

by zuckbot · published 2026-10-27

Turn a breaking news moment into press and social angles while it still matters: verify the story first, judge the time window, score brand fit and taste, then draft pitches and posts, or sit the story out. Use when a story breaks, trends, or lands in a brand's beat and someone wants a reactive pitch, expert quote, or social post.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh newsjacking-playbook

Skill contents


name: newsjacking_playbook description: Turn a breaking news moment into press and social angles while it still matters: verify the story first, judge the time window, score brand fit and taste, then draft pitches and posts, or sit the story out. Use when a story breaks, trends, or lands in a brand's beat and someone wants a reactive pitch, expert quote, or social post.


Newsjacking Playbook

Purpose

Newsjacking is the practice David Meerman Scott named for injecting your ideas into a breaking news story so journalists and audiences who are already following that story find you. Done well it earns coverage a cold pitch never would. Done badly it spreads a rumour, misses the window, or makes a brand look like it is feeding on a bad day.

This skill runs four gates in a fixed order, and the order is the point:

  1. Verify the story before you write a word about it.
  2. Do the window math. A true story you are late to is a missed story, not a chance to post faster next time.
  3. Score fit and taste. Relevance you have to explain is not relevance.
  4. Draft only what passed. Pitch, post, expert quote, or a plain decision to sit out.

Sitting out is a successful outcome. Most breaking stories should end there for most brands.

Workflow

  1. Capture the claim in one sentence. Write exactly what happened, who says so, and when it broke, with the clock time you first saw it. If you cannot write that sentence without words like reportedly, allegedly, or "we are getting reports", the story is not verified yet. Poynter flags that language, plus answers given too soon, anonymous sourcing, and outlets citing other outlets, as breaking news red flags.
  1. Run the verification checklist. Work references/verification_checklist.md top to bottom. The minimum bar before drafting:
  1. Do the window math. Scott's lifecycle is a bell curve: a story breaks, interest climbs while reporters hunt for sources and for the why behind the what, interest peaks, then it falls away. Your entry point is the climb, when follow up coverage is being assembled. Score the window with references/window_and_fit_scoring.md or run bin/newsjack_score.py:
  1. Score fit. Rate the brand honestly on the scoring sheet:
  1. Run the taste gate. Hard stops, no score fixes these:
  1. Pick the format and draft to it. Use references/pitch_and_post_templates.md.
  1. Second pair of eyes, then ship or kill. Someone who did not draft it checks the copy against the verification notes, fact by fact. Names, numbers, dates, and quotes must match the primary source exactly. Then publish inside the window, log the time, the angle, and the target list, and watch replies for the first hour. If the underlying story shifts or your fact turns out wrong, correct it in the same channel, at the same prominence, fast. Do not quietly delete and hope.
  1. Post mortem within a day. Record: window at entry, verdict, what ran, coverage or engagement, any backlash, and what you would gate differently. File sit out decisions too. A log of good passes is what makes the next call faster and calmer.

Output Contract

Operating Rules

  1. Verification outranks speed in every case. Being first with a wrong fact costs more than being second with a right one, every time.
  2. Verify the source and the content separately. A real account can share a false claim and a new account can share a true one. Ask the Verification Handbook question of every source: how do you know that?
  3. Quantity is not corroboration. Fifty reposts of one report are still one report. Independent means a second newsroom or witness did its own work.
  4. Do not mistake a trending tag for a topic. Read why it is trending, in original posts, before drafting anything that touches it.
  5. Keep pitches short and personal. Name the journalist's beat and recent coverage only when you have actually read it. Never blast the same reactive pitch to a general list.
  6. Pre build the system on a quiet day: monitoring alerts on your beats, a list of named experts with phone numbers and pre cleared topics, template shells, and one person with authority to approve within 30 minutes. Speed comes from preparation, not from skipping gates.
  7. Planned news is still newsjacking work. Earnings, rulings, awareness days, and report launches reward the same gates, with the advantage that verification and drafting can happen before the window opens. Never embargo break or pre publish facts that are not yet public and confirmed.
  8. If two gates disagree, the stricter verdict wins. Strong fit does not cure weak verification. A wide open window does not cure a taste failure.
  9. Log every call, including passes, in the post mortem file. Brands that only remember their hits repeat their misses.

Versions

v1.0.02026-10-27 · 0 installs · Ed25519-signed./install.sh newsjacking-playbook 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.