incident-response-sre

Name: incident-response-sre
Availability: InStock
Author: Sir-chawakorn

Structure incident response and blameless postmortems for software engineering teams.

9|3|Updated Jun 13, 2026

Search Tags:#observability #reliability #incident response #on-call #postmortem #sre

Ready to run

npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill incident-response-sre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response-sre
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/incident-response-sre
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill incident-response-sre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, blameless framework for managing high-pressure technical incidents, ensuring that mitigation is prioritized over diagnosis and that postmortems lead to actionable system improvements.

Core Features & Use Cases

Severity Triage: Standardized P0-P3 classification to determine impact and urgency.
Signal Correlation: A systematic approach to linking metrics, logs, and traces to identify root causes without getting lost in noise.
Blameless Postmortems: A template for documenting incidents that focuses on system guardrails rather than human error.
Use Case: Use this during an active service outage to guide your team through stabilization, communication, and the subsequent post-incident review process.

Quick Start

Initiate the incident response protocol by providing the current system symptoms and the observed impact to begin the triage and mitigation process.

Frequently Asked Questions about incident-response-sre

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

FAQPage Schema

How do I structure incident response during an active service outage?▼

Incident response during an active service outage is structured by prioritizing mitigation-first stabilization over root cause diagnosis, applying standardized P0-P3 severity triage to determine impact, and systematically correlating observability signals across metrics, logs, and traces.

What is a blameless postmortem in SRE and how does it work?▼

A blameless postmortem in SRE is a post-incident documentation process that focuses on identifying system guardrails and failures rather than attributing human error, resulting in concrete, owned action items that improve overall system reliability.

How do I triage on-call alerts using observability signal correlation?▼

On-call triage using observability signal correlation works by systematically linking metrics, logs, and traces to identify root causes without getting lost in noise, applying standardized P0-P3 severity classification to determine urgency and impact during the mitigation process.

What's the best way to classify incident severity for software engineering teams?▼

The best way to classify incident severity for software engineering teams is using a standardized P0-P3 classification system, which determines impact and urgency to guide the structured incident response workflow and prioritize mitigation efforts effectively.

Can I use this incident response framework for post-incident documentation workflows?▼

Yes, you can use this incident response framework for post-incident documentation workflows, as it provides a blameless postmortem template that focuses on system guardrails and generates concrete, owned action items for actionable system improvements.

When should I not use a mitigation-first approach during incident response?▼

You should not abandon a mitigation-first approach during incident response once the active service outage is stabilized, as the framework then transitions to signal correlation and blameless postmortem analysis to create concrete, owned action items for system improvements.