Individual skill
incident
Run a production incident and close it properly: a timeline built from evidence, impact and severity, the proven root cause, the mitigation actually applied, a blameless postmortem, follow-up actions with owners and dates, and the runbook that makes the next occurrence shorter. Use during an outage, after one, or when writing the runbook for a recurring failure. Triggers on: "incident", "outage", "sự cố", "postmortem", "RCA", "root cause", "production down", "障害", "障害報告", "hotfix", "runbook", "/atk:incident".
plugins/atk/skills/incident/SKILL.md
Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-skills Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- plugin Repository topic
- sdlc Repository topic
- team-workflow Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,819 bytesSKILL.mdcore · 5,819 bytesevals/trigger_evals.jsonasset · 1,699 bytes
Read excerpt
# Incident Response and Postmortem (`atk:incident`)
Keeps an incident legible while it is happening and honest after it ends. During the incident the
priority is mitigation and a timestamped log; the analysis waits. Afterwards the cause must be
proven, not plausible, and the actions must have owners and dates or they will not happen.
## Scope
Handles: structuring the live response, recording the timeline, classifying severity and impact,
proving root cause, writing the blameless postmortem, generating follow-up actions, and writing or
updating the runbook.
Does NOT handle: fixing the code, which is `atk:fix` once the service is stable and the timeline no
longer needs a responder's attention; deploying the hotfix (`atk:release`); or assigning blame,