CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

post-mortem

/c-level-agents:post-mortem [decision] — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.

64

Quality

80%

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/post-mortem/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured and highly actionable, with a complete output template and explicit routing. Its main weakness is workflow clarity: the retrospective process is implied by the record template rather than stated as steps, and no validation or fallback checkpoints exist for missing outcome data.

Suggestions

Add an explicit numbered procedure before the output template: locate the decision record and execution plan, gather actual outcomes, score against pre-committed criteria, audit assumptions and dissent, then write the record — instead of relying on the template's section order to imply the sequence.

Add validation/branching checkpoints, e.g., what to do when actual outcome metrics are unavailable (mark criterion UNMEASURED and note the gap) or when the pre-committed criteria cannot be found in the decision record.

Define the rule for choosing the overall WIN/PARTIAL/LOSS/MIXED status (e.g., based on which success criteria were met vs. which kill criteria triggered) so the status is scored rather than guessed.

DimensionReasoningScore

Conciseness

The body is largely lean: the output template is the deliverable itself and sections are short and functional. Minor over-explanation remains — the "Why Pre-Committed Criteria Matter" and "Why Revisit Dissent" rationale paragraphs and the line "This is the rigor that compounds over time" could be trimmed — matching anchor 4 rather than the every-token-earns-its-place anchor 5, and well above the some-unnecessary-explanation anchor 3.

4 / 5

Actionability

Provides a copy-paste-ready output template with an exact save path (`~/.claude/postmortems/YYYY-MM-DD-<slug>.md`), concrete scoring tables, dissent/assumption audit formats, and explicit routing commands. Not 5 because minor gaps remain: no decision rule for choosing WIN/PARTIAL/LOSS/MIXED overall status, and no pointer to where the input decision record is stored.

4 / 5

Workflow Clarity

The sequence is present but implicit — conveyed by the template's section order (Outcome Scoring → Dissent → Assumption Audit → Process Lessons → Status) rather than explicit procedural steps, and validation checkpoints are missing (e.g., what to do when actual outcome metrics are unavailable, or how to verify the decision record was found). This matches anchor 3 ("sequence present but checkpoints missing or implicit"); not 4 because execution steps are never stated as a process, though the artifact structure keeps it above anchor 2.

3 / 5

Progressive Disclosure

A self-contained single-file skill with no bundle files, well-organized sections, and clearly signaled cross-links (Routing, Related). Not 5 because the ~55-line output template makes up half the file and could live in a reference file, and at ~110 lines the skill exceeds the under-50-line threshold where well-organized sections alone merit a 5; not 3 because the structure is good and no content is clearly misplaced.

4 / 5

Total

15

/

20

Passed

Description

83%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 clearly states what the skill does and when to use it, with concrete trigger conditions and a helpful example. Its only weaknesses are missing natural synonyms and unaddressed overlap with the sibling /em:postmortem skill.

DimensionReasoningScore

Specificity

Names several concrete actions — "Honest retrospective on an executed decision, scored against original assumptions and dissent" — covering scoring against pre-committed criteria and revisiting dissent. Not 5 because "Closes the strategic sprint loop" is framing rather than an action, and full capability coverage is not enumerated; not 3 because more than 1-2 specific actions are stated.

4 / 5

Completeness

Explicitly answers both what ("Honest retrospective on an executed decision, scored against original assumptions and dissent") and when ("Use when a decision hits its 90-day review checkpoint or its kill criteria trigger"), with a concrete usage example ("scoring last quarter's pricing change against its pre-committed success metrics"). This matches the anchor-5 pattern of clear what + when + concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "post-mortem", "retrospective", "90-day review checkpoint", "kill criteria trigger", "success metrics", "pricing change" — phrases a user would plausibly say. A few natural variations ("postmortem", "look back at the decision") are missing, so it falls short of the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — pre-committed criteria review within the /cs strategic-sprint pipeline — with triggers (90-day checkpoint, kill criteria) unlikely to fire for unrelated skills. Not 5 because the skill body itself lists a sibling `/em:postmortem` doing near-identical retrospective work, an overlap the description does not disambiguate; not 3 because the pipeline framing and specific triggers clearly separate it from generic review skills.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/post-mortem/SKILL.md

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.