# Coordinate Reliable Incident Response

Service incidents require fast decisions, clear ownership, and reliable communication. This skill structures triage, investigation, recovery, validation, and post-incident learning.

## Install

```bash
npx skillstore add sickn33/incident-responder
```

## Metadata

- Status: approved
- Slug: sickn33-incident-responder
- Skillstore revision: r2
- Version status: missing
- Tree hash: 060079899a7b31e66888c70695b589ce67353795952374e2a9c1dd46ec0c0d97
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/incident-responder
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-incident-responder
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-incident-responder/manifest

## Capabilities

- Classifies incident severity using user, business, system, and regulatory impact.
- Defines incident commander, communication lead, and technical lead responsibilities.
- Structures investigations across metrics, traces, logs, dependencies, capacity, databases, and networks.
- Plans stabilization, rollback, staged recovery, and service health validation.
- Drafts stakeholder updates, incident timelines, postmortems, and improvement actions.
- Applies SRE concepts including error budgets, burn rates, circuit breakers, and graceful degradation.

## Use Cases

- Lead an Active Outage: Create a prioritized response plan, assign roles, assess impact, and establish update intervals.
- Investigate Service Degradation: Correlate recent changes with metrics, traces, logs, dependencies, capacity, and user impact.
- Run a Post-Incident Review: Build a blameless timeline, analyze contributing factors, and define measurable prevention and detection improvements.

## Prompt Templates

### Classify an Incident

```
Classify this incident using user impact, business impact, affected systems, and external factors: [incident details]. State assumptions and missing information.
```

### Create a Response Plan

```
Build a first-30-minute response plan for [incident]. Assign roles, prioritize stabilization, define validation checks, and draft internal and customer updates.
```

### Guide an Observability Investigation

```
Analyze these symptoms and telemetry: [details]. Propose ranked hypotheses and checks across changes, metrics, traces, logs, dependencies, capacity, databases, and networks.
```

### Design Recovery and Follow-Up

```
Using this incident timeline and evidence: [details], propose a staged recovery plan, rollback criteria, validation gates, contributing factors, and measurable follow-up actions.
```

## Limitations

- The skill provides guidance and does not directly access monitoring, deployment, or incident management systems.
- Recommendations require validation against local runbooks, permissions, compliance rules, and production conditions.
- Severity targets and response timelines must be adapted to organizational policies.
- The referenced implementation playbook is not included in this package.

## Best Practices

- Prioritize service restoration while preserving evidence and rollback options.
- Use current telemetry to test ranked hypotheses and record every important decision.
- Communicate on a fixed schedule with detail appropriate for each audience.

## Anti Patterns

- Do not make high-risk production changes without ownership, validation, and rollback criteria.
- Do not delay stakeholder updates until the root cause is known.
- Do not treat a temporary symptom reduction as confirmed recovery.

## Security Audit

- Audited at: 2026-07-24T01:03:39.244\+00:00
- Summary: All three static findings are false positives caused by Markdown formatting and ordinary descriptions of SRE incident response. The skill contains guidance only, with no executable commands, system reconnaissance, or prompt injection evidence.

## Stats

- Views: 108
- Downloads: 11
- Favorites: 0
- Popularity score: 0