Name: postmortem-writing
Rating: 49.6 (1 reviews)
Author: administrakt0r

postmortem-writing

Comprehensive guide to writing effective, blameless postmortems that drive organizational learning and prevent incident recurrence.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/postmortem-writing/SKILL.md

The canonical home for this skill is postmortem-writing in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

53%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 content is rich with concrete, actionable templates but is monolithic and over-long, inlining material that should be split into referenced files, with a broken reference to a missing playbook.

Suggestions

Move the three full templates and the facilitation guide into separate files under references/ and link to them one level deep, keeping SKILL.md as a concise overview.

Fix or remove the dangling "resources/implementation-playbook.md" reference (the directory does not exist), and align the path to the actual bundle location.

Trim the generic Instructions bullets and the fully worked example postmortem, or relocate the worked example to a reference file, to reduce token spend.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful template material, but it inlines a ~150-line fully filled example postmortem and includes generic instructions ("Clarify goals, constraints, and required inputs", "Apply relevant best practices"), and hardcodes time-sensitive values (2024-01-15, v2.3.4) that pad the budget.	3 / 5
Actionability	Copy-paste-ready markdown templates (standard postmortem, 5 Whys, quick postmortem), an action-items table with owner/due/ticket columns, and a timed facilitation agenda give concrete executable guidance, though the underlying "how to write" guidance is thinner than the templates themselves.	4 / 5
Workflow Clarity	A Quick Start timeline and a 60-minute meeting agenda provide a sequence, but there are no explicit validation/verification checkpoints for confirming postmortem quality before finalizing, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), yet the body inlines three full templates and a facilitation guide that clearly belong in separate files, and its one external reference ("resources/implementation-playbook.md") points to a non-existent path.	2 / 5
	Total	12 / 20 Passed

Description

53%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 clearly states the domain and purpose but omits any explicit "when to use" trigger guidance, which caps completeness. Trigger terms are relevant but lack common synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when conducting post-incident reviews, writing postmortems or RCAs, or facilitating blameless retrospectives."

Include natural synonyms such as "post-incident review", "incident report", and "root cause analysis" so the description matches varied user phrasing.

Replace outcome-oriented phrasing ("drive organizational learning") with one more concrete capability to lift specificity above 3.

Dimension	Reasoning	Score
Specificity	"writing effective, blameless postmortems" names the domain and one concrete action, but "drive organizational learning" and "prevent incident recurrence" are outcome claims rather than additional concrete capabilities, so coverage is not comprehensive.	3 / 5
Completeness	The description gives a clear "what" ("Comprehensive guide to writing effective, blameless postmortems") but contains no "Use when..." trigger clause, which the rubric caps at 3.	3 / 5
Trigger Term Quality	"postmortems" and "blameless postmortems" are natural terms a user would say, but common synonyms like "post-incident review", "incident report", or "root cause analysis / RCA" are absent.	3 / 5
Distinctiveness Conflict Risk	"blameless postmortems" carves a fairly distinct niche with minimal overlap risk against related skills, though it is not maximally specific with concrete trigger phrases.	4 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/postmortem-writing/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.