CtrlK
BlogDocsLog inGet started
Tessl Logo

after-action-report

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 analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is after-action-report in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable instruction skill that captures a clear framework and workflow with concrete examples and a properly signaled reference file, leaning only slightly verbose in spots.

Suggestions

Trim editorial asides like 'This is not consolation. It's calibration.' that restate what the surrounding guidance already implies, to tighten conciseness.

Add an explicit verification checkpoint in the workflow (e.g., confirm all action items have owner+due before closing the document) to push workflow clarity toward 5.

Move the full output-format template block into references/aar-template.md and link to it from the body instead of inlining the structure, deepening progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, but a few editorializing lines ('This is not consolation. It's calibration.') and mild over-explanation of blameless rationale could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance — a worked five-whys example, a causal-chain structure, and an action-item table with explicit criteria — with only minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

Clear sequenced six-step workflow with a timed meeting agenda; not a 5 because validation checkpoints are absent, though the non-destructive nature of documentation means no hard cap applies.

4 / 5

Progressive Disclosure

Body is well-structured with sectioned content and a clearly signaled one-level reference to the real references/aar-template.md; minor inlining of template structure keeps it just below 5.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-constructed description that names concrete capabilities, provides exhaustive natural trigger terms, and clearly separates when-to-use from the adjacent incident-response and launch-runbook skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'capture timeline, root cause analysis, contributing factors, and actionable lessons' — with comprehensive coverage rather than generic verbs.

5 / 5

Completeness

Explicitly answers both what (structured after-action review capturing timeline/RCA/lessons) and when ('Use this skill whenever...', 'Triggers on...', 'Also triggers when...').

5 / 5

Trigger Term Quality

Comprehensive natural triggers including synonyms users actually say: postmortem, retrospective, AAR, retro, lessons learned, blameless postmortem, RCA, five whys.

5 / 5

Distinctiveness Conflict Risk

Clear after-the-fact niche with explicit distinction from incident-response and launch-runbook; minor overlap risk with those adjacent skills, keeping it just below 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rampstackco/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.