incident postmortem writer
- Repo stars 1
- Author repo claude-skills
- Domain
- Security
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Incident Postmortem Writer
## Overview
Write postmortems that improve systems, not narratives that assign blame.
## Core Workflow
1. Build a factual timeline from logs, alerts, tickets, and communications.
2. Quantify impact, affected users, duration, and detection quality.
3. Identify the triggering cause, contributing factors, and why safeguards did not stop the incident.
4. Convert remediation into clear action items with owners, priority, and prevention intent when possible.
5. Write the final document in a blameless tone with facts separated from inference.
## Deliver
- Include a short executive summary before the detailed timeline.
- Make the distinction between root cause and contributing conditions explicit.
- End with concrete preventive actions instead of vague lessons learned.
## Guardrails
- Do not hide uncertainty; mark missing evidence clearly.
- Avoid naming individuals as the cause.
- Keep the document useful for both technical and operational follow-up.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Write postmortems that improve systems, not narratives that assign blame. · 1. Build a factual timeline from logs, alerts, tickets, and communications. · - Include a short executive summary before the detailed timeline. · - Do not hide uncertainty; mark missing evidence clearly.
files/cmd -> no explicit files or commands
body sha256 -> 9808da817cb8
Overview
Write postmortems that improve systems, not narratives that assign blame.
Core Workflow
Build a factual timeline from logs, alerts, tickets, and communications. Quantify impact, affected users, duration, and detection quality. Identify the triggering cause, contributing factors, and why safeguards did not stop the incident. Convert remediation into clear action items with owners, priority, and prevention intent when possible. Write the final document in a blameless tone with facts separated from inference.
Deliver
Include a short executive summary before the detailed timeline. Make the distinction between root cause and contributing conditions explicit. End with concrete preventive actions instead of vague lessons learned.
Guardrails
Do not hide uncertainty; mark missing evidence clearly. Avoid naming individuals as the cause. Keep the document useful for both technical and operational follow-up.