incident-postmortem-writer
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Security
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: incident-postmortem-writer
description: Turn incident timelines, logs, tickets, and chat snippets into a clear postmortem covering impac…
category: security
runtime: no special runtime
---
# incident-postmortem-writer output preview
## PART A: Task fit
- Use case: Turn incident timelines, logs, tickets, and chat snippets into a clear postmortem covering impact, detection, root cause, contributing factors, remediation items, and prevention steps. Use after outages, degraded service events, or security incidents..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Turn incident timelines, logs, tickets, and chat snippets into a clear postmortem covering impact, detection, root cause, contributing factors, remediation items, and prevention steps. Use after outages, degraded service events, or security incidents.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: incident-postmortem-writer
description: Turn incident timelines, logs, tickets, and chat snippets into a clear postmortem covering impac…
category: security
source: 00PrabalK00/claude-skills
---
# incident-postmortem-writer
## When to use
- Turn incident timelines, logs, tickets, and chat snippets into a clear postmortem covering impact, detection, root cau…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "incident-postmortem-writer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Incident Postmortem Writer
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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review