Skip to content
Back to skills

Incident Response

ASecurity

Run an incident and learn from it: declare + classify severity, split IC/comms/ops roles, communicate on a cadence, mitigate before root-causing, and write a blameless postmortem with owned, dated action items.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill incident-response --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Incident Response?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Incident Response
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-incident-response/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-incident-response)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: incident-response
description: "Run an incident and learn from it: declare + classify severity, split IC/comms/ops roles, communicate on a cadence, mitigate before root-causing, and write a blameless postmortem with owned, dated action items."
---

# Incident Response

**Purpose:** respond fast, communicate clearly, learn permanently.

## Declare & classify
Lean toward declaring. Severity sets the response size.

## Roles (separate them)
- **IC** — coordinates, decides, does NOT debug.
- **Ops** — fixes.
- **Comms** — updates stakeholders on a cadence.

## Mitigate first
Rollback / failover / flag-off to stop bleeding **before** forensic root-cause.

## Blameless postmortem
Fix the **system** that let the human err. Timeline + contributing factors + **owned, dated** action items tracked to done.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…