Judge Whether To Comment On A Live Story

Reacting to a live story is one of the few ways to reach far beyond your usual audience, and it is also how organisations acquire the screenshot that follows them for years. The failure is rarely speed - it is standing. An opinion on something you have no involvement in reads as opportunism, and the replies will say so. The decision is whether you can add something from direct experience, and whether a commercial voice belongs in this story at all.

The skill file

---
name: reactive-commentary-decision
description: Use when something has just happened in your industry and someone is asking whether the brand should post about it today.
---

# Judge Whether To Comment On A Live Story

Reacting to a live story is one of the few ways to reach far beyond your usual audience, and it is also how organisations acquire the screenshot that follows them for years. The failure is rarely speed - it is standing. An opinion on something you have no involvement in reads as opportunism, and the replies will say so. The decision is whether you can add something from direct experience, and whether a commercial voice belongs in this story at all.

## What you need first

- the story from a primary source, not a summary of a summary
- an honest answer to whether your organisation has direct experience of the thing
- an approval path agreed in advance, with someone who can say yes within hours

## Method

1. Verify the story from the primary source before anything else. Early industry reports are wrong often enough that reacting to one is more damaging than missing the window entirely.
2. Apply the standing test: can you say something from your own data, a decision you made, or a thing you had to fix? If the honest answer is a general opinion, do not post, because a general opinion is what everyone else is already posting.
3. Rule out the categories where commercial commentary does not belong: deaths, layoffs at another company, live legal matters, an individual person's misfortune. There is no angle that makes these safe.
4. Write the angle as one sentence and test whether it survives the story developing the other way. If the post only works when your prediction turns out right, it is a bet rather than commentary.
5. Set a hard ship-by time. Most of the reach sits in the first day, and a considered take on day four competes with the analysis pieces instead of the reaction.
6. Use the pre-agreed approval path rather than assembling one now. The usual failure here is not a bad decision but a good post held in review until the window shut.
7. Log what you posted and revisit it once the story resolves, because reactive posts age in public and a wrong one stays searchable under your name.

## What this produces

A written go or no-go decision naming the angle, the ship-by time, and the subjects excluded before anyone drafts anything.

## Where this goes wrong

- attaching a product mention to a news reaction, which turns a neutral post into a visible attempt to profit from the story
- posting while the facts are still moving and then deleting, which is itself the screenshot
- treating every industry story as an opportunity, so the account becomes a reaction feed with no position of its own

---

From the QuQi skill library - https://www.quqi.io/skills/reactive-commentary-decision

What you need first

• the story from a primary source, not a summary of a summary
• an honest answer to whether your organisation has direct experience of the thing
• an approval path agreed in advance, with someone who can say yes within hours

Method

1. 01 Verify the story from the primary source before anything else. Early industry reports are wrong often enough that reacting to one is more damaging than missing the window entirely.
2. 02 Apply the standing test: can you say something from your own data, a decision you made, or a thing you had to fix? If the honest answer is a general opinion, do not post, because a general opinion is what everyone else is already posting.
3. 03 Rule out the categories where commercial commentary does not belong: deaths, layoffs at another company, live legal matters, an individual person's misfortune. There is no angle that makes these safe.
4. 04 Write the angle as one sentence and test whether it survives the story developing the other way. If the post only works when your prediction turns out right, it is a bet rather than commentary.
5. 05 Set a hard ship-by time. Most of the reach sits in the first day, and a considered take on day four competes with the analysis pieces instead of the reaction.
6. 06 Use the pre-agreed approval path rather than assembling one now. The usual failure here is not a bad decision but a good post held in review until the window shut.
7. 07 Log what you posted and revisit it once the story resolves, because reactive posts age in public and a wrong one stays searchable under your name.

What this produces

A written go or no-go decision naming the angle, the ship-by time, and the subjects excluded before anyone drafts anything.

Where this goes wrong

• attaching a product mention to a news reaction, which turns a neutral post into a visible attempt to profit from the story
• posting while the facts are still moving and then deleting, which is itself the screenshot
• treating every industry story as an opportunity, so the account becomes a reaction feed with no position of its own

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Questions about this skill

More in Social & distribution