postmortem-writing

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.

Quality

71%

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 ./skills/postmortem-writing/SKILL.md

Quality

Content

42%Weight 40%Scale 1-3

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

The skill is highly actionable but suffers from severe verbosity and no progressive disclosure: three complete templates and a facilitation guide are inlined in a single ~380-line file. Splitting templates into reference files and adding a lean quick-start would materially raise quality.

Suggestions

Move the three full templates and facilitation guide into separate files under references/ (e.g. templates/standard-postmortem.md) and link to them from a concise overview, restoring progressive disclosure.

Replace the generic 'Instructions' bullets ('Apply relevant best practices and validate outcomes') with concrete, postmortem-specific drafting and validation steps.

Trim the repetitive worked example to essentials or relocate it to an example reference, since Claude can already construct a postmortem once given a template.

Dimension	Reasoning	Score
Conciseness	The body is a ~380-line monolith dominated by three full template documents and a worked example Claude could largely generate itself, with no bundle files to offload detail.	1 / 3
Actionability	Provides complete, copy-paste-ready templates (Standard Postmortem, 5 Whys, Quick Postmortem) with concrete timelines, action-item tables, and a facilitation script.	3 / 3
Workflow Clarity	Sequences exist (timeline, meeting agenda) and validation is implied by review/finalize states, but there is no explicit validate-then-proceed checkpoint for the drafting workflow.	2 / 3
Progressive Disclosure	No bundle files exist and the full templates and facilitation guide are inlined in SKILL.md rather than split into referenced files, leaving no one-level-deep disclosure structure.	1 / 3
	Total	7 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, well-formed description that concretely states capabilities and provides explicit trigger guidance in third person. It cleanly answers both what the skill does and when to invoke it without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('root cause analysis, timelines, and action items') rather than vague language.	3 / 3
Completeness	Explicitly states both what it does (write postmortems with RCA/timelines/action items) and when to use it via the 'Use when conducting incident reviews...' clause.	3 / 3
Trigger Term Quality	Includes natural terms users would say such as 'incident reviews', 'postmortem documents', and 'incident response processes'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (blameless postmortems) with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	12 / 12 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: 2 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/postmortem-writing/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.