mcpField
C
crisis-playbooks

crisis-playbooks

github.com/gtmagentsMarketing & growth42864 installsUpdated 30w ago
Repository

About crisis-playbooks

A skill for preparing coordinated communications during service outages, security incidents, regulatory events, and other sensitive situations. It provides severity, escalation, message, channel, and recovery planning for communications teams.

Key features

  1. 01Incident severity and response SLAs
  2. 02Escalation contacts and channel sequence
  3. 03Customer, partner, and internal message kits
  4. 04Status, press, and social timelines
  5. 05Monitoring and post-incident review templates

Use cases

  1. 01Coordinating outage announcements
  2. 02Preparing responses to security incidents
  3. 03Managing negative press or social media escalation
  4. 04Aligning messaging for sensitive executive or HR news

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill crisis-playbooks

After installing, type/crisis-playbooksin Claude Code to confirm it loaded.

Details

From the project README

Crisis Communications Playbooks Skill

When to Use

  • Service outages, security incidents, compliance/regulatory events.
  • Negative press cycles or social media escalations.
  • Sensitive executive/HR news requiring coordinated messaging.

Framework

  1. Severity Matrix – classify incidents (P1-P4) with response SLAs and approvers.
  2. Escalation Tree – who to notify, in what order, via which channels.
  3. Message Kits – holding statements, customer/partner/internal scripts, social/status updates.
  4. Channel Sequence – timeline for status page, email, press, social, internal posts.
  5. Monitoring & Recovery – tracking sentiment, rumor control, follow-up updates.

Templates

  • Incident briefing doc (facts, unknowns, owners, deadlines).
  • Approval checklist for legal/security/executive signoff.
  • Post-incident report with RCA, comms metrics, and improvement actions.

Tips

  • Rehearse quarterly with tabletop exercises.
  • Keep localized versions for regulated markets.
  • Archive every incident’s comms artifacts for compliance and learning.

Comments

Markdown supported