CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/post-mortem-author

Use for any question or task about incident post-mortems or incident reviews, including how to write a blameless one or reviews that keep turning into blame: a sourced timeline, root cause (what and why, not who), impact on users, revenue and SLOs, action items with owners, dates and success criteria, and what went well.

Quality

91%

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%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.

A highly actionable, well-sequenced skill: concrete rewrites, a required-field checklist for action items, a complete worked example, and a clean one-level reference split. The one weakness is token efficiency — it quotes Google SRE's basic postmortem definitions that Claude already knows and repeats the blameless rule several times.

Suggestions

Cut the three opening block quotes that define what a postmortem is ('a written record of an incident...', 'tenet of SRE culture', 'not punishment'); keep only the load-bearing quote about focusing on contributing causes without indicting individuals.

State the blameless principle once (e.g., in a short 'Principles' note) and have Step 2, the root-cause guidance, and the anti-patterns table reference it rather than each restating it.

Trim the Overview's trigger list to the single Google SRE quote or fold it into 'When to use' as a one-line summary, since Claude can be trusted to know common postmortem triggers.

DimensionReasoningScore

Conciseness

The body leans on three block quotes of Google SRE defining what a postmortem is ('a written record of an incident...', 'Blameless postmortems are a tenet of SRE culture', 'not punishment - it is a learning opportunity') — concepts Claude already knows — and the blameless rule is restated in the description, Step 2, the root-cause guidance, and the anti-patterns table. The actionable material itself is tight, so this is over-explanation to trim rather than pervasive padding.

3 / 5

Actionability

Fully concrete, copy-paste-ready instruction guidance: named skeleton sections with per-section content rules, before/after blame-language rewrites ('Bob deployed without testing' → 'The pre-deploy testing didn't cover the null-metadata case'), four required action-item fields with anti-examples, an explicit storage directory layout, and a complete filled SEV-2 worked example. For an instruction-only skill this covers the common cases end to end.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced (author → blameless review → action-item discipline → approval/closure → storage) with explicit validation gates: Step 2 is a reviewer checklist with a reject-and-rewrite feedback loop for blame language, and Step 4 defines sign-off requirements plus an explicit closure criterion ('closed when all action items ship'). Not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

The single bundle file, references/post-mortem-document-template.md (verified to exist), is clearly signaled with a markdown link in Step 1 and is one level deep; the body summarizes the 9-section skeleton inline while the full copyable template lives in the reference. The worked example is appropriately inline as the core demonstration, and navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

92%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: it combines an explicit 'Use for' trigger clause with a comprehensive, specific inventory of what the skill produces, including a distinctive blameless-review angle. The only gap is missing common synonyms such as 'retrospective' or 'postmortem' that users might naturally say.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — 'a sourced timeline', 'root cause (what and why, not who)', 'impact on users, revenue and SLOs', 'action items with owners, dates and success criteria', 'what went well' — giving comprehensive coverage of the skill's capabilities. It exceeds the 'minor gaps' level because both authoring ('how to write a blameless one') and the concrete document components are all named.

5 / 5

Completeness

Explicitly answers both questions: 'Use for any question or task about incident post-mortems or incident reviews...' (when, with concrete trigger phrasing including the blame-scenario variation) and the enumerated list of document components (what). The explicit trigger clause means the completeness cap does not apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: 'incident post-mortems', 'incident reviews', 'blameless', and 'reviews that keep turning into blame'. Falls short of comprehensive because common synonyms like 'retrospective', 'retro', or the one-word 'postmortem' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche — authoring the written post-mortem artifact and running blameless reviews — distinct from adjacent skills like incident response or on-call operations. 'Blameless' and 'reviews that keep turning into blame' are distinctive triggers with minimal conflict risk.

5 / 5

Total

19

/

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.

Reviewed

On this page