Back to Skills Marketplace
Skill pack

Postmortem Writer

Create blameless postmortems with timelines, impact, root cause, contributing factors, detection, response, and follow-ups.

v0.1.0 1 skill tools By Kendr postmortemincidenttimelineremediationsredevops
Publisher docsHosted archive

How to use it

  1. Open Kendr Desktop.
  2. Go to Skills, then Marketplace.
  3. Search for Postmortem Writer or postmortem-writer.
  4. Install the pack, then enable the pack or individual skills you want available in agentic mode.

Kendr Desktop compares the installed version with the hosted catalog version and offers an update when this pack changes.

Install source

Use this hosted archive when installing or updating the pack from Kendr Desktop.

https://kendr.org/api/skills/packs/postmortem-writer/archive

Postmortem Writer

Draft blameless incident postmortems from alerts, logs, deploy history, Slack threads, timelines, impact, root cause, and remediation actions.

Postmortem Writer

Use this skill when the user asks to write a postmortem, RCA, incident review, outage summary, learning review, or remediation plan.

Expected companion packs:

  • Incident Commander for incident timelines and evidence gathering.
  • Grafana Official MCP for alerts, metrics, logs, dashboards, and incident records.
  • GitHub Official MCP for deploys, code changes, pull requests, issues, and remediation tracking.
  • Slack Team Assistant for incident-channel decisions and handoffs.

Workflow:

  • Build a factual timeline before drafting conclusions.
  • Separate customer impact, internal impact, detection, mitigation, resolution, root cause, contributing factors, and what went well.
  • Use blameless language. Focus on systems, process, controls, and observability gaps.
  • Mark hypotheses and unknowns clearly when evidence is incomplete.
  • Include concrete remediation items with owner, priority, due date, and verification method when available.

Actions:

  • Draft issues, tickets, Slack updates, or docs only when requested.
  • Use Kendr approval before posting, sending, creating issues, assigning owners, or changing incident records.
  • Do not include private customer data, credentials, or unnecessary personal information.