post-mortem

/cs: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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

78%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 instruction-only workflow skill with a concrete, copy-paste-ready post-mortem template, clear sequencing, and explicit routing. Its main weakness is that the metric-gathering and validation steps are implicit rather than spelled out as explicit checkpoints.

Suggestions

Add an explicit validation checkpoint before scoring, e.g. 'Confirm the pre-committed success/kill criteria are pulled from the original /cs:decide record before filling the scoring tables.'

Add brief concrete guidance on how to source 'Actual' outcome values (metrics, events, customer signals) so the gathering step is actionable rather than implicit.

Trim or merge the two short 'Why...' rationale sections into the template intro to reduce prose, since the core value is already conveyed by the template and routing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient: the body is a concrete output template plus short skill-specific rationale ('Why Pre-Committed Criteria Matter', 'Why Revisit Dissent') that earns its place rather than explaining concepts Claude already knows; only minor trimming possible.	4 / 5
Actionability	Provides a copy-paste-ready output record template with concrete fields, scoring tables, file save path, and routing rules; minor gap is that the process for gathering and verifying 'Actual' outcome metrics is left implicit.	4 / 5
Workflow Clarity	Clear sequence from trigger to inputs to filled scoring tables to dissent/assumption audit to forward actions to routing, with explicit feedback in the Status section (LOSS → schedule follow-up boardroom); the pre-committed-criteria check serves as the validation mechanism though it is not labeled as an explicit checkpoint.	4 / 5
Progressive Disclosure	No bundle files are present and none are needed; the body is well-organized into clearly headed sections (Pipeline Position, When to Run, Inputs, Output, Routing, Related) with one-level-deep cross-skill navigation, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 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, specific description that explicitly states both capability and trigger conditions with concrete examples, written in appropriate third-person voice. It is clearly distinguishable from sibling skills; the only minor gaps are a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Honest retrospective on an executed decision, scored against original assumptions and dissent', 'scoring last quarter's pricing change against its pre-committed success metrics'), with only minor gaps in coverage rather than the full multi-action enumeration of a 5.	4 / 5
Completeness	Explicitly answers both what ('Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop.') and when ('Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change...') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage ('post-mortem', 'retrospective', '90-day review checkpoint', 'kill criteria trigger', 'pricing change') that users would naturally say, though a few synonyms (e.g. 'retro', 'lessons learned') are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (strategic-sprint post-mortem at a 90-day checkpoint tied to pre-committed /cs:decide criteria) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: c-level-agents/skills/post-mortem/SKILL.md
Commit: 19392f7

Reviewed: ~11 hours ago

Table of Contents

Discovery Implementation Validation

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.