New: 97,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

Post Mortem

by alirezarezvani in alirezarezvani/claude-skills

/cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.

MITAuto-check passedDevOps & Cloud

Install Post Mortem

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill post-mortem -a claude-code

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

GitHub CLI
$ gh skill install alirezarezvani/claude-skills post-mortem --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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-agents/skills/post-mortem .claude/skills/post-mortem && 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
post-mortem
GitHub stars
28k
Token cost
~968 tokens
SKILL.md length
204 words
Files
1
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

/cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.

  • A decision hits its 90-day review checkpoint
  • SKILL.md covers Pipeline Position, When to Run, Inputs and Output: Post-Mortem Record, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Its kill criteria trigger — e.g

What it does

Post Mortem is an agent skill from alirezarezvani/claude-skills. /cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Runbooks and postmortems and Retrospectives. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • A decision hits its 90-day review checkpoint
  • Its kill criteria trigger — e.g

Example prompts

  • “/post-mortem”

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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

Post Mortem loads about 968 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 204 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~968

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 204 words, ~968 tokens.

Download SKILL.mdSave it as .claude/skills/post-mortem/SKILL.md (or your agent's skills folder).
name
post-mortem
description
/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.

/cs:post-mortem — Honest Retrospective

Command: /cs:post-mortem <decision-path>

Closes the strategic sprint loop. Scores a decision against the success and kill criteria written before the decision (not retro-fitted) and revisits the preserved dissent. This is the rigor that compounds over time.

Pipeline Position

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                                                                                       ↑ you are here

When to Run

  • At the 90-day checkpoint (auto-scheduled by /cs:decide)
  • When a kill criterion triggers
  • After a major decision is reversed
  • Quarterly on all decisions of the past quarter

Inputs

  • The decision record (output of /cs:decide)
  • The execution plan (output of /cs:execute)
  • Actual outcomes (metrics, events, customer signals)

Output: Post-Mortem Record

Saved to ~/.claude/postmortems/YYYY-MM-DD-<slug>.md:

markdown
# Post-Mortem: <decision title>
**Decision date:** YYYY-MM-DD
**Post-mortem date:** YYYY-MM-DD
**Status:** WIN / PARTIAL / LOSS / MIXED

## Outcome Scoring (against pre-committed criteria)

| Success Criterion | Threshold | Actual | Met? |
|---|---|---|---|
| <metric 1> | <threshold> | <actual> | ✅ / ❌ |
| <metric 2> | <threshold> | <actual> | ✅ / ❌ |

| Kill Criterion | Threshold | Actual | Triggered? |
|---|---|---|---|
| <metric> | <threshold> | <actual> | ✅ / ❌ |

**Overall:** WIN / PARTIAL / LOSS / MIXED

## What We Got Right
- <factor 1>
- <factor 2>

## What We Got Wrong
- <factor 1>
- <factor 2>

## Preserved Dissent — Revisited
[Original dissent from the boardroom memo, scored:]

- **<dissenter>:** <original concern>
  - **Did it materialize?** YES / NO / PARTIAL
  - **Cost if YES:** <quantified impact>
  - **Lesson:** <one sentence>

## Assumption Audit
[Original brief's assumptions, scored:]

- **Assumption 1:** <text>
  - **Held?** YES / NO / PARTIAL
  - **Why:** <explanation>

## Process Lessons
- **Phase 2 isolation worked?** YES / NO
- **Devil's advocate concerns played out?** YES / NO / PARTIAL
- **Cadence was right?** YES / TOO LOOSE / TOO TIGHT

## Forward Actions
- [ ] <change to operating system or routing logic>
- [ ] <new decision to make based on this learning>
- [ ] <update company-context.md>

## Status
- WIN → archive, log lesson
- LOSS → schedule follow-up boardroom: `/cs:brief` for the next call

Why Pre-Committed Criteria Matter

The biggest temptation in post-mortems is retroactive justification: "we always knew X, that's why we did Y." Pre-committed criteria, signed at /cs:decide time, eliminate that move. The numbers either matched or they didn't.

Why Revisit Dissent

The dissent column from /cs:boardroom is the single most useful piece of organizational memory. Most of the time, the dissenter was directionally right. Revisiting and scoring it builds calibration over years.

Routing

  • /cs:brief — if the post-mortem surfaces a new decision
  • /cs:freeze — if the post-mortem reveals a process gap that needs cooldown enforcement
  • Updates to company-context.md via cs-onboard

Version: 1.0.0

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

Files

Just SKILL.md in c-level-agents/skills/post-mortem of alirezarezvani/claude-skills.

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Post Mortem 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.

Post Mortem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Post Mortem this skillalirezarezvani/claude-skills28k—~968Automated safety check: PassMIT
Campaign Postmortemzapier/gtm-cheat-codes342—~438Automated safety check: PassMIT
After Action Reportrampstackco/claude-skills9351 repos~2.5kAutomated safety check: PassMIT
Breach Patternsbriiirussell/cybersecurity-skills412—~3.5kAutomated safety check: NotesMIT
66 Crisis Playbook Globalminhnv0807/ai-business-skills608—~2.8kAutomated safety check: PassMIT
Incident RetrospectiveOpenHands/extensions157—~922Automated safety check: PassMIT

Similar skills

  • Campaign Postmortem

    zapier/gtm-cheat-codes

    Official

    Build sourced campaign retrospectives from goals, launch context, performance data, team feedback, and follow-up actions.

    342 GitHub stars~438 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    935 GitHub starsUsed in 1 repo~2.5k tokens
    Product & Project ManagementAuto-check passed

  • Breach Patterns

    briiirussell/cybersecurity-skills

    Learn from public breach disclosures — extract the audit question each one implies and check your own stack.

    412 GitHub stars~3.5k tokensUpdated 4 mo ago
    DatabasesAuto-check: notes

  • 66 Crisis Playbook Global

    minhnv0807/ai-business-skills

    A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…

    608 GitHub stars~2.8k tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

  • Incident Retrospective

    OpenHands/extensions

    Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions.

    157 GitHub stars~922 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Report Generation

    seb1n/awesome-ai-agent-skills

    Generate professional reports — sprint retrospectives, financial summaries, analytics dashboards, and incident postmortems — from structured data with templates, charts, and multi-format output.

    206 GitHub stars~3.4k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed

  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Categories

Questions about Post Mortem

What does Post Mortem do?

/cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent. Post Mortem is an agent skill from alirezarezvani/claude-skills. /cs:post-mortem <decision — Honest retrospective on an executed decision, scored against original assumptions and dissent.

When should I use Post Mortem?

Post Mortem fits situations like: A decision hits its 90-day review checkpoint; its kill criteria trigger — e.g.

How do I install Post Mortem in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill post-mortem -a claude-code`. Or copy the skill folder (c-level-agents/skills/post-mortem in alirezarezvani/claude-skills) into .claude/skills/post-mortem in your project. Claude Code loads it when a task matches its description.

How do I install Post Mortem in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill post-mortem -a codex`. Or copy the skill folder (c-level-agents/skills/post-mortem in alirezarezvani/claude-skills) into .agents/skills/post-mortem in your project. Codex loads it when a task matches its description.

Can I use Post Mortem 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 alirezarezvani/claude-skills --skill post-mortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-mortem, .gemini/skills/post-mortem, .github/skills/post-mortem and .opencode/skills/post-mortem in your project.

What does Post Mortem need to run?

SKILL.md names no scripts, command-line tools or credentials: Post Mortem is instructions for the agent only.

Does Post Mortem 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 Post Mortem 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. Review the folder before installing.

What licence does Post Mortem use?

Post Mortem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Post Mortem use?

About 968 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Post Mortem?

Skills that share tags, products or a category with Post Mortem: Campaign Postmortem (zapier/gtm-cheat-codes, 342 stars), After Action Report (rampstackco/claude-skills, 935 stars), Breach Patterns (briiirussell/cybersecurity-skills, 412 stars) and 66 Crisis Playbook Global (minhnv0807/ai-business-skills, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Post Mortem?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,788 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

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