mcpField
I
incident-response

incident-response

github.com/w95Cloud & DevOps28536 installsUpdated 35w ago
Repository

About incident-response

An incident-response skill for teams guiding incidents from detection through resolution and postmortem. It provides severity criteria, a response sequence, communication templates, and a blameless review format.

Key features

  1. 01Classifies incidents into four severity levels
  2. 02Guides triage, communication, mitigation, and resolution
  3. 03Provides status-update communication guidance
  4. 04Structures blameless postmortems with action items

Use cases

  1. 01Classifying the impact of a service outage
  2. 02Coordinating incident response and updates
  3. 03Planning mitigation and verifying a fix
  4. 04Recording causes and follow-up actions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/w95/awesome-claude-corporate-skills --skill incident-response

After installing, type/incident-responsein Claude Code to confirm it loaded.

Details

From the project README

Incident Response

Guide incident response from detection through resolution and postmortem.

Severity Classification

LevelCriteriaResponse Time
SEV1Service down, all users affectedImmediate, all-hands
SEV2Major feature degraded, many users affectedWithin 15 min
SEV3Minor feature issue, some users affectedWithin 1 hour
SEV4Cosmetic or low-impact issueNext business day

Response Framework

  1. Triage: Classify severity, identify scope, assign incident commander
  2. Communicate: Status page, internal updates, customer comms if needed
  3. Mitigate: Stop the bleeding first, root cause later
  4. Resolve: Implement fix, verify, confirm resolution
  5. Postmortem: Blameless review, 5 whys, action items

Communication Templates

Provide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.

Postmortem Format

Blameless. Focus on systems and processes. Include timeline, root cause analysis (5 whys), what went well, what went poorly, and action items with owners and due dates.

Comments

Markdown supported