CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/post-mortem-author

Build-an-X workflow that produces a blameless post-mortem from an incident - captures the timeline (chronological event sequence with sources), root cause analysis (what + why, not who), impact (users / revenue / SLO debt), action items (with owners + due dates + measurable success criteria), and "what went well" (intentional). Per Google SRE: "Blameless postmortems are a tenet of SRE culture." Use after every user-visible incident, not just severe ones.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is a well-structured, highly actionable process skill: a sequenced 5-step workflow with explicit closure gates, a fillable section skeleton, and a complete worked example. Its only weakness is conciseness — the Google SRE blameless framing is quoted and restated several times, which adds tokens without adding new guidance.

Suggestions

Collapse the repeated Google SRE blockquotes: state the blameless principle once in the Overview and reference it from Step 2 / Anti-patterns rather than quoting 'Blameless postmortems are a tenet of SRE culture' and 'not punishment' verbatim in multiple sections.

Trim the Overview's three consecutive SRE blockquotes to one defining quote plus a single sentence on the blameless framing, since Claude already understands SRE postmortem culture.

Consolidate the redundantly stated 'what, not who' guidance (Overview, Step 1 item 5, Step 2, Anti-patterns) into one canonical statement referenced elsewhere.

DimensionReasoningScore

Conciseness

Mostly efficient but repeats conceptual justification Claude already knows — the Google SRE 'Blameless postmortems are a tenet of SRE culture' / 'not punishment' framing is quoted four times (Overview, Step 2, Anti-patterns, References) and the blameless principle is restated across multiple sections. Not level 3 because the repeated SRE blockquotes and restated framing are tokens that do not each earn their place; not level 1 because it does not pad with basic explanations of what a post-mortem or library is.

2 / 3

Actionability

Concrete and copy-paste ready: a fill-every-section skeleton, explicit action-item fields (Owner / Due date / Priority / Success criterion), a fully worked INC-1234 example with real Timeline and Action-items tables, and a storage directory layout — matching the 'fully executable... specific examples' anchor adapted to an instruction-only skill.

3 / 3

Workflow Clarity

A clear 5-step sequence (Author → Blameless review → Action item discipline → Approval + closure → Storage) with explicit gates: 'The post-mortem isn't "done" until' sign-off checklist and 'closed when all action items ship', plus Step 2's reject-blame-language before/after as a review checkpoint. Matches the 'clear sequence with explicit validation steps' anchor; the post-mortem is not a destructive/batch operation so the strict validate-fix-retry cap does not apply.

3 / 3

Progressive Disclosure

Overview body points to a single, clearly-signaled one-level reference — 'Copy the full section skeleton from references/post-mortem-document-template.md' (verified to exist) — with the worked example kept inline for illustration. Well-organized sections and easy navigation match the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong description: it specifies multiple concrete deliverables, gives natural trigger terms, and includes an explicit 'Use after every user-visible incident' clause covering both what and when. Slightly busy with the parenthetical detail and the embedded Google SRE quote, but every element earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete components — 'captures the timeline (chronological event sequence with sources), root cause analysis... impact (users / revenue / SLO debt), action items (with owners + due dates + measurable success criteria), and "what went well"' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('produces a blameless post-mortem' enumerating the sections) and when ('Use after every user-visible incident, not just severe ones'), matching the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Natural user terms — 'post-mortem', 'blameless post-mortem', 'incident', 'user-visible incident' — give good coverage of what a user would actually say; not jargon-only.

3 / 3

Distinctiveness Conflict Risk

Clear niche (blameless post-mortem from incidents) with distinct triggers; unlikely to fire for an unrelated skill, matching the 'clear niche with distinct triggers' anchor. Voice is third person ('produces', 'captures'); no first/second-person penalty applies.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents