after-action-report 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.
after-action-report from rampstackco/claude-skills-pm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rampstackco/claude-skills-pm/after-action-report@git:20261005.1e83d8fPins git:20261005.1e83d8f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rampstackco/claude-skills-pm
- Path
skills/after-action-report/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261005.1e83d8f, committed Oct 5, 2026
- First version recorded
- May 19, 2026
- Size
- 9,902 bytes
- Repository stars
- 4
- License
- MIT
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, 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
# After-Action Report Run a structured retrospective on a launch, incident, or completed project. Produce actionable lessons, not just a document. This skill is for after-the-fact analysis. For active incident response, use `incident-response`. For planning launches, use `launch-runbook`. --- ## When to use - After any incident (any severity) - After every major launch - At the end of a project (sprint retro, quarterly retro, project closeout) - When a recurring issue has happened enough times to demand investigation - When a decision didn't work out and the team wants to learn ## When NOT to use - During an active incident (use `incident-response`) - For pre-launch planning (use `launch-runbook`) - For one-off bug fixes that don't merit broad analysis --- ## Required inputs - The event being analyzed (incident, launch, project) - A timeline reconstructed from logs, chat, tickets - Participant accounts of what they observed and did - Outcomes and impact (what actually happened to users, the business) --- ## The framework: blameless analysis …
Read the whole file at its exact version.
How to install
mdr add rampstackco/claude-skills-pm/after-action-report@sha256:97c20ae6885fc9d7The line at the top of this page pins the label git:20261005.1e83d8f, 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_j4eo7dchdyl7meb3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 19, 2026 and Oct 5, 2026, about one every 139 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.1e83d8f latest | 2026-10-05 | 1e83d8f | 9,902 B | A | view · diff |
| git:20260519.62f33d9 | 2026-05-19 | 62f33d9 | 9,379 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 (9902 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
rampstackco/claude-skills-pm · 4 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j4eo7dchdyl7meb3 GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills-pm/after-action-report GET https://markdownregistry.com/api/v1/blob/97c20ae6885fc9d70e65b249070914ed919df7c5a406e8c26548ee5d3cf5749e
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 rampstackco/claude-skills-pm
Every file in rampstackco/claude-skills-pm