incident-evidence-review SKILL.md skillA
incident-evidence-review from gsa-tts/agentic-coding-patterns is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gsa-tts/agentic-coding-patterns/incident-evidence-review@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gsa-tts/agentic-coding-patterns
- Path
.agents/skills/incident-evidence-review/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Aug 20, 2026
- First version recorded
- Jul 2, 2026
- Size
- 10,884 bytes
- Repository stars
- 16
- License
- CC0-1.0
Review incident and postmortem write-ups for evidence discipline — separating facts, assumptions, hypotheses, and timeline — and flag unsupported claims, without conducting the investigation or determining root cause.
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
# Skill: Incident Evidence Review Review an incident or postmortem write-up for **evidence discipline**. Sort every statement into **facts**, **assumptions**, **hypotheses**, and **timeline** entries, then flag anything presented as fact that lacks support and any hypothesis stated as a settled conclusion. > **Self-limiting: this skill reviews incident write-ups; it does not run the > investigation.** It never gathers live evidence, never determines authoritative > root cause, and never handles live incident data. All examples here are > synthetic. The investigation process itself belongs to the > [agentic-coding-playbook](https://github.com/GSA-TTS/agentic-coding-playbook) > and your agency incident-response (IR) plan; this skill defers to both. ## When to Use - Reviewing a postmortem or incident report draft before it is shared - Checking whether a write-up's conclusions are actually supported by evidence - Separating what was observed from what was guessed after an incident - Confirming a timeline is complete and ordered before publication ## When NOT to Use - During a live incident — follow the IR plan, not a document review …
Read the whole file at its exact version.
How to install
mdr add gsa-tts/agentic-coding-patterns/incident-evidence-review@sha256:77b52ff67dbcb41aThe line at the top of this page pins the label v1.0.0, 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_iltwkdku4virwjk2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 2, 2026 and Aug 20, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-20 | ae5b0dd | 10,884 B | A | view · diff |
| v1.0.0 | 2026-07-28 | ea6ea67 | 10,881 B | A | view · diff |
| v1.0.0 | 2026-07-02 | c736287 | 10,523 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 (10884 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
gsa-tts/agentic-coding-patterns · 16 stars · license CC0-1.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iltwkdku4virwjk2 GET https://markdownregistry.com/api/v1/resolve?ref=gsa-tts/agentic-coding-patterns/incident-evidence-review GET https://markdownregistry.com/api/v1/blob/77b52ff67dbcb41a2543852f053cebd8b4fb1ba26cb4bad427f64df2fae88278
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.