New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Postmortem

by boshu2 in boshu2/agentops

Explain why a change, incident or session went as it did, separating proven causes from coincidence.

Apache-2.0Auto-check passedDevOps & Cloud

Install Postmortem

skills CLI
$ npx skills add boshu2/agentops --skill postmortem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install boshu2/agentops postmortem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/postmortem .claude/skills/postmortem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
postmortem
GitHub stars
447
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
641 words
Files
4 (incl. scripts, references)
Skills in repo
31
Repo updated
First seen
Licence
Apache-2.0

At a glance

Explain why a change, incident or session went as it did, separating proven causes from coincidence.

  • Works in 5 steps: Pin the question, accepted intent,… → Rebuild only the timeline the claims… → Put each causal claim through the first… → …
  • Retro is selected by name
  • SKILL.md covers First check: correlation or…, Prompt, Critical Constraints and Workflow, plus 2 more sections
  • Runs Shell scripts from its folder

What it does

Postmortem is an agent skill from boshu2/agentops. Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml` and `scripts/validate.sh`).

It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.

When your agent uses it

  • Retro is selected by name
  • Tasks that involve Runbooks and postmortems

Example prompts

  • “/postmortem”

Requirements

  • A Bash shell

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Pin the question, accepted intent, subject identity, actual outcome and
  2. Rebuild only the timeline the claims depend on, keeping delivered behavior,
  3. Put each causal claim through the first check above. Distinguish necessary
  4. For time or token claims, state source, interval, units, included and
  5. Optionally seek independent support or challenge for contested causal claims

What it can do on your machine

Read from SKILL.md and the folder at commit 3bdbfed. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Postmortem loads about 1.6k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 41 tokens; SKILL.md has 641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from boshu2/agentops at commit 3bdbfed, republished under its Apache-2.0 licence (© boshu2). 641 words, ~1,575 tokens.

Download SKILL.mdSave it as .claude/skills/postmortem/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
postmortem
description
Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.
practices
sre, lean-startup
hexagonal_role
domain
produces
postmortem-report.md
skill_api_version
1
user-invocable
true
disable-model-invocation
true
metadata.capabilities
postmortem
metadata.effects
write_postmortem_report
metadata.canonical_status
canonical
metadata.disposition
keep_strategy

Postmortem

Answer an explicit retrospective causal question about a completed or stopped goal, session or change using its actual intent, outcome and judgment evidence. For an explicitly requested interim analysis, pin the cutoff and pending checks; its conclusions describe that interval and do not establish a final outcome. Neighbours: how a plan not yet run could fail is Premortem; whether a finished change meets acceptance is Validate.

First check: correlation or cause?

Treat every causal statement as a hypothesis, including the one the caller arrives with. Promoting a claim from correlation to cause requires all three:

  • a stated mechanism: the specific path by which the condition produced the outcome, in terms a reader could check against the subject;
  • discriminating evidence: an observation that the mechanism predicts and at least one plausible alternative does not;
  • a counterfactual test: what should have differed if the claim were false, with cited evidence showing it did differ.

Post-hoc fix attribution, "we changed X and the failure stopped, therefore X was the cause", satisfies none of these alone. The symptom may be intermittent, or the recovery and the change may share an unobserved cause. Keep such claims as correlations, name the alternatives still standing, and suggest the discriminating experiment. A recommendation built on an unproven cause is framed as that experiment, not as a supported change. Every supported causal claim needs all three elements with citations; anything less stays a correlation or an unknown.

Prompt

text
Postmortem last Thursday's release: the deploy needed four attempts and two
rollbacks before it stuck. Using the deploy log, the CI runs and the incident
channel notes, which failures were avoidable and what caused each one?
Answer inline.

Critical Constraints

  • Postmortem is retrospective causal analysis, not the general learning umbrella or a code-acceptance gate: acceptance proof and causal inference are different judgments, so a request for code and a postmortem does not make the postmortem an input to code judgment. Wait for a known outcome unless interim analysis was requested, and keep the overall request incomplete until the requested analysis exists.
  • Existing verdicts and native judgments remain unchanged. It does not re-run acceptance validation or fabricate missing proof to enable a retrospective. An existing verdict.v2 is optional evidence; its absence does not exclude a stopped or unvalidated subject.
  • Because the caller owns subsequent action, do not rewrite proof, operate tracker state, change the remaining plan, reopen work or promote a rule.
  • Empty or inconclusive analysis is valid; recommend no change when warranted. Manufacture neither certainty nor a lesson.
Show full SKILL.md (328 more words)Show less

Workflow

  1. Pin the question, accepted intent, subject identity, actual outcome and available judgment with exact ids (commits, checks, messages, an existing verdict); keep missing evidence explicit.
  2. Rebuild only the timeline the claims depend on, keeping delivered behavior, failed or stopped work and process output distinct. Hidden author reasoning is not fact; missing judgment is not a PASS or a FAIL.
  3. Put each causal claim through the first check above. Distinguish necessary validation and compatibility work from avoidable rework; repeated review alone proves no waste.
  4. For time or token claims, state source, interval, units, included and excluded actors, and uncertainty. Separate elapsed time, overlapping work and accounting scopes; never equate totals with waste, savings or money without supporting evidence.
  5. Optionally seek independent support or challenge for contested causal claims within caller authority. Return the output below and stop; suggestions do not authorize implementation.

Output Specification

  • Default to concise inline Markdown, no mandatory report or worksheet:

    text
    Question: <the causal question>
Inputs: <intent, outcome and evidence, with exact ids>; missing: <gaps>
Timeline: <only the events the claims depend on>
Claims:
- <claim>: supported | correlation | rejected | unknown
  mechanism / discriminating evidence / counterfactual: <each, cited, or "none">
  alternatives still standing: <rivals the evidence cannot rule out>
Unknowns: <what would settle them>
Changes (at most three, or "no change"): <change> - <its limit, or the experiment that tests it>

  • Only when requested, save YYYY-MM-DD-postmortem-<topic>.md in caller-selected protected external non-Git storage. Missing routing does not authorize a repository fallback; preserve existing requested evidence under owner policy.

  • The caller owns bookkeeping, planning and delivery. Optional Memory owns any separately authorized curation, support and destination-disclosure review; retrospective evidence cannot promote itself.

Quality Checklist

  • The causal question and actual inputs are pinned; gaps are explicit.
  • Supported and rejected claims cite discriminating evidence.
  • Alternatives, counterfactuals, and unknowns remain visible.
  • At most three changes, each bounded or framed as an experiment.
  • The report stops short of proof, planning, tracker, and delivery authority.

Behavior examples are in postmortem.feature.

© boshu2, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/postmortem of boshu2/agentops.

  • SKILL.md
  • agents/openai.yaml
  • references/postmortem.feature
  • scripts/validate.sh

Open the folder on GitHubat commit 3bdbfed

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Postmortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Postmortem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Postmortem this skillboshu2/agentops4471 repos~1.6kAutomated safety check: PassApache-2.0
Trader Memory Coretradermonty/claude-trading-skills3k3 repos~4.3kAutomated safety check: PassMIT
OpenRig Upgrade Proceduremvschwarz/openrig5.9k1 repos~2.9kAutomated safety check: PassApache-2.0
Author Migrationnrwl/nx29k—~12kAutomated safety check: NotesMIT
Write Notes Like Deepseekczm15053/write-notes-like-deepseek484—~2kAutomated safety check: PassNone
GreptimeDB Release RunbookGreptimeTeam/greptimedb6.7k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Trader Memory Core

    tradermonty/claude-trading-skills

    Track investment theses across their lifecycle — from screening idea to closed position with postmortem.

    3k GitHub starsUsed in 3 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    5.9k GitHub starsUsed in 1 repo~2.9k tokens
    DevOps & CloudAuto-check passed

  • Author Migration

    nrwl/nx

    Author or scope a first-party Nx migration. An agent skill from nrwl/nx.

    29k GitHub stars~12k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Write Notes Like Deepseek

    czm15053/write-notes-like-deepseek

    A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…

    484 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • GreptimeDB Release Runbook

    GreptimeTeam/greptimedb

    Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.

    6.7k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Statem

    henryqin1997/statem

    A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…

    1.3k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from boshu2/agentops

All 31 skills in this repo

  • Agent Native

    boshu2/agentops

    Dispatch independent tasks to parallel workers or subagents without write collisions.

    447 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Council

    boshu2/agentops

    Compare independent opinions from several models or contexts without inflating agreement.

    447 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed

  • Craft Goal

    boshu2/agentops

    Draft or lint a bounded long-running goal prompt with a finish line and hard limits.

    447 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

  • Doc

    boshu2/agentops

    Write or update READMEs, docs, repo instructions and handoff notes, checked against source.

    447 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Idea Genie

    boshu2/agentops

    Brainstorm evidence-backed options for what to build, or stress-test an idea.

    447 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Implement

    boshu2/agentops

    Change or repair code, config or services without weakening tests; report what ran and what did not.

    447 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Categories

Questions about Postmortem

What does Postmortem do?

Explain why a change, incident or session went as it did, separating proven causes from coincidence. Postmortem is an agent skill from boshu2/agentops. Explain why a change, incident or session went as it did, separating proven causes from coincidence.

When should I use Postmortem?

Postmortem fits situations like: retro is selected by name; tasks that involve Runbooks and postmortems.

How do I install Postmortem in Claude Code?

Run `npx skills add boshu2/agentops --skill postmortem -a claude-code`. Or copy the skill folder (skills/postmortem in boshu2/agentops) into .claude/skills/postmortem in your project. Claude Code loads it when a task matches its description.

How do I install Postmortem in Codex?

Run `npx skills add boshu2/agentops --skill postmortem -a codex`. Or copy the skill folder (skills/postmortem in boshu2/agentops) into .agents/skills/postmortem in your project. Codex loads it when a task matches its description.

Can I use Postmortem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshu2/agentops --skill postmortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/postmortem, .gemini/skills/postmortem, .github/skills/postmortem and .opencode/skills/postmortem in your project.

What does Postmortem need to run?

Going by SKILL.md and its folder, Postmortem needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Postmortem access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Postmortem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Postmortem use?

Postmortem is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Postmortem use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 502 tokens, read only when the agent opens those files.

What are the alternatives to Postmortem?

Skills that share tags, products or a category with Postmortem: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), OpenRig Upgrade Procedure (mvschwarz/openrig, 5.9k stars), Author Migration (nrwl/nx, 29k stars) and Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 484 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Postmortem?

boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 447 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.

Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.