CtrlK
BlogDocsLog inGet started
Tessl Logo

postmortem

/em:postmortem — Honest analysis of what went wrong. Use after a failed launch, missed quarter, or bad hire to run a blameless 5-Whys retrospective with a change register — e.g. dissecting why the Q3 release slipped six weeks.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/postmortem/SKILL.md

The canonical home for this skill is postmortem in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, actionable framework with strong sequencing and a usable output template. The main weakness is moderate verbosity in the framing/tone sections that restates concepts Claude already knows.

Suggestions

Trim the 'Why Most Post-Mortems Fail' and 'Tone of Good Post-Mortems' sections to essentials; Claude already understands blameless retrospectives, so keep only the diagnostic guidance that shapes behavior.

Consider moving the worked good/bad 5-Whys and action-item examples into a references file, keeping SKILL.md as a lean overview with the framework steps and output template inline.

Add a brief facilitation note for each step (e.g., who to involve, timebox) to close the minor actionability gaps in meeting execution.

DimensionReasoningScore

Conciseness

Mostly efficient actionable framing, but the 'Why Most Post-Mortems Fail' and 'Tone of Good Post-Mortems' sections are essay-like and explain blameless-retrospective concepts Claude already knows, so they could be tightened.

3 / 5

Actionability

Provides a concrete 7-step framework, good/bad example pairs with named owners and dates, and a copy-paste output-format template; minor gaps in meeting-facilitation specifics.

4 / 5

Workflow Clarity

Seven steps are clearly sequenced with explicit checkpoints (the 'test for a good root cause' and the Step 7 verification date); not a destructive/batch operation, so the validation cap does not apply.

4 / 5

Progressive Disclosure

Single well-organized file with clear section headers and no nested references; the output format and example library could optionally be split into reference files, but inlining is reasonable for this overview.

4 / 5

Total

15

/

20

Passed

Description

87%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 description that concisely conveys purpose, method, and trigger conditions in third-person voice with a concrete example. Minor room to add a couple more synonymous trigger phrases.

DimensionReasoningScore

Specificity

Names a concrete method ('blameless 5-Whys retrospective') and a concrete output ('change register') plus a worked example, giving several specific actions rather than vague abstractions.

4 / 5

Completeness

Explicitly answers both what ('run a blameless 5-Whys retrospective with a change register') and when ('Use after a failed launch, missed quarter, or bad hire') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'failed launch', 'missed quarter', 'bad hire', and 'what went wrong'; good coverage though a few synonymous trigger phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (blameless post-mortem retrospectives) with distinct triggers, making overlap with unrelated skills unlikely.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/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.