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.

79

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A high-quality instruction-only skill: lean operational content, concrete examples and good/bad contrasts, a clearly sequenced workflow with a tracking feedback loop, and a single well-signaled real reference one level deep. It avoids explaining concepts Claude already knows and keeps every token actionable.

DimensionReasoningScore

Conciseness

The body is dense operational guidance Claude does not inherently know (the 6-section framework, blameless nuance, timed agenda, failure patterns) with no padding over familiar concepts; every section earns its place. Not scored below 3 because it does not explain what a postmortem is and stays lean despite its length.

3 / 3

Actionability

Highly concrete for an instruction-only skill: a worked five-whys example, a four-factor causal chain, action-item criteria with good/bad contrasts ('Improve monitoring' vs 'Add alert on connection pool saturation, threshold 80%, page on-call'), and a copy-ready markdown output template with table headers.

3 / 3

Workflow Clarity

A clearly sequenced 6-step Workflow (Schedule → Gather → Run meeting → Write → Distribute → Track) with a minute-budgeted agenda and an ownership rule ('the facilitator is not the scribe'), plus a feedback loop where unclosed action items re-surface in the next AAR. Not capped at 2 because the task is a retrospective process, not a destructive/batch/XML operation requiring validate-fix-retry checkpoints.

3 / 3

Progressive Disclosure

Well-organized inline overview with a single clearly-signaled, one-level-deep reference to the real file references/aar-template.md (verified to exist), which offloads the fillable template. Not scored below 3 because navigation is explicit and references are exactly one level deep.

3 / 3

Total

12

/

12

Passed

Description

100%

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

An excellent description: concrete actions, exhaustive natural trigger terms, explicit what-and-when guidance, and a well-bounded niche, all in third-person voice. It satisfies every anchor at the top level with no over-claims or filler.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'capture timeline, root cause analysis, contributing factors, and actionable lessons' — across launch/incident/project, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Run a structured after-action review...') and when with dedicated trigger clauses ('Use this skill whenever...', 'Triggers on...', 'Also triggers when...').

3 / 3

Trigger Term Quality

Dense natural-language triggers a user would actually say: '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', plus the just-shipped/just-resolved phrasing.

3 / 3

Distinctiveness Conflict Risk

A clearly bounded post-event-analysis niche with distinct triggers; the scope is narrowed to past events, and the body further distinguishes it from active incident-response and launch planning, so conflict risk is low. Not scored below 3 because the framing is specific rather than generic.

3 / 3

Total

12

/

12

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.