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.
80
71%
Does it follow best practices?
Impact
92%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/postmortem-writing/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates its purpose, lists concrete deliverables, and provides explicit trigger guidance. It uses third person voice, includes natural keywords users would say, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Write effective blameless postmortems', 'root cause analysis', 'timelines', and 'action items'. These are distinct, concrete deliverables. | 3 / 3 |
Completeness | Clearly answers both 'what' (write blameless postmortems with root cause analysis, timelines, and action items) and 'when' (conducting incident reviews, writing postmortem documents, improving incident response processes) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'postmortems', 'root cause analysis', 'incident reviews', 'postmortem documents', 'incident response'. These cover the main terms someone needing this skill would use. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around incident postmortems and blameless reviews. The terms 'postmortem', 'incident review', 'root cause analysis', and 'blameless' are highly specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, well-structured postmortem templates with realistic examples that Claude can directly use. However, it is extremely verbose — much of the content (blameless culture explanation, facilitation tips, do's/don'ts) teaches concepts Claude already knows. The monolithic structure with everything inline wastes context window tokens and would benefit greatly from splitting templates into separate referenced files.
Suggestions
Reduce the SKILL.md to a concise overview (~50 lines) with key principles and a quick-start template, moving the full Standard and 5 Whys templates into separate referenced files (e.g., STANDARD_TEMPLATE.md, FIVE_WHYS.md).
Remove or drastically condense sections that explain concepts Claude already knows: blameless culture table, 'When to Use This Skill' list, facilitation tips, and the Do's/Don'ts lists.
Add a validation checklist (e.g., 'Before finalizing: verify all timeline entries have timestamps, all action items have owners and due dates, root cause analysis goes at least 3 levels deep') to improve workflow clarity.
Cut the 'Core Concepts' and 'Postmortem Triggers' sections entirely — Claude understands these concepts and they consume tokens without adding actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Includes extensive explanations of blameless culture concepts, facilitation tips, and meeting structures that Claude already understands. The full example postmortem template with fictional data is useful but could be much more concise. The 'When to Use This Skill' and 'Core Concepts' sections add little value for Claude. | 1 / 3 |
Actionability | Provides three complete, copy-paste-ready markdown templates (standard, 5 Whys, quick postmortem) with realistic examples. The templates include specific fields, formatting, and example content that Claude can directly adapt. The facilitation guide and anti-patterns table provide concrete, specific guidance. | 3 / 3 |
Workflow Clarity | The postmortem timeline (Day 0 through Quarterly) provides a clear sequence, and the meeting structure has timed sections. However, there are no validation checkpoints — no steps to verify the postmortem is complete, no checklist to ensure all sections are filled, and no feedback loop for reviewing action item quality before finalizing. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no bundle files or references to supporting documents. The three full templates, facilitation guide, anti-patterns, best practices, and resources are all inline. The templates alone could each be separate referenced files, with SKILL.md serving as a concise overview. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
b09ec7f
- 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.