agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/crisis-communications/SKILL.md

crisis-communications

Skill1 starsChanged 25 days agoMITView on GitHub

Plans clear, timely crisis communications when an incident threatens customers, staff, reputation or regulatory standing.

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:

    Use during or right after a serious incident such as a data breach, outage, product fault, safety event or public complaint, or to prepare …

    line 9

≈ “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 Communications

When to use it

Use during or right after a serious incident such as a data breach, outage, product fault, safety event or public complaint, or to prepare a crisis plan in advance.

What Claude needs

  • client-context.md for business background
  • Confirmed facts about the incident and what is still unknown
  • Affected groups
  • Actions already taken
  • Legal, regulatory and contractual notification duties
  • Spokespeople and the approval chain

Method

  1. Separate confirmed facts, unconfirmed reports and unknowns, and keep this log updated as facts change.
  2. Identify affected audiences such as customers, staff, regulators, partners, media and investors, and their main concerns.
  3. Set the order and timing of communications, with mandatory notifications first.
  4. Draft a holding statement and audience messages covering what happened, what it means, what is being done and when the next update will come.
  5. Name one spokesperson, the approval route and a question-and-answer sheet.
  6. Plan follow-up updates and a post-incident review of how communications went.

Output format

Provide a crisis communication plan with fact log, audience map, timeline, holding statement, audience-specific messages, Q&A sheet and approval chain.

Quality checks

  • Makes no speculative or unconfirmed claims
  • Meets every notification deadline that applies
  • Flags statements that need legal review before release

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.