Devops Incident Response

Use when the user had an outage and needs a postmortem, an on-call process, incident severity levels (SEV1-SEV4), incident commander roles, escalation policies, runbooks, PagerDuty or Opsgenie setup, or an incident timeline. Produces incident process docs, runbooks and blameless postmortems. Not for SLO and error budget design (use sre-sli-slo-management).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill devops-incident-response
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/incident-response ~/.claude/skills/devops-incident-response

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Incident Response

## Purpose
Establish a structured incident response framework with clear severity levels, defined roles, documented runbooks, and a blameless postmortem culture to minimize recovery time and prevent recurrence.

## Agent Protocol

### Trigger
"incident response", "on-call", "PagerDuty", "OpsGenie", "incident management", "postmortem", "runbook", "severity", "escalation", "SEV", "SEV1", "SEV2", "SEV3", "incident command", "IC role", "incident timeline", "blameless postmortem", "incident lifecycle", "incident detection", "incident mitigation", "MTTD", "MTTR".

### Input Context
- Current incident state (detected, ongoing, mitigated, resolved)
- Service affected and current impact (users down, degraded, partial)
- Severity level if already classified
- Team structure and on-call rotation
- Existing runbooks and their locations
- Communication channels (Slack, Teams, PagerDuty)
- Compliance requirements (SOC2, PCI, HIPAA postmortem timelines)

### Output Artifact
Incident response framework with severity matrix, lifecycle workflow, runbook template, on-call schedule, and postmortem process. For active incidents: structured timeline with IC assignments, action items, and communication updates.

### Response Format
Read the full skill on GitHub

Details

Skill name
devops-incident-response
Path
skills/devops/incident-response/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Devops Incident Response skill do?

Use when the user had an outage and needs a postmortem, an on-call process, incident severity levels (SEV1-SEV4), incident commander roles, escalation policies, runbooks, PagerDuty or Opsgenie setup, or an incident timeline. Produces incident process docs, runbooks and blameless postmortems. Not for SLO and error budget design (use sre-sli-slo-management).

How do I install the Devops Incident Response skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill devops-incident-response. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Devops Incident Response popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Devops Kubernetes Autoscaling

45

j4flmao/agent-skills

Use when the user asks about HPA, VPA, Cluster Autoscaler, Karpenter, KEDA to scale pods on queue length, custom or external metrics autoscaling, scaling behavior and flapping, or autoscaling cost. Produces combined HPA/VPA/node autoscaling configs. Not for KEDA scaler details (use cloud-native-event-driven-scaling) or data workloads (use devops-kubernetes-for-data).

DevOps & Cloud

Devops Gitops Advanced

45

j4flmao/agent-skills

Use when the user asks about Argo CD ApplicationSets and generators, multi-cluster GitOps, sync waves and hooks at scale, cluster bootstrapping with Cluster API or Crossplane, Argo CD Image Updater, or Sealed Secrets, External Secrets and SOPS in GitOps. Produces fleet-scale GitOps designs. Not for basic Argo CD setup (use argo-cd).

DevOps & Cloud

Devops Kubernetes for Data

45

j4flmao/agent-skills

Use when the user asks about Spark on Kubernetes, the Spark Operator, Airflow KubernetesExecutor, Kafka on Kubernetes with Strimzi, Volcano or Kueue batch scheduling, GPU scheduling, node pools or Karpenter for data jobs, or storage for data workloads. Produces data-platform configs on Kubernetes. Not for pipeline design (use data-etl-pipeline).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.