🚨Agent
Incident post-mortem
Compiles a blameless post-mortem from Sentry, PagerDuty, GitHub, and Slack — timeline to action items.
- Surfaces
- agent · skill · mcp
- Complexity
- advanced
- Trigger
- natural
- Est. tokens
- 18,000
- Requires MCP
- sentry, github, slack
What It Does
Multi-source incident reconstruction. Pulls PagerDuty timing and responders, Sentry events in that window, GitHub PRs merged near the incident, and Slack messages from the incident channel. Produces a blameless post-mortem following a stored template and opens action-item issues.
When It Triggers
- ▸"Write the post-mortem for incident INC-1234"
- ▸"Document what happened during yesterday's outage"
- ▸"Compile the post-mortem for the email-delivery incident"
SKILL.md
markdown
---
name: incident-postmortem
description: Compiles an incident post-mortem from Sentry, PagerDuty, GitHub, and Slack sources. Produces a blameless write-up with timeline, root cause, action items. Use when user says "write post-mortem for incident X", or "document what happened".
---
# Incident Post-mortem
## Requires
- Sentry MCP, PagerDuty MCP (optional), GitHub MCP, Slack MCP
## Phases
### Phase 1: Collect
1. Incident ID → PagerDuty for start/end times, responders
2. Sentry events in that time window → affected users, stack traces
3. GitHub: PRs merged ±6h of incident start
4. Slack: messages in #incidents channel for human timeline
### Phase 2: Analyze
- Timeline: minute-by-minute
- Trigger: the event that caused impact
- Root cause: why the trigger had the effect it did
- Contributing factors: things that made it worse
### Phase 3: Write
- Use the blameless template in `references/postmortem.md`
- Action items with owner + target date
- Open issues for each action item via `github_createIssue`
references/postmortem.md
markdown
# Blameless Post-mortem Template
## Summary
One paragraph. What happened, impact, how long.
## Timeline
Bullet list of minute-precision events.
## Root Cause
Not "who" — "why". The technical and process-level reasons.
## Action Items
- [ ] Owner — item — due date
Gotchas
- ▸Blameless means the write-up focuses on "why", not "who" — scrub names from the draft.
- ▸Action items without an owner and date are worthless — the skill should refuse to finalize until both are set.
- ▸Sensitive incidents: keep the draft in a private repo or restricted Drive folder.