About

Imported from nickcrew/claude-cortex (skills/incident-response/SKILL.md). Install upstream with npx skills add nickcrew/claude-cortex --skill incident-response. Copyright stays with the author.

Incident Response

Name: incident-response
Author: nickcrew

Structured incident management from detection through postmortem, with resilience patterns for preventing and containing cascading failures.

When to Use

Production incident in progress (outage, degradation, data loss)
Designing circuit breakers, bulkheads, or fallback strategies
Conducting or planning chaos engineering exercises
Writing or reviewing postmortem documents
Establishing on-call procedures and escalation paths

Avoid when:

The issue is a development-time bug with no production impact
Designing general system architecture (use system-design instead)

Quick Reference

Topic	Load reference
Triage Framework	`skills/incident-response/references/triage-framework.md`
Postmortem Patterns	`skills/incident-response/references/postmortem-patterns.md`

Incident Response Workflow

Phase 1: Detect

Alert fires or user report received
Confirm the issue is real (not a false positive)
Identify affected services and user impact scope

Phase 2: Triage

Classify severity (P0-P3)
Assign incident commander
Open communication channel (war room, Slack channel)
Begin status page updates

Phase 3: Contain

Stop the bleeding: rollback, feature flag, traffic shift
Prevent cascade: circuit breakers, load shedding, bulkhead isolation
Communicate: stakeholder updates every 15 minutes for P0/P1

Phase 4: Resolve

Implement fix (minimal viable fix first)
Validate in staging if time permits
Deploy with monitoring and rollback plan ready
Confirm recovery with metrics returning to baseline

Phase 5: Postmortem

Document timeline within 48 hours
Conduct blameless review with all participants
Identify root cause and contributing factors
Assign action items with owners and deadlines
Update runbooks and alerting based on lessons learned

Severity Framework

Level	Impact	Response Time	Examples
P0	Complete outage, data loss, security breach	Immediate (< 5 min)	Service down, data corruption, credential leak
P1	Major feature broken, significant user impact	< 30 min	Payment processing failed, auth broken for region
P2	Degraded performance, partial feature loss	< 4 hours	Elevated latency, non-critical feature unavailable
P3	Minor issue, workaround available	Next business day	UI glitch, slow report generation, cosmetic error

Output

Incident timeline and severity classification
Containment actions taken
Postmortem document with action items
Updated runbooks and alerting rules

Common Mistakes

Skipping severity classification and treating everything as P0
Making changes without a rollback plan
Forgetting to communicate status to stakeholders
Writing postmortems that assign blame instead of identifying systemic issues
Not following up on postmortem action items

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/nickcrew-claude-cortex-incident-response/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

nickcrew-claude-cortex-incident-response.ocm.jsonjson

{
  "ocm": "1",
  "id": "nickcrew-claude-cortex-incident-response",
  "kind": "skill",
  "name": "incident-response",
  "description": "Incident triage, cascade prevention, and postmortem methodology. Use when handling production incidents, designing resilience patterns, or conducting chaos engineering exercises.",
  "publisher": "nickcrew",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "incident-response",
      "outage",
      "postmortem",
      "triage",
      "incident",
      "response",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Incident triage, cascade prevention, and postmortem methodology. Use when handling production incidents, designing resilience patterns, or conducting chaos engineering exercises."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/nickcrew/claude-cortex",
      "path": "skills/incident-response/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/nickcrew/claude-cortex/blob/HEAD/skills/incident-response/SKILL.md",
      "key": "nickcrew/claude-cortex/skills/incident-response/SKILL.md"
    }
  },
  "instructions": "# Incident Response\n\nStructured incident management from detection through postmortem, with resilience patterns for preventing and containing cascading failures.\n\n## When to Use\n\n- Production incident in progress (outage, degradation, data loss)\n- Designing circuit breakers, bulkheads, or fallback strategies\n- Conducting or planning chaos engineering exercises\n- Writing or reviewing postmortem documents\n- Establishing on-call procedures and escalation paths\n\nAvoid when:\n- The issue is a development-time bug with no production impact\n- Designing general system architecture (use system-design in",
  "cost": {
    "context_tokens": 739
  }
}

Fetch it by URL: GET /api/v1/registry/nickcrew-claude-cortex-incident-response/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.