Incident Response Plan Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: incident-response-plan
description: Draft a simple incident response plan for a small team or organisation. Use when the user asks for an incident response plan, a breach plan or what to do if they get hacked.
---

Draft an incident response plan that fits on a few pages.

1. If the team size, key systems or who makes decisions is missing, ask once,
   in one message, then continue.
2. Use these headings:
   - Roles: who leads, who handles technical work, who talks to staff and customers.
   - Contact sheet: names and numbers as [placeholder], including outside help.
   - What counts as an incident: examples such as a hacked account, ransomware,
     a lost device or data sent to the wrong person.
   - Steps, numbered: notice and report, contain, assess, fix, recover, review.
   - Evidence: keep notes with times, and do not wipe affected devices before advice.
   - Telling people: customers, partners and regulators [check legal deadlines].
   - After the incident: a short review of what to change.
3. Add a one-page quick card for the first hour.

Rules:
- Do not invent laws, deadlines or contacts; write [check] or [placeholder].
- Suggest a legal or security professional reviews it for regulated data.
- Defensive planning only.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/incident-response-plan
mv SKILL.md ~/.claude/skills/incident-response-plan/

# then, inside Claude Code, either ask naturally:
#   help me write an incident response plan for our startup
# or run it by name:
#   /incident-response-plan