incident-postmortem

Name: incident-postmortem
Availability: InStock
Author: lkb-99

Collect logs, metrics, alerts, and communications into structured Markdown post-mortem reports.

Updated Aug 27, 2026

Search Tags:#timeline #reporting #postmortem #sre #root-cause-analysis #blameless #incident-analysis

Ready to run

npx skills add https://github.com/LKB-99/manus-auto-skills --skill incident-postmortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/LKB-99/manus-auto-skills/tree/main/incident-postmortem
Command: npx skills add https://github.com/LKB-99/manus-auto-skills --skill incident-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct a structured, blameless post-mortem framework that collects incident data, timelines, root-cause analysis, and action items to drive learning and reliability.

Core Features & Use Cases

Data collection: gather logs, metrics, alerts, and team communications to build a complete incident narrative.
RCA & Timeline: create an accurate sequence of events and root-cause analysis using methods like 5 Whys or Ishikawa.
Reporting & Action: generate a shareable post-mortem report with defined owners and due dates to prevent recurrence.
Use Case: After a service outage, run a post-mortem to identify root causes and define corrective actions.

Quick Start

Create a new directory named post-mortem-YYYY-MM-DD-incident and start filling the provided Markdown template with timeline, root-cause analysis, and action items.

Frequently Asked Questions about incident-postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I conduct a blameless incident post-mortem after a service outage?▼

To conduct a blameless incident post-mortem, gather logs, metrics, alerts, and team communications to build a complete narrative, then use structured Markdown templates to document timelines, root-cause analysis, and action items.

What root-cause analysis techniques can I use for incident reporting?▼

For incident reporting and root-cause analysis, you can apply the 5 Whys or Ishikawa methods to identify underlying causes, ensuring the post-mortem remains blameless and focused on systemic reliability improvements.

How do I build an incident timeline from logs and metrics?▼

Build an incident timeline by collecting data from dashboards, logs, and collaboration artifacts, then mapping these events chronologically into a structured template to create an accurate sequence of the outage.

Can I use this post-mortem framework for security incidents and performance degradation?▼

Yes, this structured post-mortem framework applies to service outages, security incidents, performance degradation, and major incidents, guiding data collection, timeline construction, RCA, and reporting across these scenarios.

What is the best way to track action items and owners after an incident post-mortem?▼

The best way to track action items after an incident post-mortem is to generate a shareable report using a structured template that defines specific owners and due dates for each corrective action to prevent recurrence.