WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Incident (WHAT)
Use for unplanned events that disrupt or degrade production systems, live users, or critical operations.
## Default guardrails
1. Apply **`output-handshake`** before final output.
2. Capture immediate mitigation separately from root cause and follow-up actions.
3. Use **`meeting-minutes`** if a validation or post-incident meeting needs minutes.
4. Create/link follow-up bugs or tasks only after approval.
## References
- `references/default-template.md`
- `references/example-payment-outage.md` — example incident with full timeline, RCA, and action items
- `bug`
- `meeting-minutes`
The line at the top of this page pins the label git:20260831.856ee57, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ai6gvb2oxr6q6ipi
GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/incident
GET https://markdownregistry.com/api/v1/blob/e275ca28ca5e07c15dfccd7d99d61b3f6a76474d710318597971e7d25cd30256
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/adr/SKILL.md · WHAT — Create and maintain Architecture Decision Records (ADRs) per the process. Covers when
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/brag-slim/SKILL.md · Turn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/brag/SKILL.md · Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone…
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/bug/SKILL.md · WHAT - Draft and review bugs using the Bug Template; classifies whether an issue should be
jikig-ai/soleur · plugins/soleur/skills/incident/SKILL.md · This skill should be used when scaffolding a redaction-gated post-incident report (PIR) after a production incident.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.opencode/skills/incident/SKILL.md · WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;
lamngockhuong/aiteamkit · plugins/atk/skills/incident/SKILL.md · Run a production incident and close it properly: a timeline built from evidence, impact and severity, the proven root…
greglas75/zuvo · skills/incident/SKILL.md · Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill…
umararshad4/honey-stack · skills/incident/SKILL.md · Respond to a production outage: assess severity, mitigate first (roll back/flip a flag/scale), investigate safely…
