- Home
- Skills
- DevOps & Cloud
- incident postmortem Skill Pro
Works with the AI Agents you already use
incident postmortem Skill Pro
Create structured, blameless SRE postmortems from incident logs, chat notes, and deployment records.
$5
incident postmortem Skill Pro
Example session with this skill installed
Generate a postmortem for a 30-minute API outage on 2024-10-12. Deployment v2.4.1 went live at 14:00 UTC. At 14:05, Error rates hit 45%. Rollback initiated at 14:25. Resolved by 14:35.
- Read your context and instructions
- Compiled the incident postmortem pro
I have processed the incident evidence for the API outage on 2024-10-12. The following report synthesizes the timeline and provides a blameless analysis of the deployment failure.
Incident Postmortem: API High Error Rate (v2.4.1 Deployment)
1. Executive Summary
A 30-minute service disruption occurred following deployment v2.4.1, causing a 45% error rate for all authenticated API requests. Recovery was achieved through a manual rollback to v2.4.0.
2. Incident Details
- Date and timezone: 2024-10-12 (UTC)
- Service/system: Core API Gateway
- Severity: SEV-1
- Evidence reviewed: Deployment logs, incident description
3. Customer and Business Impact
Approximately 45% of users experienced 5xx errors. Impact lasted from 14:05 to 14:35 UTC.
4. Timeline
| Time (UTC) | Event | Evidence/source | Confidence |
|---|---|---|---|
| 14:00 | Deployment v2.4.1 started | CI/CD Logs | Verified |
| 14:05 | Error rates spiked to 45% | Monitoring Alert | Verified |
| 14:25 | Rollback to v2.4.0 initiated | Operator Observation | Verified |
| 14:35 | Error rates normalized | Dashboard | Verified |
5. Root Cause Analysis
- Trigger: Automated deployment of version 2.4.1.
Technical failure: The new container image lacked the required environment variable for database connection pooling.
Root cause: CI/CD pipeline does not validate environment variable presence against the target schema before swapping traffic.
- Detection gaps: 5-minute delay between impact start and operator intervention.
6. Corrective Action Items
| ID | Action | Rationale | Priority | Owner | Verification | Status |
|---|---|---|---|---|---|---|
| 1 | Add env-var validation to CI | Prevents misconfigured deploys | P0 | Platform Team | Test build failure | Open |
| 2 | Implement canary releases | Limit impact scope of failures | P1 | SRE | 10% traffic test | Open |
Next steps
- Assign owners to the P0 validation task.
- Investigate why the 14:05 alert didn't trigger an automatic rollback.
- Review the database connection pool settings for current production.
Connects securely to your tools. The creator never sees your data.
About this skill
Raw incident logs and frantic Slack threads are poor sources for long-term learning. This skill acts as an SRE facilitator to turn messy event data into structured, blameless postmortems.
What it does
- Evidence synthesis extracts facts from logs, alerts, deployment records, and chat history.
- Blameless analysis focuses on system failures and process gaps rather than individual human error.
- Timeline construction generates a chronological table of events with evidence-based confidence levels.
- Root cause mapping distinguishes between triggers, technical failures, and deep contributing factors.
- Action item tracking generates prioritized, verifiable tasks to prevent recurrence.
How it works
- Provide the agent with incident evidence including timestamps, logs, and stakeholder observations.
- The agent identifies gaps in the narrative and requests missing essential details.
- It classifies statements as verified, inferred, or unknown to maintain a high bar for evidence.
- The agent generates a 10-section report including impact analysis, 5-Whys reasoning, and a response review.
Frameworks & tools
This skill is designed for Site Reliability Engineering (SRE) workflows and works with inputs from monitoring tools, incident management platforms, and version control logs. It follows standard industry postmortem formats used by high-velocity DevOps teams.
Why this beats prompting it yourself
Prompting an LLM for a postmortem often results in hallucinated timestamps or "human error" conclusions. This skill enforces a strict evidence-confidence model and a causal chain analysis that prevents the model from settling on the first visible failure.
Use cases
- Drafting official incident reports for stakeholders after a service outage.
- Conducting "5 Whys" deep dives into recurring technical debt.
- Reviewing response effectiveness to improve on-call runbooks.
- Summarizing multi-channel incident threads into a single source of truth.
Known limitations
Does not integrate directly with Jira or PagerDuty APIs to create tickets. It cannot verify if a remediation is actually deployed unless the evidence is provided in the input text.
Cannot auto-fetch logs from cloud providers; requires manual input of evidence. Does not directly create GitHub issues or Jira tickets.
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 18 days ago
Permissions
No special permissions declared or detected