incident-response

Guides systematic detection, triage, mitigation, resolution, and post-mortem analysis of production incidents.

90|10|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/korallis/Droidz --skill incident-response-korallis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/korallis/Droidz/tree/main/droidz_installer/payloads/droid_cli/default/skills/incident-response
Command: npx skills add https://github.com/korallis/Droidz --skill incident-response-korallis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to managing and resolving production incidents, minimizing downtime and preventing future occurrences.

Core Features & Use Cases

  • Triage and Severity Assessment: Quickly categorize incidents based on impact (P0-P4).
  • Mitigation and Resolution: Guides through steps like rollbacks, hotfixes, and verification.
  • Post-Mortem Analysis: Facilitates root cause analysis and action item creation.
  • Use Case: When a critical service goes down, this skill helps you systematically detect, triage, mitigate, resolve, and document the incident to restore service quickly and learn from the event.

Quick Start

Use the incident-response skill to manage a P1 production outage.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I manage a production outage systematically?

Systematic production incident response involves moving through detection, triage, mitigation, resolution, and post-mortem analysis to minimize downtime and prevent future occurrences.

How do I assess severity levels during incident triage?

Incident triage assesses severity levels from P0 to P4 to categorize incidents based on impact, ensuring appropriate resource allocation during a production outage.

What is the best way to write a post-mortem after resolving an incident?

Writing an incident post-mortem facilitates root cause analysis and creates action items to prevent recurrence of the production issue after mitigation and resolution steps are complete.

Can I use this for production support without any external dependencies?

Yes, incident response guidance operates without external dependencies, providing templates for runbooks and outage communication directly to manage production support workflows.

What steps are involved in incident mitigation and resolution?

Incident mitigation and resolution steps guide users through applying rollbacks, hotfixes, and verification processes to restore critical services quickly during an outage.