When something goes wrong with your software, you need a clear plan. This skill helps you run an incident response workflow from start to finish. It guides you through triage, communication, and writing a blameless postmortem.
You can use it when an alert comes in, when production is down, or when you need to share a status update. It works for any kind of incident, big or small. The skill sorts issues into severity levels from SEV1 to SEV4 so you know how fast to respond.
After the incident is resolved, the skill helps you write a clear postmortem document. This document shows what happened, what went wrong, and what actions to take next. The goal is to learn and improve, not to blame anyone.
Global
mkdir -p ~/.claude/skills/incident-responseProject
mkdir -p .claude/skills/incident-responseSource Repository
Appinsights Instrumentationmicrosoft/azure-skills
Learn how to add Azure Application Insights monitoring to your web app
Azure Kustomicrosoft/azure-skills
Run fast KQL queries on Azure Data Explorer for log and telemetry analysis
Caveman Statsjuliusbrussee/caveman
See real token usage and estimated savings directly from your session log
Azure Observabilitymicrosoft/azure-skills
Track Azure app errors, performance, and infrastructure with monitoring tools
Convex Performance Auditget-convex/agent-skills
Find and fix Convex performance problems with step-by-step diagnostic guidance
Google Agents Cli Observabilitygoogle/agents-cli
Set up tracing, logging, and analytics for your ADK agents easily
Golang Observabilitysamber/cc-skills-golang
Monitor your Go services with logs metrics traces and profiling
Golang Samber Slogsamber/cc-skills-golang
Compose, sample, and route Go logs to multiple backends with ease