What is a Claude Code Skill?

A Claude Code Skill is a specialized capability that enhances Claude's behavior, providing domain-specific guidance and implementation patterns for tasks like incident management.

Can I customize the incident severity definitions?

Absolutely. You can configure your own severity definitions, escalation paths, and requirements by updating the ops.local.md file.

How does the skill handle different incident severities?

The skill uses P1 (Critical), P2 (Major), and P3 (Minor) classifications to determine response times, management escalation, and mandatory post-mortem requirements.

What is the Five Whys methodology used in this skill?

It is a root cause analysis technique that asks 'Why?' five times to move past the immediate event to the underlying systemic or organizational gap.

Does this skill support blameless post-mortems?

Yes, the skill enforces 'Universal Rules' that frame all questions around system and process failures rather than individual mistakes.

Incident Intelligence & RCA

Name: Incident Intelligence & RCA
Author: panaversity

bypanaversity

•

分析与监控

Automates incident reporting, root cause analysis, and post-mortem documentation to drive systemic improvements in system reliability.

This skill streamlines the entire incident management lifecycle, providing standardized frameworks for post-mortems, root cause analysis (RCA), and corrective action tracking. It enforces industry best practices such as blameless reviews, the 'Five Whys' methodology, and severity-based escalation paths. By integrating with ITSM logs and team communication tools, it helps engineering and operations teams move beyond proximate causes to identify systemic gaps, ensuring every outage results in verifiable, time-bound improvements that prevent recurrence.

主要功能

01Blame-free incident review templates and lessons learned briefs

02Guided Five Whys root cause analysis drill

0311 GitHub stars

04Standardized Post-Mortem and Incident Log generation

05Severity-based classification and escalation workflows (P1-P3)

06Verifiable corrective action tracking with ownership and deadlines

使用场景

01Conducting a structured post-mortem after a critical P1 service outage

02Maintaining a centralized tracker for long-term corrective actions across multiple incidents

03Drilling down into systemic process failures using the Five Whys methodology

主要功能

01Blame-free incident review templates and lessons learned briefs

02Guided Five Whys root cause analysis drill

0311 GitHub stars

04Standardized Post-Mortem and Incident Log generation

05Severity-based classification and escalation workflows (P1-P3)

06Verifiable corrective action tracking with ownership and deadlines

使用场景

01Conducting a structured post-mortem after a critical P1 service outage

02Maintaining a centralized tracker for long-term corrective actions across multiple incidents

03Drilling down into systemic process failures using the Five Whys methodology