skills.rest
Cure-Consulting-Group
Cure-Consulting-GroupOFFICIAL
Explore all skills by this author →
GitHub

incident-response

Classify production incidents by severity and guide runbooks, communication, and post-mortems.

1|1|Updated Mar 9, 2026
Search Tags:#post-mortem#incident response#runbook#on-call#production support#severity classification
One-click install
npx skills add https://github.com/Cure-Consulting-Group/ProductEngineeringSkills --skill incident-response-cure-consulting-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/Cure-Consulting-Group/ProductEngineeringSkills/tree/main/skills/incident-response
Command: npx skills add https://github.com/Cure-Consulting-Group/ProductEngineeringSkills --skill incident-response-cure-consulting-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework to manage production incidents effectively, from initial detection and classification to resolution and post-mortem analysis, ensuring minimal disruption and rapid recovery.

Core Features & Use Cases

  • Incident Classification: Quickly categorize incidents by severity (SEV1-SEV4) based on impact and user affected.
  • Runbook Guidance: Step-by-step instructions for triage, mitigation, and resolution tailored for various platforms (Firebase, GCP, Mobile, Web).
  • Communication Templates: Pre-written messages for internal stakeholders and external customers during and after an incident.
  • Post-Mortem Framework: A structured template to conduct blameless post-mortems, identify root causes, and define preventative action items.
  • Use Case: During a sudden spike in 5xx errors on your web application, use this Skill to classify the incident, follow the runbook to identify the cause (e.g., a recent deployment), mitigate the issue by rolling back, and then use the post-mortem template to document the event and create action items to prevent recurrence.

Quick Start

Use the incident-response skill to classify an incident with the following details: service is down, affecting 75% of users, and revenue is impacted.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I classify production incident severity for cloud-native applications?▼

Production incident severity is classified into SEV1-SEV4 levels based on user impact and revenue loss. This framework allows rapid categorization of cloud-native incidents to trigger appropriate escalation paths and response procedures.

What is the best way to structure a blameless post-mortem after a production outage?▼

A blameless post-mortem requires a structured template to identify root causes and define preventative action items. This approach ensures teams document the event objectively and create metrics to track resolution effectiveness.

How do I create runbook instructions for triaging web and mobile incidents?▼

Runbook instructions for triaging incidents should provide step-by-step mitigation and resolution paths tailored for specific platforms like Firebase, GCP, Mobile, and Web. This ensures standardized incident handling across different deployment environments.

Can I use standardized templates for external customer communication during an incident?▼

Standardized communication templates provide pre-written messages for both internal stakeholders and external customers during an incident. This ensures consistent updates throughout the incident response lifecycle without delaying resolution.

Does incident response work for cloud-native applications on GCP and Firebase?▼

Incident response frameworks support cloud-native applications, mobile platforms, and web services including GCP and Firebase. The structured runbooks and classification systems are tailored to handle various platform-specific deployment architectures.

Related Skills

Explore More Software Engineering Skills→
LeandroBenjaminLLeandroBenjaminL

infra-sre

Monitor services and configure alerts using Prometheus and Grafana.

Community
Advanced
neurofooneurofoo
106

postmortem

Facilitate blameless post-mortem incident analysis to identify root causes and define preventative action items.

Community
Intermediate
involvexinvolvex

database-migrations-migration-observability

Monitor database migrations with CDC pipelines, metrics, and alerts.

Community
Advanced
legioncodeinclegioncodeinc
72

status-page-stinger

Structure incident communication and reliability workflows for public status pages.

Official
Advanced