incident-postmortem-template
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill incident-postmortem-templateIncident Postmortem Template - Auto-activating skill for Technical Documentation. Triggers on: incident postmortem template, incident postmortem template Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just naming the skill without explaining its capabilities or providing meaningful selection guidance. It lacks concrete actions, has redundant and narrow trigger terms, and provides no explicit 'Use when' clause. The only slight positive is that 'incident postmortem' is a somewhat specific domain term.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates structured incident postmortem documents including timeline, root cause analysis, impact assessment, and action items.'
Add an explicit 'Use when...' clause with varied trigger scenarios, e.g., 'Use when the user needs to document an outage, create a post-incident review, write an RCA report, or analyze service failures.'
Expand trigger terms to include natural variations: 'incident report', 'outage postmortem', 'RCA', 'root cause analysis', 'post-incident review', 'service failure analysis'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Incident Postmortem Template') but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'generates', 'creates', 'structures', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' is only implied through repetitive trigger terms. There is no explicit 'Use when...' clause or meaningful guidance on when to select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('incident postmortem template' listed twice) and extremely narrow. Missing natural variations users might say like 'post-incident review', 'outage report', 'incident analysis', 'RCA template', 'root cause analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'incident postmortem' is fairly specific to a particular document type, which provides some distinctiveness. However, it could overlap with other technical documentation or template-related skills due to the vague description. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely meta-content describing what the skill supposedly does without providing any actual incident postmortem template or guidance. It contains zero actionable information - no template structure, no example sections (timeline, impact, root cause, action items), and no concrete instructions for creating postmortems.
Suggestions
Replace the entire content with an actual incident postmortem template showing required sections (Summary, Timeline, Impact, Root Cause, Action Items, Lessons Learned)
Add a concrete example of a filled-out postmortem or at minimum show the expected format for each section
Include a brief workflow: 1) Gather timeline facts, 2) Identify root cause, 3) Document impact metrics, 4) Define action items with owners
Remove all meta-description ('This skill provides...', 'When to Use...') and replace with the actual template content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about incident postmortems. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no template structure, no example sections, no actual postmortem format. The skill describes what it does rather than providing any executable or usable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. For a postmortem template skill, there should be clear sections (timeline, root cause, action items, etc.) or a step-by-step process for creating one. None exists. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual template content, no references to detailed materials, and no structured navigation to useful resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.