postmortem

Generate structured HTML incident postmortems with JSON data backups.

4|2|Updated Apr 26, 2026

Search Tags:#documentation #reporting #postmortem #incident #blameless #outage

Ready to run

npx skills add https://github.com/IsNoobgrammer/skills-for-agents --skill postmortem-isnoobgrammer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/IsNoobgrammer/skills-for-agents/tree/main/skills/postmortem
Command: npx skills add https://github.com/IsNoobgrammer/skills-for-agents --skill postmortem-isnoobgrammer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent, emotionally charged, or skipped incident documentation by enforcing a structured, blameless, and visually professional reporting workflow.

Core Features & Use Cases

Automated Reporting: Generates a complete, self-contained HTML incident dashboard including timelines, 5 Whys analysis, and action items.
Visual Data Representation: Automatically creates charts for error rates and impact, and renders cascading cards for root cause analysis.
Use Case: After a production outage, use this skill to quickly gather incident details and generate a polished, shareable report that focuses on system improvements rather than individual blame.

Quick Start

Invoke the postmortem skill to begin documenting the recent production incident and generate the required report files.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I create a blameless postmortem report after a production outage?▼

To create a blameless postmortem report after an outage, you need a standardized template that structures timelines, root cause analysis, and action items. This approach enforces a consistent, visually professional reporting workflow focused on system improvements rather than individual blame.

What is the best way to document incident timelines and 5 Whys root cause analysis?▼

Documenting incident timelines and 5 Whys root cause analysis is best handled by enforcing a structured reporting template. This standardizes the creation of incident postmortems, ensuring consistent data capture for timelines and cascading root cause cards.

Can I generate HTML incident dashboards with automated charts for error rates?▼

Yes, you can generate HTML incident dashboards with automated charts for error rates. The reporting workflow automatically creates visual data representations for impact and error rates while rendering a complete, self-contained HTML dashboard.

Does generating incident postmortem reports require local file system access?▼

Generating incident postmortem reports does require local file system access. This access is necessary to manage incident directories, store JSON data backups, and configure gitignore files for the generated HTML reports and associated assets.

How do I track action items consistently across multiple incident reviews?▼

To track action items consistently across multiple incident reviews, you should enforce a standardized postmortem template. This ensures action item tracking is structurally integrated into the generated HTML reports and JSON data backups for every incident.