Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Blameless post-mortem incident analysis with timeline, root cause, and action items.
Install Postmortem
$ npx skills add neurofoo/agent-skills --skill postmortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neurofoo/agent-skills postmortem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/postmortem .claude/skills/postmortem && rm -rf skills-srcUse ~/.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/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .claude/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/neurofoo/agent-skills/tree/main/postmortemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add neurofoo/agent-skills --skill postmortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neurofoo/agent-skills postmortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/postmortem .agents/skills/postmortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .agents/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill postmortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neurofoo/agent-skills postmortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/postmortem .cursor/skills/postmortem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .cursor/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/neurofoo/agent-skills.git --path postmortem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add neurofoo/agent-skills --skill postmortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neurofoo/agent-skills postmortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/postmortem .gemini/skills/postmortem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .gemini/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install neurofoo/agent-skills postmortemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add neurofoo/agent-skills --skill postmortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/postmortem .github/skills/postmortem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .github/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill postmortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install neurofoo/agent-skills postmortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/postmortem .opencode/skills/postmortem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "postmortem" agent skill from https://github.com/neurofoo/agent-skills/tree/main/postmortem into .opencode/skills/postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "postmortem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
postmortem- GitHub stars
- 119
- Token cost
- ~684 tokens
- SKILL.md length
- 267 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Blameless post-mortem incident analysis with timeline, root cause, and action items.
- Works in 3 steps: [lesson] → [lesson] → [lesson]
- Tasks that involve Runbooks and postmortems
- SKILL.md covers Instructions, Executive Summary, Timeline and Impact, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Postmortem is an agent skill from neurofoo/agent-skills. Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
Its SKILL.md is about 680 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. The repository describes itself as: Agent Skills for Claude Code and OpenCode. The licence is MIT.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/postmortem”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- [lesson]
- [lesson]
- [lesson]
What it can do on your machine
Read from SKILL.md and the folder at commit 0e7ac2a. 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.
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 684 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 267 words of instructions outside code blocks.
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 neurofoo/agent-skills at commit 0e7ac2a, republished under its MIT licence (© neurofoo). 267 words, ~684 tokens.
Download SKILL.mdSave it as
.claude/skills/postmortem/SKILL.md (or your agent's skills folder).- name
- postmortem
- description
- Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
- user-invocable
- true
Blameless Post-Mortem
Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.
Instructions
Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.
Output Format
Executive Summary
Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]
Summary [2-3 sentence overview: what happened, impact, resolution]
Timeline
All times in [timezone].
| Time | Event | Actor |
|---|---|---|
| HH:MM | [What happened] | [Who/what did it] |
| HH:MM | [Detection] | [How it was noticed] |
| HH:MM | [Response action] | [Who responded] |
| HH:MM | [Resolution] | [What fixed it] |
Key Moments
- Trigger: [What initiated the incident]
- Detection: [How/when we knew something was wrong]
- Mitigation: [When bleeding was stopped]
- Resolution: [When fully resolved]
Impact
Customer Impact
- Users affected: [number]
- Duration of impact: [time]
- Symptoms experienced: [what users saw]
Business Impact
- Revenue impact: [if applicable]
- SLA/SLO breach: [yes/no, details]
Root Cause Analysis
Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]
Trigger [The immediate cause—what set things in motion]
Contributing Factors
| Factor | How It Contributed |
|---|---|
| [factor] | [explanation] |
Why Wasn't This Caught?
- Why didn't tests catch it?
- Why didn't monitoring alert earlier?
What Went Well
| What Worked | Why It Helped |
|---|---|
| [thing] | [explanation] |
What Went Poorly
| What Failed | Impact |
|---|---|
| [thing] | [impact] |
Action Items
Immediate (This week)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
Short-term (This month)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
Lessons Learned
- [lesson]
- [lesson]
- [lesson]
Guidelines
- Blameless: "The deploy script didn't validate" not "Alice deployed without checking"
- Thorough timeline: Include everything, even embarrassing delays
- Specific actions: "Add memory alerting" not "Improve monitoring"
- Assigned owners: Unowned actions don't happen
$ARGUMENTS
© neurofoo, 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 postmortem of neurofoo/agent-skills.
Open the folder on GitHubat commit 0e7ac2a
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Postmortem this skillneurofoo/agent-skills | 119 | — | ~684 | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 477 | — | ~1.9k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 5.5k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
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…
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.
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.
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…
More from neurofoo/agent-skills
All 22 skills in this repoFive Whys Analysis
neurofoo/agent-skills
Runs a Five Whys root cause analysis, asking why repeatedly from the stated problem until it reaches an actionable cause, then lists corrective actions and verification.
Eisenhower Matrix Prioritizer
neurofoo/agent-skills
Sorts a task list into the four Eisenhower quadrants (do, schedule, delegate, eliminate) with reasons, a time distribution check and first actions.
OODA Loop Analysis
neurofoo/agent-skills
Walks a problem or decision through the OODA loop: observe the facts, orient on causes and assumptions, decide among at least three options, and plan the execution.
Cynefin Problem Classifier
neurofoo/agent-skills
Sorts a problem into the Cynefin domains of simple, complicated, complex, chaotic or confused, then recommends a way of working that fits that domain.
Wardley Map Analysis
neurofoo/agent-skills
Maps a user need's value chain against evolution stages to guide build-versus-buy decisions and show competitive dynamics.
Jtbd
neurofoo/agent-skills
Jobs to Be Done analysis to understand what customers really want.
Related
Categories
Questions about Postmortem
What does Postmortem do?
Blameless post-mortem incident analysis with timeline, root cause, and action items. Postmortem is an agent skill from neurofoo/agent-skills. Blameless post-mortem incident analysis with timeline, root cause, and action items.
When should I use Postmortem?
Postmortem fits situations like: tasks that involve Runbooks and postmortems.
How do I install Postmortem in Claude Code?
Run `npx skills add neurofoo/agent-skills --skill postmortem -a claude-code`. Or copy the skill folder (postmortem in neurofoo/agent-skills) 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 neurofoo/agent-skills --skill postmortem -a codex`. Or copy the skill folder (postmortem in neurofoo/agent-skills) 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 neurofoo/agent-skills --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?
SKILL.md names no scripts, command-line tools or credentials: Postmortem is instructions for the agent only.
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. Review the folder before installing.
What licence does Postmortem use?
Postmortem 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 Postmortem use?
About 684 tokens (SKILL.md is roughly 2.7k 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 Postmortem?
Skills that share tags, products or a category with Postmortem: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 477 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Postmortem?
neurofoo (a GitHub user) maintains it in neurofoo/agent-skills, which has 119 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on January 19, 2026.
Source: neurofoo/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.