incident SKILL.md skillA
incident from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/incident@git:20261014.03c655ePins git:20261014.03c655e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/incident/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.03c655e, committed Oct 14, 2026
- First version recorded
- Oct 1, 2026
- Size
- 5,819 bytes
- Repository stars
- 9
- License
- MIT
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…
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 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@sha256:4f8b2aa31d8eb499The line at the top of this page pins the label git:20261014.03c655e, 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.
[](https://markdownregistry.com/a/art_ewncghbvel5qsggh)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 1, 2026 and Oct 14, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.03c655e latest | 2026-10-14 | 03c655e | 5,819 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 5,609 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 (5819 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 · 9 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ewncghbvel5qsggh GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/incident GET https://markdownregistry.com/api/v1/blob/4f8b2aa31d8eb499ad45b6545d2d90bd9cddc6f3d20a5bd0041dce41b40f660b
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit