CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/incident-response/skills/postmortem-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is highly actionable with concrete templates, a timed facilitation guide, and specific anti-pattern guidance, but it inconsistently applies progressive disclosure: it declares templates belong in references/details.md yet inlines two large templates while omitting the standard one. Tightening this split and de-duplicating the Do's/Don'ts versus Anti-Patterns sections would materially improve token efficiency.

Suggestions

Move the inline Template 2 (5 Whys) and Template 3 (Quick Postmortem) into references/details.md so the body matches its own declaration that the template library lives there, keeping only a brief summary of each template type in the body.

Merge the Best Practices Do's/Don'ts list into the Anti-Patterns table (or vice versa) — both cover blame, follow-up, and action-item scope, so combining them removes ~15 lines of redundant guidance.

Summarize the standard postmortem document's section structure (or the Draft/In Review/Final status workflow) inline so the most common artifact's shape is visible without opening the reference.

DimensionReasoningScore

Conciseness

The body announces "Full template library and detailed worked examples live in `references/details.md`" yet still inlines ~100 lines of Templates 2 and 3, and the Do's/Don'ts list largely duplicates the Anti-Patterns table. Mostly efficient but with unnecessary duplicated content that could be tightened, matching anchor 3 rather than 4's "minor instances".

3 / 5

Actionability

Provides concrete, copy-paste-ready formats: a full 5 Whys worked example with evidence, a quick-postmortem template, a timed 60-minute meeting structure, and a specific anti-patterns table with better approaches. It is not 5 because the standard full postmortem — the most common artifact — has its template only in the reference file, leaving a minor coverage gap in the body.

4 / 5

Workflow Clarity

Clear sequencing via the Day 0 to Quarterly timeline and the staged, time-boxed meeting agenda, with follow-up verification explicitly emphasized ("Don't skip follow-up - Verify actions completed"). Not 5 because document review checkpoints (Draft/In Review/Final) are implicit in the body and only surfaced in the reference file — minor validation gaps matching anchor 4.

4 / 5

Progressive Disclosure

The reference to `references/details.md` is clearly signaled and one level deep, but the body then inlines large template content that it explicitly says lives in that reference, and the inline numbering starts at "Template 2" with no Template 1 in the body. This mismatch between declared and actual placement matches anchor 3 ("content that should be separate is inline") rather than anchor 4's "minor organization gaps".

3 / 5

Total

14

/

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 description that explicitly states both capabilities and trigger conditions with concrete, natural phrases. The main improvement opportunities are adding common synonyms (retrospective, post-incident review) and acknowledging the facilitation/culture-building capabilities the skill actually covers.

DimensionReasoningScore

Specificity

"root cause analysis, timelines, and action items" plus "write effective blameless postmortems" lists several concrete capabilities, matching anchor 4. It is not 5 because capabilities covered in the body (facilitating blameless meetings, building learning culture) are absent from the description.

4 / 5

Completeness

Clearly answers "what" ("Write effective blameless postmortems with root cause analysis, timelines, and action items") and "when" with an explicit "Use when..." clause listing three concrete trigger scenarios, matching the anchor 5 example structure. It exceeds anchor 4, whose "when" is a single generic clause.

5 / 5

Trigger Term Quality

"incident reviews", "writing postmortem documents", and "incident response processes" are natural user phrases, giving good keyword coverage. It falls short of anchor 5 because common synonyms like "post-incident review", "retrospective", and the "post-mortem" spelling variant are missing.

4 / 5

Distinctiveness Conflict Risk

Postmortem/incident-review writing is a clear niche with distinct triggers ("postmortem documents", "incident reviews") unlikely to fire for unrelated skills, matching anchor 5. Not 4 because the triggers are specific enough that overlap risk with closely related skills is minimal.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/incident-response/skills/postmortem-writing/SKILL.md

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.