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.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a well-organized, lean framework with concrete examples, a sequenced workflow, and a verified external reference. It is highly actionable; only the fillable output template and modest feedback-loop structure keep it from full marks.

Suggestions

Add an explicit feedback loop in the workflow for failed or incomplete action items (e.g., track -> re-surface -> escalate) to strengthen workflow_clarity.

Consider moving the large output-format markdown template into the existing references/aar-template.md to reduce duplication and tighten the inline body.

Make the action-item table example concrete with realistic sample owner/due values to improve copy-paste actionability.

DimensionReasoningScore

Conciseness

Lean and efficient; it assumes Claude's competence, never explaining what a postmortem is, and every section earns its place with no padding.

5 / 5

Actionability

Highly actionable with a worked five-whys example, a causal-chain example, and an action-item table with explicit criteria (Specific/Owned/Dated/Sized/Closeable); the output format is a fillable template rather than fully copy-paste-ready code, a minor gap.

4 / 5

Workflow Clarity

Clear 6-step sequence with a timeboxed agenda and explicit follow-through checkpoint ('Action items that don't close re-surface in the next AAR'); this is not a destructive/batch operation, so the validation cap does not apply, though explicit feedback loops are limited.

4 / 5

Progressive Disclosure

Good structure with a well-signaled, verified one-level-deep reference (references/aar-template.md); most content is appropriately inline with minor organization gaps in the long output-format block.

4 / 5

Total

17

/

20

Passed

Description

100%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.

The description is comprehensive and well-crafted, explicitly answering what the skill does and when to use it with a rich set of natural trigger terms and synonyms. It is specific, distinct from sibling skills, and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('capture timeline, root cause analysis, contributing factors, and actionable lessons') across three named domains (launch, incident, project), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (structured review capturing timeline, RCA, factors, lessons) and 'when' ('Use this skill whenever...', 'Triggers on...', 'Also triggers when...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: postmortem, retrospective, AAR, retro, post-incident review, lessons learned, blameless postmortem, RCA, five whys — phrases users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche as after-the-fact analysis, distinct from active incident response (cross-referenced as incident-response), with specific triggers that minimize overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.