# Incident Response

> Triage and respond to production incidents

- **Type:** Skill
- **Install:** `agentstack add skill-stbenjam-skillsaw-incident-response`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [stbenjam](https://agentstack.voostack.com/s/stbenjam)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [stbenjam](https://github.com/stbenjam)
- **Source:** https://github.com/stbenjam/skillsaw/tree/main/tests/fixtures/apm/clean/.apm/skills/incident-response
- **Website:** https://skillsaw.org/

## Install

```sh
agentstack add skill-stbenjam-skillsaw-incident-response
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Incident Response

Guide the on-call engineer through incident triage, investigation,
and resolution for production issues.

## When to Use This Skill

Use when a PagerDuty alert fires or a user reports a production issue
that needs immediate investigation.

## Implementation Steps

### Step 1: Gather Context

Collect information about the incident:
- Alert source and timestamp
- Affected service and environment
- Error rate and latency changes from monitoring

### Step 2: Investigate

Run diagnostic commands:
```bash
kubectl get pods -n production | grep -v Running
kubectl logs -f deployment/$SERVICE -n production --since=10m
aws cloudwatch get-metric-statistics --namespace Custom --metric-name ErrorRate
```

### Step 3: Identify Root Cause

Correlate findings with recent changes:
```bash
git log --oneline --since="2 hours ago"
kubectl rollout history deployment/$SERVICE -n production
```

### Step 4: Mitigate

If a recent deployment is the cause, roll back:
```bash
kubectl rollout undo deployment/$SERVICE -n production
```

### Step 5: Document

Create an incident report with:
- Timeline of events
- Root cause analysis
- Resolution steps taken
- Action items to prevent recurrence

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [stbenjam](https://github.com/stbenjam)
- **Source:** [stbenjam/skillsaw](https://github.com/stbenjam/skillsaw)
- **License:** Apache-2.0
- **Homepage:** https://skillsaw.org/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-stbenjam-skillsaw-incident-response
- Seller: https://agentstack.voostack.com/s/stbenjam
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.