What is a blameless postmortem?

A blameless postmortem is a process of analyzing a technical incident to understand its systemic causes without assigning fault to individuals, fostering a culture of honesty, psychological safety, and continuous improvement.

What are the key components of an incident report generated by this skill?

Reports include a high-level summary, a detailed chronological timeline, root cause analysis (RCA), impact assessment, resolution steps, and a list of SMART action items.

How does this skill improve system reliability?

By identifying multiple contributing factors and systemic weaknesses rather than stopping at 'human error,' the skill helps you generate actionable improvements that prevent entire classes of future failures.

When should I use this Claude Code skill?

Use this skill immediately after resolving a production outage, security incident, or major bug. It is most effective when technical details are fresh but the immediate crisis has passed.

Blameless Postmortems & Incident Analysis

Name: Blameless Postmortems & Incident Analysis
Author: lev-os

bylev-os

0•

배포 및 DevOps

Conducts systematic incident analysis focusing on systemic causes rather than individual actions to prevent recurrence and build a culture of reliability.

This skill provides a comprehensive framework for performing blameless postmortems following production outages, security breaches, or major bugs. Based on industry-leading SRE practices from Google and Etsy, it guides users through creating structured documentation, including chronological timelines, multi-factor root cause analysis, and prioritized action items. By emphasizing 'how' systems failed over 'who' made a mistake, this skill helps engineering teams foster psychological safety and transform technical failures into long-term organizational learning and improved system resilience.

주요 기능

01Chronological timeline construction with UTC synchronization

020 GitHub stars

03Action item prioritization and tracking frameworks

04Blameless communication and questioning techniques

05Structured templates for comprehensive incident documentation

06Guidance for 'Five Whys' and systemic root cause analysis

사용 사례

01Analyzing production service outages or performance degradation

02Investigating security incidents and data breaches

03Facilitating team retrospectives after major software delivery failures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lev-os/agents blameless-postmortems

For use in Claude.ai and ChatGPT

Download Skill