incident-postmortem
Facilitates incident reporting by drafting postmortems focused on root cause analysis.
Install
mkdir -p .claude/skills/incident-postmortem && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13362" && unzip -o skill.zip -d .claude/skills/incident-postmortem && rm skill.zipInstalls to .claude/skills/incident-postmortem
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.Key capabilities
- →Draft an incident postmortem with a timeline.
- →Identify root causes and contributing factors.
- →Define corrective and preventive actions.
- →Focus on systemic causes over blame.
- →Assign owners and due dates for actions.
How it works
This skill drafts an incident postmortem by building a timeline from evidence, identifying root causes, and defining corrective actions, while focusing on systemic improvements.
Inputs & outputs
When to use incident-postmortem
- →Documenting production outages
- →Performing root cause analysis
- →Managing incident remediation
About this skill
Incident Postmortem
Purpose
Draft an incident postmortem with timeline, RCA, and action items.
Inputs to request
- Incident timeline and impact.
- Logs, alerts, and change history.
- Mitigations taken and outcomes.
Workflow
- Build a clear incident timeline from evidence.
- Identify root causes and contributing factors.
- Define corrective and preventive actions.
Output
- Postmortem draft with action items.
Quality bar
- Focus on systemic causes over blame.
- Assign owners and due dates for actions.
When not to use it
- →When the task is not to draft an incident postmortem.
- →When the task does not require a structured post-incident report.
- →When the task involves assigning blame rather than focusing on systemic causes.
Limitations
- →It requires inputs such as incident timeline, logs, alerts, and change history.
- →It focuses on systemic causes over individual blame.
- →It requires assigning owners and due dates for actions.
How it compares
This skill provides a structured, systemic approach to postmortem generation with a focus on actionable items and root cause analysis, unlike an unstructured report that might lack clear actions or blame individuals.
Compared to similar skills
incident-postmortem side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| incident-postmortem (this skill) | 0 | 5mo | No flags | Intermediate |
| equilateral-agents | 5 | 9mo | No flags | Intermediate |
| logging-observability | 3 | 6mo | No flags | Intermediate |
| opentelemetry-instrumentation-extension | 3 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by spideynolove
View all by spideynolove →You might also like
equilateral-agents
Equilateral-AI
22 production-ready AI agents with database-driven orchestration for security reviews, code quality analysis, deployment validation, infrastructure checks, and compliance. Auto-activates for security concerns, deployment tasks, code reviews, quality checks, and compliance questions. Includes upgrade paths to enterprise features (GDPR, HIPAA, multi-account AWS, ML-based optimization).
logging-observability
getsentry
Review code for correct logging and error handling patterns. Use when reviewing code that handles errors, uses logging functions, or captures exceptions. Enforces the error hierarchy where 4xx errors are never logged to Sentry and 5xx errors always are. Trigger phrases include "review logging", "check error handling", "audit observability", or verify correct use of logIssue vs logError.
opentelemetry-instrumentation-extension
docker
Extend OpenTelemetry instrumentation when new functionality is added to the MCP Gateway. Use when (1) new operations/functions are added, (2) reviewing code for missing instrumentation, (3) user requests otel/telemetry additions, or (4) working with state-changing operations. Analyzes git diff, suggests instrumentation points following project standards in docs/telemetry/README.md, implements with approval, writes tests, updates documentation, and verifies with debug logging and docker logs.
incident-response-smart-fix
sickn33
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res
analytics-developer
anyproto
Context-aware routing to the Anytype iOS analytics system. Use when adding analytics events, tracking user routes, or working with AnytypeAnalytics and AnalyticsConstants.
ark-vulnerability-fixer
mckinsey
CVE research and security patch workflow for Ark. Provides CVE API integration, mitigation strategies, and security-focused PR templates. Works with research, analysis, and setup skills for comprehensive vulnerability fixing.