incident SKILL.md skillA
incident from umararshad4/honey-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add umararshad4/honey-stack/incident@git:20261017.c52b424Pins git:20261017.c52b424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- umararshad4/honey-stack
- Path
skills/incident/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.c52b424, committed Oct 17, 2026
- First version recorded
- Oct 17, 2026
- Size
- 4,397 bytes
- Repository stars
- 4
- License
- MIT
Respond to a production outage: assess severity, mitigate first (roll back/flip a flag/scale), investigate safely, communicate, write a blameless postmortem. Use when prod is down, degraded, or errors spike.
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 A live outage is not a debugging session. **Restore service first, understand why later.** Different from the `debug` skill, which is for local, non-urgent root-causing. ## What an AI agent must NOT do An agent **never makes a unilateral risky change to production during an incident.** Mitigations that mutate prod — **rollback, feature-flag flips, scaling, failover, traffic shedding, config changes** — need **explicit human approval** before you run them. You *may* autonomously: read dashboards/logs/traces, correlate "what changed", draft the status update, build the timeline, and *recommend* a specific mitigation with rationale — then wait for a human. Never run a write/mutating query on prod, never restart or flush state on a hunch, never post an external status update without sign-off. ## Lifecycle Detect → Acknowledge (fast, so others know it's owned) → Assess severity → **Mitigate (stop the bleeding)** → Communicate → Resolve → Postmortem. Declare early; under-declaring costs more than over-declaring. ## Severity (classify by user/business impact, not cause) …
Read the whole file at its exact version.
How to install
mdr add umararshad4/honey-stack/incident@sha256:b2ad0fa9c41916d6The line at the top of this page pins the label git:20261017.c52b424, 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_ciutrjsrvtqhhbwn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 17, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.c52b424 latest | 2026-10-17 | c52b424 | 4,397 B | A | view · diff |
| git:20261017.e40035b | 2026-10-17 | e40035b | 4,372 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 (4397 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
umararshad4/honey-stack · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ciutrjsrvtqhhbwn GET https://markdownregistry.com/api/v1/resolve?ref=umararshad4/honey-stack/incident GET https://markdownregistry.com/api/v1/blob/b2ad0fa9c41916d64f694d66d37307bbdadbfb4f594840561c0a4f19c45443d7
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 umararshad4/honey-stack
Every file in umararshad4/honey-stack