incident-readout SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
incident-readout from yeaight7/agent-powerups is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yeaight7/agent-powerups/incident-readout@git:20260606.51fc3fePins git:20260606.51fc3fe in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yeaight7/agent-powerups
- Path
skills/incident-readout/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260606.51fc3fe, committed Jun 6, 2026
- First version recorded
- Jun 2, 2026
- Size
- 2,345 bytes
- Repository stars
- 8
- License
- Apache-2.0
Use when a bug fix or complex debugging session concludes and a blameless post-mortem summary is needed for human review.
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
## Purpose When a complex debugging session ends, produce an incident readout. This prevents knowledge loss and helps humans review the fix quickly. Keep it blameless: causes and prevention, not people. ## When to Use - A bug fix landed after a non-trivial debugging session - An incident is resolved and needs a reviewable summary - Session knowledge would otherwise be lost at handoff ## Inputs - The fix (diff or commits) and the debugging context from the session - The related PR or issue, if one exists ## Workflow 1. **Reconstruct the facts from history** — pull them from the repo rather than recalling them: ```bash git log --oneline -10 # the fix commits git show <fix-commit> --stat # what the fix touched gh pr view <number> --json title,body,comments # if a PR exists ``` 2. **Fill the readout structure.** Output an incident readout document (or print to terminal) using this structure: ```markdown ### 1. The Symptom What was reported? (1-2 sentences) ### 2. The Root Cause What was the actual underlying technical reason for the failure? Be highly …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/incident-readout@sha256:3f187f0a1ad43dc5The line at the top of this page pins the label git:20260606.51fc3fe, 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_w73vfj5c4tbixrv3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 2, 2026 and Jun 6, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.51fc3fe latest | 2026-06-06 | 51fc3fe | 2,345 B | A | view · diff |
| git:20260602.4a7c336 | 2026-06-02 | 4a7c336 | 871 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 (2345 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
yeaight7/agent-powerups · 8 stars · license Apache-2.0 · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w73vfj5c4tbixrv3 GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/incident-readout GET https://markdownregistry.com/api/v1/blob/3f187f0a1ad43dc521a769589a64272fa4cb68369711c6ebe218db0c430a1f8a
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 yeaight7/agent-powerups
Every file in yeaight7/agent-powerups