incident-responder

Structure incident response with severity classification, communication protocols, and recovery procedures.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill incident-responder-amidvoshakul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-responder
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/incident-responder
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill incident-responder-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the chaos and high-pressure environment of system outages by providing a structured, SRE-aligned framework for rapid stabilization, communication, and post-incident learning.

Core Features & Use Cases

  • Incident Command Structure: Establishes clear roles and communication protocols to prevent decision paralysis during critical outages.
  • Observability-Driven Troubleshooting: Guides the user through systematic investigation techniques using metrics, logs, and distributed tracing.
  • Blameless Post-Mortem: Facilitates a culture of continuous improvement by focusing on systemic root causes rather than human error.

Quick Start

Use the incident-responder skill to initiate a P1 incident response protocol for the current service outage.

Frequently Asked Questions about incident-responder

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

FAQPage Schema
What is an SRE incident response framework for managing system outages?

An SRE incident response framework establishes structured incident command protocols, severity classification, and communication strategies to manage system outages. It guides technical teams through rapid stabilization, observability-driven investigation, and root cause analysis.

How do I conduct observability-driven troubleshooting during a critical outage?

Observability-driven troubleshooting systematically investigates critical outages using metrics, logs, and distributed tracing. It guides responders through structured incident command protocols to prevent decision paralysis and achieve rapid stabilization.

How do I write a blameless post-mortem after resolving an incident?

Writing a blameless post-mortem involves documenting systemic root causes rather than focusing on human error. It facilitates continuous improvement by analyzing the incident timeline and recovery procedures without assigning individual blame.

Can this incident management skill handle P1 critical service outages?

Yes, the incident management skill initiates P1 incident response protocols to handle critical service outages. It establishes clear roles and communication protocols to execute rapid stabilization and structured recovery procedures.

What is the best way to classify incident severity during a service disruption?

The best way to classify incident severity is using an SRE-aligned framework that categorizes service disruptions based on impact. This classification dictates the required communication strategies, incident command structure, and recovery procedures.

Why does my incident response process suffer from decision paralysis?

Incident response processes suffer from decision paralysis when they lack a structured incident command structure. Establishing clear roles and communication protocols prevents this paralysis and enables rapid stabilization during critical outages.