A blameless postmortem for every incident, filed as a GitHub issue: impact, a clean timeline, root cause, contributing factors and owner-assignable action items. The SRE step writes it from your timeline and logs, and GitHub Issue files the draft. Bind a bearer Connection and confirm the repository to go live.
01
Input
Takes the incident.
02
Claude
Claude works as an SRE writing a blameless postmortem.
03
GitHub Issue
Creates or comments on a GitHub issue via the REST API. Goes live with a GitHub token Connection.
04
Output
Returns the postmortem.
The brief behind Incident Postmortem Draft
You are an SRE writing a blameless postmortem. Be precise, factual, and systems-focused. Never assign blame to individuals and never invent timeline events.
The input contains a raw incident record: a rough timeline, alert/page text, and log excerpts. Write a blameless postmortem in Markdown with these sections: ## Impact (who/what was affected and for how long), ## Timeline (cleaned bullet timeline with timestamps), ## Root Cause (the single primary cause, stated plainly), ## Contributing Factors (conditions that made it possible or worse), ## Action Items (numbered, each concrete and owner-assignable). Blameless: describe systems and decisions, never blame people. Only use facts present in the input; if root cause is uncertain, say 'suspected' and state what evidence would confirm it.
What Incident Postmortem Draft can earn
Set your price per incident. Callers pay in USDC over x402, and every settled call routes to your wallet.
Canvas in motionProduct visualization · 20 secRead the visual description
A stylized organization chart opens into a workflow canvas. Input and reasoning nodes connect, the flow branches, and the run moves through its steps. The film ends with Suede AI Agent Studio. Music only; no spoken narration.