incident-response Skill
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution. Published by anthropics in knowledge-work-plugins.
What is incident-response Skill?
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution. Published by anthropics in knowledge-work-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Writing
- Data analysis use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use incident-response Skill
- Use it for data analysis.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/knowledge-work-plugins
- Skill file: engineering/skills/incident-response/SKILL.md
What it does
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
Skill instructions
/incident-response If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Manage an incident from detection through postmortem. Usage /incident-response $ARGUMENTS Modes /incident-response new [description] Start a new incident /incident-response update [status] Post a status update /incident-response postmortem Generate postmortem from incident data If no mode is specified, ask what phase the incident is in. How It Works ┌─────────────────────────────────────────────────────────────────┐ │ INCIDENT RESPONSE │ ├─────────────────────────────────────────────────────────────────┤ │ Phase 1: TRIAGE │ │ ✓ Assess severity (SEV1-4) │ │ ✓ Identify affected systems and users │ │ ✓ Assign roles (IC, comms, responders) │ │ │ │ Phase 2: COMMUNICATE │ │ ✓ Draft internal status update │ │ ✓ Draft customer communication (if needed) │ │ ✓ Set up war room and cadence │ │ │ │ Phase 3: MITIGATE │ │ ✓ Document mitigation steps taken │ │ ✓ Track timeline of events
Explore related resources
Frequently asked questions
What is incident-response?
incident-response is a open-source AI agent skill with Copy skill directory. Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update.
Who is incident-response best for?
incident-response is best for reusing agent instructions, scripts, and references, data analysis workflows, writing workflows.
How do I install incident-response?
Install or run incident-response using Copy skill directory. Check incident-response for the latest setup command.
Is incident-response actively maintained?
incident-response may need a closer maintenance check before production use.
Auto-fetched from GitHub.
