skills.rest
iceflower
iceflowerCOMMUNITY
Explore all skills by this author →
GitHub

incident-response

Generate incident response runbooks with severity definitions and mitigation steps.

1|Updated Mar 17, 2026
Search Tags:#runbook#on-call#postmortem#mitigation#severity#incident#response
One-click install
npx skills add https://github.com/iceflower/agent-skills --skill incident-response-iceflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/iceflower/agent-skills/tree/main/incident-response
Command: npx skills add https://github.com/iceflower/agent-skills --skill incident-response-iceflower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Incident response workflow including severity classification, communication protocols, triage, mitigation strategies, runbook authoring, postmortem process, and on-call best practices. Covers MTTD, MTTA, MTTR metrics and SLO/SLI/SLA relationships. Use when handling production incidents, writing runbooks, or establishing incident response procedures.

Core Features & Use Cases

  • Severity classification and incident lifecycle templates
  • Runbook authoring and postmortem templates
  • On-call coordination, communication templates, and metrics dashboards
  • Alignment with blameless postmortems and SLOs

Quick Start

Describe a production incident scenario to generate a complete runbook, escalation plan, and post-incident processes.

Frequently Asked Questions about incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an incident response runbook for production outages?▼

Generate a structured incident response runbook by describing a production outage scenario, which produces severity definitions, mitigation steps, communication templates, and post-incident postmortem checklists.

What is the best way to classify incident severity during on-call rotations?▼

Classify incident severity by evaluating impact against SLOs and SLIs, enabling on-call teams to trigger appropriate triage, mitigation, and escalation protocols during production outages.

How do I conduct a blameless postmortem after resolving an incident?▼

Conduct a blameless postmortem using generated templates to document MTTD, MTTA, and MTTR metrics, analyze root causes without assigning blame, and establish on-call best practices for future prevention.

Can I use this to generate communication templates for on-call coordination?▼

Yes, you can generate on-call coordination and communication templates that align with your incident lifecycle, ensuring structured information delivery during triage, mitigation, and post-incident reviews.

Does incident response planning work with existing SLO and SLA metrics?▼

Incident response planning aligns directly with SLO, SLI, and SLA metrics to define severity, measure MTTD and MTTR, and ensure mitigation strategies meet reliability objectives during production operations.

Related Skills

Explore More Software Engineering Skills→
omeraltnomeraltn

agency-incident-response-commander

Coordinate production incident response and post-mortem facilitation for distributed services.

Community
Advanced
daemon-blockint-techdaemon-blockint-tech
7

incident-management-engineer

Define severity models, escalation policies, on-call rotations, and postmortem workflows.

Community
Advanced
chicongstchicongst
2

sre-engineering

Coordinate production incident response and post-mortem analysis.

Community
Advanced
Prathmesh2000Prathmesh2000
1

incident-manager

Structure production-incident response with playbooks, severity levels, and postmortem templates.

Community
Advanced