- Home
- Skills
- DevOps & Cloud
- Blameless Postmortem Writer
Blameless Postmortem Writer
Incident postmortem writer: turns your logs, chat, alerts and deploy history into a blameless postmortem with a sourced timeline, impact, contributing factors and action items.
$5
Works with the AI Agents you already use
Blameless Postmortem Writer
Example session with this skill installed
Write a blameless postmortem for the checkout outage on 14 March. Evidence: the deploy log, the alert history and the engineering chat excerpt.
- Read your context and instructions
- Compiled the blameless postmortem writer
Illustrative. The incident and the evidence are invented; this shows the structure and depth the skill produces.
Summary
- A configuration change raised a connection pool size above the database limit, and checkout attempts failed for 31 minutes.
- About 18% of checkout attempts returned errors [INFERRED from the error-rate graph; exact count UNKNOWN].
- Detection came from a customer report, 12 minutes after the first errors; no alert fired.
- Rolling back the configuration fixed it.
- Most important action: alert on database connection saturation and validate pool settings against the database limit before deploy.
Impact
| Item | Value | Tag |
|---|---|---|
| Duration | 14:02 to 14:33 UTC (31 min) | CONFIRMED (deploy log, alert history) |
| Share of checkout attempts failing | about 18% at peak | INFERRED (graph description) |
| Data loss | None found | UNKNOWN (no payment reconciliation in the evidence) |
| Time to detect | 12 min | CONFIRMED (first error 14:02, first report 14:14) |
| Time to mitigate | 17 min after acknowledgement | CONFIRMED |
Timeline (UTC)
| Time | Event | Source | Tag |
|---|---|---|---|
| 13:58 | Configuration change deployed: pool size 40 to 120 per instance | deploy log | CONFIRMED |
| 14:02 | First 5xx responses on the checkout API | alert history | CONFIRMED |
| 14:02 to 14:14 | No alert fires; error rate climbs | alert history | CONFIRMED |
| 14:14 | Support relays a customer report of failed payments | chat | CONFIRMED |
| 14:16 | On-call engineer acknowledges and starts on the application logs | chat | CONFIRMED |
| 14:21 | Database shows "too many connections"; the team suspects traffic | chat | CONFIRMED |
| 14:24 | Traffic comparison shows no unusual volume | chat | CONFIRMED |
| 14:27 | The errors are linked to the 13:58 deploy | chat | CONFIRMED |
| 14:31 | Configuration rolled back | deploy log | CONFIRMED |
| 14:33 | Error rate back to normal | graph description | INFERRED |
Gap: 14:02 to 14:14 has no human action in the evidence. Whether anyone saw the dashboard is UNKNOWN.
Contributing factors
Trigger: pool size per instance (120) times the number of instances exceeded the database connection limit. [INFERRED: instance count and limit are only described as "several" and "a few hundred"]
- Latent condition: nothing in the deploy process compares pool settings with the database limit.
Detection gap: no alert watches connection saturation or the checkout error rate; detection depended on a customer report.
Response gap: the first hypothesis (traffic) was reasonable given the error message and took three minutes to rule out; the deploy history was not on the first dashboard opened.
What went well / badly / lucky
- Well: acknowledgement within two minutes of the report; the rollback was one step.
- Badly: 12 minutes undetected; change history not visible next to the error graph.
- Lucky: it happened in a low-traffic hour.
Action items
| # | Action | Type | Owner role | Priority | Verification |
|---|---|---|---|---|---|
| 1 | Alert when database connections exceed 80% of the limit for 2 minutes | detect | platform on-call lead | P0 | Alert fires in a staging load test |
| 2 | Pre-deploy check comparing pool size times instance count with the database limit | prevent | platform engineer | P1 | The check blocks a test change over the limit |
| 3 | Show recent deploys on the checkout error dashboard | mitigate | observability owner | P1 | Dashboard shows the last 24 hours of deploys |
| 4 | Checkout error-rate alert at 2% for 3 minutes | detect | payments team lead | P0 | Alert fires in a staging fault test |
Open questions
- Exact instance count and database connection limit at the time.
- Whether any payments were captured but not recorded (run the reconciliation report for 14:00 to 14:35).
- Whether anyone saw the error rate between 14:02 and 14:14.
Next steps
- Confirm the open questions with the owners named above.
- Share the draft with the people involved before it is published.
Connects securely to your tools. The creator never sees your data.
About this skill
Write the postmortem your team will actually use. Give it the evidence from an outage or failed release (log excerpts, chat messages, alert history, deploy history, a ticket) and it produces a blameless review: a timeline in one time zone where every row cites its source, the impact with its numbers and how they were obtained, contributing factors instead of a single root cause, what went well, what went badly and where you were lucky, and action items with a type, an owner role, a priority and a way to verify each one.
What makes it different from a generic prompt: every statement is tagged CONFIRMED, INFERRED or UNKNOWN, so gaps are shown instead of filled with guesses. The wording is checked for blame (names, "failed to", "human error"). It computes time to detect, acknowledge, mitigate and resolve when the evidence allows, and it turns vague actions like "improve monitoring" into measurable ones. It also covers thin evidence, conflicting timestamps and a separate customer-facing summary.
What it reads and does: it works only from the evidence you paste or point it to. It runs no scripts and no commands, makes no network connection and contacts no one.
Honest limits: it cannot verify your evidence, and the result is only as good as what you give it. It is not for live incident response, for deciding fault, or for legal or compliance statements.
Works only from the evidence you give it and cannot verify that evidence. Not for live incident response, for deciding fault, or for legal or compliance statements. Quality depends on the quality of the logs, chat and timestamps provided.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
Requires
Permissions
File Scopes
A prompt-only skill (SKILL.md). It reads only the evidence you paste or name; it runs no commands, makes no network connection and reads no environment variables.