agentleFS
teodstrteodstr/boardroom/skills/crisis-communication/SKILL.md

crisis-communication

Skill0 starsChanged 3 days agoMITView on GitHub

Handle a corporate crisis or reputational issue with Situational Crisis Communication Theory (SCCT): establish the facts, assess how responsible the public will hold the organization, choose the response strategy, and draft the holding statement, key messages and stakeholder plan for the first hours and days. Use for product recalls, accidents, scandals, data breaches, bad buzz, crisis simulations and PR case studies. Triggers: "crisis communication", "PR crisis", "press statement", "product recall", "bad buzz", "communication de crise", "gestion de crise", "communiqué de presse", "comunicación de crisis", "gestión de crisis", "comunicado de prensa".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never mix deny with diminish or rebuild: it destroys credibility.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Crisis communication (SCCT)

Protect people first, then the organization's reputation, with a response that matches how much responsibility the public attributes to the organization.

When to use

  • A crisis is happening or being simulated: accident, product harm or recall, misconduct, data breach, viral criticism.
  • Preparing a crisis plan, or analyzing how a company handled a crisis.

Inputs

  1. What happened, when, where, and who is affected. What is confirmed and what is not.
  2. The organization's history of similar crises and its reputation before the crisis.
  3. The stakeholders involved and any legal or regulatory obligations (notification deadlines, recalls).

Method

  1. Establish the facts. Separate confirmed facts from unconfirmed reports. Never speculate in public.
  2. Protect people first. The first messages give instructing information (what people should do to stay safe, for example stop using the product) and adjusting information (concern for those affected, what is being done). Reputation comes after.
  3. Identify the crisis type and its level of responsibility:
    • Victim cluster (natural disaster, rumor, product tampering, workplace violence): weak attribution.
    • Accidental cluster (technical-error accident or product harm, challenges from stakeholders): minimal attribution.
    • Preventable cluster (human-error accident or product harm, organizational misdeed): strong attribution.
  4. Adjust for intensifiers. A history of similar crises, or a poor reputation before the crisis, makes the public treat the crisis one level more severely.
  5. Choose the response strategy:

    • Deny (attack the accuser, denial, scapegoating): only when the accusation is false (rumor, misinformation). Blaming others usually backfires.
    • Diminish (excuse, justification): for accidental crises without intensifiers.
    • Rebuild (compensation, apology): for preventable crises, and for accidental crises with intensifiers.
    • Bolster (reminding of past good works, praising stakeholders, or showing the organization is also a victim in the victim cluster): only as a complement to the other strategies.

    Never mix deny with diminish or rebuild: it destroys credibility.

  6. Map the stakeholders: victims and customers, employees, authorities, media, investors, partners, online communities. For each one: what they need to know, the channel, the spokesperson, the timing.
  7. Draft the messages:
    • A holding statement for the first hour: what we know, what we are doing, concern for those affected, when the next update will come.
    • Three key messages at most, repeated consistently.
    • Answers to the hardest questions.
  8. Plan the timeline (first hour, first 24 hours, first week) and the monitoring (media coverage, online sentiment, call volumes).
  9. After the crisis: draw the lessons and show proof of the corrective actions taken.

Ethical rule: never recommend lying, denying confirmed facts, or withholding information that people need for their safety or that the law requires. Recommend involving legal counsel before admitting liability.

Output

### Situation
| Confirmed | Unconfirmed |
|---|---|

### Crisis type and responsibility
<Cluster, intensifiers, resulting level of responsibility.>

### Recommended strategy
<Strategy and why.>

### Holding statement (draft)
…

### Key messages
1. …

### Stakeholder plan
| Stakeholder | What they need | Channel | Spokesperson | When |
|---|---|---|---|---|

### Timeline
| When | Action | Owner |
|---|---|---|

### Tough questions
| Question | Answer |
|---|---|

Quality bar

  • People's safety comes before reputation in the first messages.
  • The response strategy matches the crisis type and the intensifiers.
  • Statements contain only confirmed facts, show empathy and announce the next update.
  • Messages are consistent across stakeholders and channels.
  • Nothing in the plan relies on deception.
  • Written in the user's language, with the standard terms below.

Terminology

EnglishFrançaisEspañol
Crisis communicationCommunication de criseComunicación de crisis
Holding statementDéclaration d'attenteComunicado inicial
SpokespersonPorte-parolePortavoz
Key messagesMessages clésMensajes clave
StakeholdersParties prenantesGrupos de interés
Product recallRappel de produitRetirada de producto

Sources

  • Coombs, W. T. (2007). Protecting organization reputations during a crisis: The development and application of situational crisis communication theory. Corporate Reputation Review, 10(3), 163–176.
  • Benoit, W. L. (1995). Accounts, Excuses, and Apologies: A Theory of Image Restoration Strategies. State University of New York Press.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.