postmortem-author

Generate Sunkworks-style postmortem reports from Kubernetes incident data.

4|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/kingdon/skills --skill postmortem-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-author
Source: https://github.com/kingdon/skills/tree/main/.github/skills/postmortem-author
Command: npx skills add https://github.com/kingdon/skills --skill postmortem-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Post-Mortem Author helps teams generate transparent, structured post-mortems from live debugging sessions, preserving a narrative of events, decisions, and recovery steps.

Core Features & Use Cases

  • Automated timeline reconstruction from Kubernetes events and deployment histories.
  • Structured post-mortem templates with recovery playbooks, lessons learned, and episode notes for live streams.
  • Use cases include incident post-mortems, reliability reviews, and knowledge sharing across engineering teams.

Quick Start

After an outage, trigger the /postmortem slash command to generate a new report. The example below shows how to collect, structure, and share incident findings.

Frequently Asked Questions about postmortem-author

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

FAQPage Schema
How do I generate a Kubernetes incident post-mortem from live debugging data?

Kubernetes incident post-mortems reconstruct timelines and identify failure patterns by gathering events via kubectl. The generated report includes recovery playbooks and lessons learned for engineering teams.

What is included in a structured post-mortem report for outage analysis?

A structured post-mortem report includes reconstructed event timelines, identified failure patterns, recovery playbooks, and lessons learned to preserve the narrative of decisions and recovery steps.

Does this postmortem generation workflow require any specific dependencies or platforms?

This workflow requires a Kubernetes environment to gather events via kubectl and relies on standard Unix tools, using a Bash-driven process without external software dependencies.

How do I automate timeline reconstruction for a Kubernetes outage?

Automate timeline reconstruction by executing a Bash script that collects deployment histories and cluster events via kubectl, structuring them into a chronological incident narrative.

Can I use standard Unix tools to build incident recovery playbooks?

Yes, you can build incident recovery playbooks using a Bash-driven workflow compatible with standard Unix tools, processing collected Kubernetes events to document structured recovery steps.

When should I generate a post-mortem report after an incident?

Generate a post-mortem report immediately after resolving an outage to capture live debugging data, document the timeline, and structure incident findings for reliability reviews and team knowledge sharing.