What incident severity levels are supported?

The skill supports four levels: P1 (Service down/15m response), P2 (Major degradation/30m), P3 (Minor impact/4h), and P4 (No impact/Next business day).

Can I use this for team communication?

Absolutely. It includes a structured communication template to report incident impact, current status, ETA for resolution, and update channels.

How does the escalation path work?

It provides a tiered timeline starting with the On-Call Engineer, moving to the Team Lead at 30 minutes, Engineering Manager at 1 hour, and VP of Engineering at 2 hours.

Does this skill include automated troubleshooting steps?

Yes, it includes specific runbooks for common issues like High CPU (using top -c), Out of Disk space (df -h), and Database slowness (SHOW PROCESSLIST).

Incident Response Infrastructure

Name: Incident Response Infrastructure
Author: timequity

bytimequity

Deployment & DevOps

Manages system incidents, executes runbooks, and coordinates on-call procedures to maintain service reliability and minimize downtime.

About

The Incident Response skill provides a comprehensive framework for managing production issues within the Claude Code environment. It equips engineering teams with standardized severity levels, automated communication templates, and structured escalation paths to handle everything from minor degradations to critical P1 outages. By offering predefined runbooks for common infrastructure failures like high CPU usage or database latency, this skill ensures that on-call engineers can move quickly from alert acknowledgement to root cause resolution and postmortem documentation.

Key Features

Standardized P1-P4 severity levels and response SLAs
Automated status communication templates for stakeholders
0 GitHub stars
Comprehensive on-call checklists for consistent incident handling
Predefined runbooks for CPU, disk, and database troubleshooting
Clear time-based escalation paths for engineering leadership

Use Cases

Coordinating communication between on-call engineers and management during incidents
Executing rapid troubleshooting steps for common infrastructure bottlenecks
Standardizing the response workflow for production system outages

About

Key Features

Standardized P1-P4 severity levels and response SLAs
Automated status communication templates for stakeholders
0 GitHub stars
Comprehensive on-call checklists for consistent incident handling
Predefined runbooks for CPU, disk, and database troubleshooting
Clear time-based escalation paths for engineering leadership

Use Cases

Coordinating communication between on-call engineers and management during incidents
Executing rapid troubleshooting steps for common infrastructure bottlenecks
Standardizing the response workflow for production system outages