I
incident-communication-playbook
About incident-communication-playbook
incident-communication-playbook is a skill for teams coordinating incident communications. It structures internal and customer updates, support responses, timelines, and review gates around verified facts and user impact.
Key features
- 01Classifies incident impact and scope
- 02Drafts internal and customer updates
- 03Creates support macros and follow-ups
- 04Separates facts, unknowns, and actions
- 05Sets timelines and approval gates
Use cases
- 01Coordinating communications during an incident
- 02Preparing a customer status update
- 03Giving support teams consistent response macros
- 04Routing privacy-sensitive incidents for review
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill incident-communication-playbookAfter installing, type/incident-communication-playbookin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/incident-communication-patterns.md
Details
From the project READMEIncident Communication Playbook
Use this skill to communicate incidents clearly, quickly, and proportionately.
Workflow
- Identify incident type, user impact, blast radius, uncertainty, legal/privacy risk, and channels.
- Read
references/incident-communication-patterns.md. - Draft internal coordination, customer-facing updates, support macros, and post-incident follow-up.
- Separate known facts, unknowns, actions, next update time, and user workaround.
- Produce a communication timeline and approval/risk gates.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not speculate beyond verified facts.
- Do not hide material user impact.
- Route privacy/security/legal-sensitive incidents through the required review path.
Output format
Incident type:
Impact:
Channels:
Timeline:
- <time> <audience> <message/update>
Customer update:
- <draft>
Support macro:
- <draft>
Post-incident follow-up:
- <items>
Comments
Markdown supported