Postmortem Report Writer
Generate blameless postmortem reports following Google SRE culture
by myriadprotocolTechnology & SoftwareEngineeringSite Reliability Engineer (standalone)Incident ManagementWhat You Can Do
You can convert raw incident information—timelines, logs, metrics, and witness accounts—into professional postmortem reports that follow Google SRE blameless culture principles. The skill structures complex incidents into clear narratives covering what happened, why it happened, impact analysis, and actionable follow-up items, enabling your team to learn from failures and prevent recurrence.
Features
frames incidents as systemic failures, not individual mistakes
organizes events chronologically with exact timestamps and decision points
documents customer-facing and internal effects with metrics
identifies underlying causes using 5-why methodology or equivalent
surfaces process gaps, monitoring blind spots, and design limitations
generates specific, trackable remediation items with owners and deadlines
follows industry-standard postmortem structure and cultural guidelines
produces polished documents suitable for leadership review and team discussion
Example Output
Example 1: Database Failover Incident
Incident Title: Primary Database Failover Delay (45-minute customer impact)
Timeline:
- 14:22 UTC: Disk IO saturation on primary database detected
- 14:24 UTC: Automated health checks fail; failover initiated
- 14:28 UTC: Secondary replica promoted; DNS update propagation begins
- 14:67 UTC: 95% of traffic restored; final clients reconnect
Root Cause: Monitoring thresholds set too high to catch IO saturation early. Failover runbook was undocumented, causing 3-minute delay in decision-making.
Contributing Factors: No load testing in 6 months; cache invalidation strategy created unexpected query surge; secondary replica 45 seconds behind primary.
Follow-ups:
- Implement predictive IO monitoring with earlier alerts (Owner: Platform team, Due: 2 weeks)
- Automate failover decision at 80% IO utilization (Owner: SRE, Due: 3 weeks)
Example 2: API Rate Limiting Bug
Incident Title: Unintended 429 errors for legitimate traffic (72-minute outage)
Root Cause: Rate limiter configuration deployed with typo: per-user limits applied per-IP instead. Legitimate traffic from shared NAT hit limits immediately.
Contributing Factors: Rate limiter change deployed without load test; no staging environment matches production traffic patterns; missing validation in deployment pipeline.
Follow-ups:
- Add integration tests for rate limiter edge cases (Owner: Backend team)
- Require load test sign-off for traffic-facing changes (Owner: Release mgmt)
What's Included
- SKILL.md instruction file with blameless culture principles and incident severity guidelines:
- Postmortem template covering timeline, impact, root cause, contributing factors, and follow-ups:
- Blameless writing checklist to catch blame language and reframe incidents systemically:
- 5-Why analysis framework to dig deeper into root causes:
- Follow-up action tracker with ownership, severity, and deadline fields:
Who It's For
- SRE/DevOps Engineers — leading incident response and postmortem writing
- Engineering Managers — reviewing postmortems and driving follow-up actions
- Technical Leads — documenting incidents and building institutional knowledge
- On-call Responders — capturing incident details immediately after resolution
- Quality/Process Leads — tracking systemic improvements across incidents
Best For
- Production incidents causing customer-facing downtime or data impact (>15 min)
- Near-misses that could have caused major incidents without detection
- Process failures requiring organizational learning and systemic change
- Recurring incidents with similar root causes across different teams
- High-complexity incidents involving multiple systems, teams, or contributing factors
You might also like
You get Claude to analyze your API specifications and automatically generate bulletproof parameter validation logic. Claude creates security-hardened middleware, enforces type constraints, detects malicious input patterns, and generates comprehensive error handling — all tailored to your framework and existing codebase. The result is production-ready validation code with zero unvalidated inputs reaching your business logic.
This skill enables you to automatically audit your websites against compliance standards and detect deviations from expected baselines. You can track regulatory requirements, identify policy violations, and generate compliance reports with actionable remediation steps. Monitor multiple sites simultaneously and maintain detailed audit trails for compliance documentation.
Transform schema and data changes into production-ready migration packages that protect data integrity and minimize downtime. You can handle column additions, renames, type conversions, and backfills using proven patterns like expand-contract and shadow tables. The skill generates explicit rollback scripts, validation checklists, and phased execution plans that keep applications stable throughout the migration.
You'll transform high-level feature requirements into a complete development plan covering API design, frontend implementation, testing strategy, and documentation. The skill helps you identify dependencies, parallelize work across frontend and backend teams, and establish quality gates that ensure features ship bug-free with proper error handling and logging.
You can conduct comprehensive toxicology safety assessments, generate regulatory-compliant safety documentation, and produce detailed hazard analyses for pharmaceutical and chemical submissions. This skill structures toxicological data into standardized safety reports, maps findings to regulatory guidelines (FDA, EMA, ICH), and identifies risk characterization strategies to support regulatory submissions and approval timelines.
You can submit your Solidity smart contracts for comprehensive security analysis, vulnerability detection, and gas optimization recommendations. Claude reviews your code against known attack vectors, design patterns, and best practices—identifying reentrancy risks, overflow/underflow issues, access control flaws, and inefficient operations. You receive actionable fix recommendations with explanations of the security implications and gas savings potential.
You can design end-to-end NGS pipelines tailored to your experiment type (WGS, WES, RNA-seq, targeted), troubleshoot pipeline failures by analyzing QC metrics and logs, and optimize performance by fine-tuning parameters and identifying bottlenecks. This skill handles the full workflow from raw sequencing data quality assessment through variant interpretation and annotation.
You can accelerate your entire antenna design workflow—from initial concept to optimized specifications—by leveraging Claude's knowledge of electromagnetic theory, antenna types, and design trade-offs. Claude helps you parameterize designs, identify optimal configurations for your frequency band and application, and prepare detailed briefs for simulation and manufacturing. You'll generate design reviews, impedance-matching solutions, and validation checklists without context-switching to multiple tools.