Automated summary
Produces a blameless post-mortem of an incident, structured into executive summary, timeline, impact, root cause and action items.
Strengths
- Imposes a complete structure: timeline, key moments, customer and business impact, root cause, what went well and poorly, actions by deadline
- Explicitly separates the root cause from the immediate trigger and asks why the problem was not caught earlier
- Enforces the blameless rule by steering wording toward systems and processes rather than individuals
- Every action gets an owner and a due date, split into immediate and short-term buckets
Limitations
- The skill does not gather or verify facts, so the report is only as good as the details the user supplies
- No guidance on confidentiality, distribution or retention of a document that may contain sensitive details
- The full template is heavy for a minor incident or a lightweight incident review
Use it after an outage, a security incident, a project failure or any event you want to prevent from recurring.
Avoid it when the goal is to assign personal responsibility, or when the facts are not yet established and the analysis would be speculative.
Security analysis
SafeThe skill is a pure prompt/template for structuring a blameless post-mortem. It declares no allowed-tools, makes no bash, network, docker, or filesystem calls, and never asks the agent to read secrets, exfiltrate data, or disable safety mechanisms. The only dynamic element is the standard $ARGUMENTS placeholder for incident details. There is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Write a blameless post-mortem for the March 12 incident: the payment API returned 500s for 45 minutes after the v2.3 deploy, detected by customer support tickets, fixed by rolling back the deploy.Fais un post-mortem sans reproche de la fuite de credentials découverte lundi : un token S3 était exposé dans un dépôt public depuis trois jours, révoqué après alerte d'un chercheur.Our nightly ETL job failed silently for two days and downstream dashboards showed stale numbers — produce a full post-mortem with timeline, root cause, contributing factors and owned action items.name: postmortem description: Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring. user-invocable: true
Blameless Post-Mortem
Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.
Instructions
Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.
Output Format
Executive Summary
Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]
Summary [2-3 sentence overview: what happened, impact, resolution]
Timeline
All times in [timezone].
| Time | Event | Actor | |------|-------|-------| | HH:MM | [What happened] | [Who/what did it] | | HH:MM | [Detection] | [How it was noticed] | | HH:MM | [Response action] | [Who responded] | | HH:MM | [Resolution] | [What fixed it] |
Key Moments
- Trigger: [What initiated the incident]
- Detection: [How/when we knew something was wrong]
- Mitigation: [When bleeding was stopped]
- Resolution: [When fully resolved]
Impact
Customer Impact
- Users affected: [number]
- Duration of impact: [time]
- Symptoms experienced: [what users saw]
Business Impact
- Revenue impact: [if applicable]
- SLA/SLO breach: [yes/no, details]
Root Cause Analysis
Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]
Trigger [The immediate cause—what set things in motion]
Contributing Factors | Factor | How It Contributed | |--------|-------------------| | [factor] | [explanation] |
Why Wasn't This Caught?
- Why didn't tests catch it?
- Why didn't monitoring alert earlier?
What Went Well
| What Worked | Why It Helped | |-------------|---------------| | [thing] | [explanation] |
What Went Poorly
| What Failed | Impact | |-------------|--------| | [thing] | [impact] |
Action Items
Immediate (This week) | Action | Owner | Due | |--------|-------|-----| | [action] | [owner] | [date] |
Short-term (This month) | Action | Owner | Due | |--------|-------|-----| | [action] | [owner] | [date] |
Lessons Learned
- [lesson]
- [lesson]
- [lesson]
Guidelines
- Blameless: "The deploy script didn't validate" not "Alice deployed without checking"
- Thorough timeline: Include everything, even embarrassing delays
- Specific actions: "Add memory alerting" not "Improve monitoring"
- Assigned owners: Unowned actions don't happen
$ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/blameless-post-mortem-analysis-mrx3xy3r/download' --output '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md.part' && mv '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md.part' '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && test -s '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/postmortem' && cp -R '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r' '.claude/skills/postmortem'Cursor
test -f '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && test -s '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/postmortem' && cp -R '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r' '.cursor/skills/postmortem'Codex
test -f '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && test -s '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/postmortem' && cp -R '.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r' '.agents/skills/postmortem'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/blameless-post-mortem-analysis-mrx3xy3r'openskills read 'blameless-post-mortem-analysis-mrx3xy3r'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/blameless-post-mortem-analysis-mrx3xy3r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.