incident skillA
incident is agent-read markdown (skill) from lamngockhuong/aiteamkit: 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", "/.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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, which is never an output of this skill. ## Roles An Incident Commander is named first, before anything else, and is not the person typing commands. SRE executes mitigation. Tech Lead owns the root cause analysis. PM owns stakeholder and client communication. See `shared/team-roles.md`. ## Invocation ```bash /atk:incident --live # Structure an ongoing incident: roles, timeline, comms …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/incident@git:20260922.c7615a5mdr add lamngockhuong/aiteamkit/incident@sha256:350b8432a43d69d5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_cslcwejonvvsjytz)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.c7615a5 latest | 2026-09-22 | c7615a5 | 5,483 B | A | view · diff |
| git:20260920.d282a91 | 2026-09-20 | d282a91 | 5,253 B | A | view · diff |
| git:20260918.73a33f4 | 2026-09-18 | 73a33f4 | 4,915 B | A | view · diff |
| git:20260918.dcc08e9 | 2026-09-18 | dcc08e9 | 4,811 B | A | view · diff |
| git:20260917.01d91de | 2026-09-17 | 01d91de | 4,803 B | A | view · diff |
| git:20260917.cf90c7f | 2026-09-17 | cf90c7f | 4,568 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5483 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lamngockhuong/aiteamkit · 5 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cslcwejonvvsjytz GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/incident GET https://markdownregistry.com/api/v1/blob/350b8432a43d69d5b2a79a2d97cb7ad9d9668441d44bae7fc2089569c23b1bb6
Your agent 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.
More from lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit