operator-incident-evidence SKILL.md skillA
operator-incident-evidence from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/operator-incident-evidence@git:20261011.81f7574Pins git:20261011.81f7574 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
skills/operator-incident-evidence/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261011.81f7574, committed Oct 11, 2026
- First version recorded
- May 22, 2026
- Size
- 13,304 bytes
- Repository stars
- 14
- License
- MIT
Use when the user is GATHERING EVIDENCE FOR A POSTMORTEM / INCIDENT REPORT after the incident is past peak. Natural phrasing: "build the evidence package for last night''s incident", "I need to write the postmortem — what does cub-scout have?", "gather all the data we have about the prod outage", "what changed on payments-api between 14:00 and 16:00?", "produce an audit trail for the rollback decision", "save the evidence before the cluster state moves on". Composes `trace` + `compare…
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
# operator-incident-evidence The postmortem-evidence loop. After the incident is past peak (or fully resolved), the operator needs to **assemble a structured evidence package** for the postmortem doc, the release-engineering meeting, or the audit ticket. This skill composes `trace` + `compare three-way` + `bundle` + `history` + `audit` + `receipt verify --save` into a deterministic, fingerprinted record. Read-only by design. Postmortems should **never** mutate cluster state — capture, don't fix. ## When to use Explicit phrasings: - "Build the evidence package for last night's incident" - "I need to write the postmortem — what does cub-scout have on payments-api?" - "Gather all the data we have about the prod outage at 14:00" - "What changed on payments-api between 14:00 and 16:00?" - "Produce an audit trail for the rollback decision" - "Save the evidence before the cluster state moves on" - "Snapshot everything relevant to the outage" - "Fingerprinted evidence for the SEV-2 ticket" Implicit intents: - The incident is **past peak** (the pager is no longer firing); time pressure has eased …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/operator-incident-evidence@sha256:a882708ae3d4eef1The line at the top of this page pins the label git:20261011.81f7574, 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_5ftshfazfvxj7ypw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 22, 2026 and Oct 11, 2026, about one every 47 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.81f7574 latest | 2026-10-11 | 81f7574 | 13,304 B | A | view · diff |
| git:20260926.4c4b67c | 2026-09-26 | 4c4b67c | 13,202 B | A | view · diff |
| git:20260522.8abb9be | 2026-05-22 | 8abb9be | 12,670 B | A | view · diff |
| git:20260522.095dc05 | 2026-05-22 | 095dc05 | 12,646 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 (13304 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
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5ftshfazfvxj7ypw GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/operator-incident-evidence GET https://markdownregistry.com/api/v1/blob/a882708ae3d4eef174d35ea92ff85479beb4ba2246c6bbf920cab9cc077fd322
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.