Skip to content
Agentmart
Submit a tool

postmortem

Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions.

Skill by prestarius

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/prestarius-postmortem

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions. Use whenever the user says "postmortem", "incident review", "RCA", "write up this outage", or when a diagnosing-bugs session ends on an incident that deserves a durable record.

Use cases: writing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/postmortem

What's inside

Skill name
postmortem
Description
Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions. Use whenever the user says "postmortem", "incident review", "RCA", "write up this outage", or when a diagnosing-bugs session ends on an incident that deserves a durable record.
License
MIT
Instructions
22 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

Read `./CONTEXT.md` if present. Gather facts from the conversation (especially any diagnosing-bugs
output), logs, and whatever the user provides. One incident per document.

Structure:
1. **Summary** — severity, duration, user impact, one-line cause. Up front, no suspense.
2. **Timeline** — absolute timestamps (date + time + zone), from first signal to resolution.
   Include detection lag and mitigation time explicitly.
3. **Contributing factors** — plural by default; resist the single "root cause". Cover the
   trigger, why defenses didn't catch it, and what made recovery slow.
4. **What went well / what went poorly** — honest, short.
5. **Follow-up actions** — concrete and verifiable, each preventing a contributing factor or
   shortening detection/recovery. Written so the to-tickets skill can turn them into tickets.

Rules:
- Blameless: name systems, gaps, and missing guardrails — never people. "The deploy pipeline
  allowed X", not "Y pushed without checking".
- Facts only; mark every unknown `TODO:` instead of reconstructing a plausible story.
- If the fix isn't verified yet, say so in the summary.

Offer (opt-in): file via the obsidian-note skill; capture a durable decision via the domain-modeling skill;
turn follow-ups into tickets via the to-tickets skill.

From prestarius/jet-skills-stack, MIT.

More from prestarius/jet-skills-stack

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Oct 19, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/prestarius/jet-skills-stack
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from prestarius

Cite this page

postmortem skill. Agent Mart. https://agentmart.dev/skills/prestarius-postmortem (last updated 2026-10-24)