What happens when an incident is declared?

Claude will gather initial details, assign a severity level, identify the response team, and begin a live incident record to track all mitigation actions.

Who is the primary user for this skill?

It is designed for Site Reliability Engineers (SREs), DevOps engineers, and on-call developers who need a structured framework during high-pressure outages.

Can it help with post-mortem documentation?

Yes, it automatically tracks the incident timeline and gathers response details to generate a standardized Post-Incident Review (PIR) report.

How does this skill determine incident severity?

It evaluates customer impact, revenue loss, and the availability of workarounds to classify issues from SEV1 (Critical) to SEV4 (Low) based on pre-defined SRE standards.

Incident Triage & Response Coordination

Name: Incident Triage & Response Coordination
Author: jmagly

byjmagly

•

Analytics & Monitoring

Coordinates rapid incident classification, severity assessment, and response workflows to minimize system downtime.

About

This skill acts as an AI Incident Commander within Claude, providing a structured framework for managing production outages and system failures. It automates the critical first steps of incident response—from gathering initial impact data and assigning severity levels (SEV1-SEV4) to assembling responders and maintaining a real-time event timeline. By standardizing the triage process, it ensures consistent communication, faster mitigation, and detailed documentation for post-incident analysis.

Key Features

Internal and external communication management
Post-incident review (PIR) preparation and root cause analysis
67 GitHub stars
Standardized incident record and timeline generation
Automated SEV1-SEV4 severity classification logic
Response team mobilization and role assignment

Use Cases

Generating comprehensive incident reports for stakeholders and post-mortems
Tracking real-time response actions during a high-pressure production outage
Determining the business impact and severity level of a new system failure

About

Key Features

Internal and external communication management
Post-incident review (PIR) preparation and root cause analysis
67 GitHub stars
Standardized incident record and timeline generation
Automated SEV1-SEV4 severity classification logic
Response team mobilization and role assignment

Use Cases

Generating comprehensive incident reports for stakeholders and post-mortems
Tracking real-time response actions during a high-pressure production outage
Determining the business impact and severity level of a new system failure