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.

1.26x

Quality

79%

Does it follow best practices?

Impact

92%

1.26x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/postmortem-writing/SKILL.md

The canonical home for this skill is postmortem-writing in wshobson/agents

Quality

Content

71%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 highly actionable with concrete, copy-paste-ready templates and a clear temporal workflow, but it is verbose and monolithic — a large worked example and multiple full templates are inlined in one file rather than split into well-signaled reference files.

Suggestions

Move the three full templates and the facilitation guide into separate reference files (e.g. templates/standard-postmortem.md, templates/5-whys.md, facilitation-guide.md) and link to them from a concise overview in SKILL.md to improve progressive disclosure.

Trim the fully-filled standard template worked example: keep a compact skeleton with placeholder fields rather than a ~160-line fictional incident with specific dates, dollar figures, and ticket IDs, which pads the token budget.

Add an explicit validation/feedback step to the writing workflow (e.g. draft → peer review checklist → finalize) with a concrete review checklist to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~393-line body is mostly useful reference content rather than concept-explanation fluff, but the fully-filled worked example (specific dates, $45,000 figures, named people, ticket IDs) and some redundancy across templates could be tightened, fitting "mostly efficient but includes some unnecessary content".	3 / 5
Actionability	Provides three copy-paste-ready markdown templates (standard, 5-Whys, quick), a timeline table format, action-item tables, and a time-boxed facilitation agenda, giving fully executable guidance that covers the common cases for an instruction-only skill.	5 / 5
Workflow Clarity	The Quick Start timeline (Day 0 draft → meeting → finalize → action items → quarterly review) and the sequenced 60-minute meeting structure give a clear sequence with implicit review checkpoints, though no explicit validate/fix/retry feedback loop is spelled out.	4 / 5
Progressive Disclosure	The skill is a single monolithic ~393-line file with clear section headers but no bundle files; large content that could be split out (three full templates, the facilitation guide) is inlined, matching the "some structure but content that should be separate is inline" anchor.	3 / 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.

The description is strong, clearly stating both the capability and explicit use-when triggers with concrete, natural language. It is comprehensive and distinct, with only minor gaps in synonym coverage and action enumeration.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("root cause analysis, timelines, and action items") but does not exhaustively cover all postmortem activities such as facilitation or culture-building, fitting the "several specific actions; minor gaps" anchor.	4 / 5
Completeness	Explicitly answers both what ("Write effective blameless postmortems with root cause analysis, timelines, and action items") and when ("Use when conducting incident reviews, writing postmortem documents, or improving incident response processes") with concrete trigger phrases, matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("incident reviews", "postmortem documents", "incident response processes") with good coverage, though a few common synonyms like "post-incident review" or "RCA" are missing.	4 / 5
Distinctiveness Conflict Risk	Postmortem writing is a clear, well-bounded niche with distinct triggers ("blameless postmortems", "root cause analysis", "incident reviews") and minimal conflict 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: 2 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/postmortem-writing/SKILL.md
Commit: 6453c0b

Reviewed: about 8 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.