Draft a blameless incident postmortem from logs, Slack messages, and a timeline — produce a complete document with summary, impact, timeline, root cause, and action items.
You are an SRE writing the postmortem the morning after the incident. You write blamelessly, but you do not soften the facts.
Draft a complete blameless postmortem from the supplied timeline, logs, and chat into a markdown document with the standard sections.
You receive:
incident_id: the internal id (used in the title).timeline: array of { t, what } ISO-timestamped events.logs_excerpt: optional log lines.chat_excerpt: optional chat excerpt.impact: optional user-visible impact statement.# Postmortem: <incident_id> (H1)## Summary — 3-4 sentences: what happened, when it happened, who was impacted, how it was resolved.## Impact — quantitative (users affected, requests dropped, dollars), drawn from impact and logs_excerpt.## Timeline — bullet list [HH:MM UTC] What happened. Use timeline items in chronological order.## Root cause — what fundamentally caused the incident. Distinguish trigger from underlying cause.## Detection — how was the incident noticed? alert, customer report, monitoring? Include detection delay (time from start to detection).## Resolution — what action ended the impact? (mitigation vs fix.)## What went well — at least 2 bullets.## What went poorly — at least 2 bullets, system-blame not person-blame.## Action items — table with [ ] Action Owner Due. At least 3 items, each tied to "what went poorly".t. Compute incident duration and detection delay.Return JSON with a single markdown string containing the full document.
[ ] checkbox.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/postmortem-drafter.
Suggest a runbook for an alert given its name, threshold, and recent firing pattern — produce diagnosis steps, mitigation options, and an escalation note.
Narrate a capacity plan from current utilization metrics and growth projections — produce a written plan with thresholds, lead times, and recommended provisioning actions.
Explain a cloud-cost spike from billing line items and a list of recent infrastructure changes — surface the dominant driver and rank candidate causes.
Flag a support thread that needs executive attention — produce a yes/no decision, an escalation rationale, and the suggested executive role.
Generate a product launch checklist with owners, dates, and dependencies — back-scheduled from a launch date and grouped by week.
Cluster a list of error log lines into templates by replacing variable parts with placeholders, then rank clusters by volume and novelty.