Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Review a completed session to extract actionable improvements.
Install Post Mortem
$ npx skills add rileyhilliard/claude-essentials --skill post-mortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rileyhilliard/claude-essentials post-mortem --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/rileyhilliard/claude-essentials.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ce/skills/post-mortem .claude/skills/post-mortem && 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 "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .claude/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortemType 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 rileyhilliard/claude-essentials --skill post-mortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rileyhilliard/claude-essentials post-mortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ce/skills/post-mortem .agents/skills/post-mortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .agents/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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 rileyhilliard/claude-essentials --skill post-mortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rileyhilliard/claude-essentials post-mortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ce/skills/post-mortem .cursor/skills/post-mortem && 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 "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .cursor/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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/rileyhilliard/claude-essentials.git --path plugins/ce/skills/post-mortem--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 rileyhilliard/claude-essentials --skill post-mortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rileyhilliard/claude-essentials post-mortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ce/skills/post-mortem .gemini/skills/post-mortem && 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 "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .gemini/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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 rileyhilliard/claude-essentials post-mortemInstalls 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 rileyhilliard/claude-essentials --skill post-mortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ce/skills/post-mortem .github/skills/post-mortem && 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 "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .github/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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 rileyhilliard/claude-essentials --skill post-mortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rileyhilliard/claude-essentials post-mortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rileyhilliard/claude-essentials.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ce/skills/post-mortem .opencode/skills/post-mortem && 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 "post-mortem" agent skill from https://github.com/rileyhilliard/claude-essentials/tree/main/plugins/ce/skills/post-mortem into .opencode/skills/post-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-mortem", 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
post-mortem- GitHub stars
- 130
- Token cost
- ~1.3k tokens
- SKILL.md length
- 582 words
- Files
- 7 (incl. references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review a completed session to extract actionable improvements.
- Works in 4 steps: Reconstruct What Happened → Assess Execution Quality → Identify Systemic Causes → …
- Tasks that involve Runbooks and postmortems
- SKILL.md covers When to Use, Investigation Types, Core Process and Output Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Post Mortem is an agent skill from rileyhilliard/claude-essentials. Review a completed session to extract actionable improvements. Identifies DX friction, documentation gaps, architectural confusion, anti-patterns, process failures, and skill/config improvements. Uses progressive disclosure for targeted investigation types.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/anti-patterns.md`, `references/architecture-clarity.md` and `references/bug-prevention.md`).
It sits in DevOps & Cloud, covering Runbooks and postmortems. The licence is MIT.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/post-mortem”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3a67a01. 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 1.3k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 582 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 rileyhilliard/claude-essentials at commit 3a67a01, republished under its MIT licence (© rileyhilliard). 582 words, ~1,320 tokens.
Download SKILL.mdSave it as
.claude/skills/post-mortem/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- post-mortem
- description
- Review a completed session to extract actionable improvements. Identifies DX friction, documentation gaps, architectural confusion, anti-patterns, process failures, and skill/config improvements. Uses progressive disclosure for targeted investigation types.
Post-Mortem
Review a completed session or task to assess how it went and extract improvements. This covers both "how did we do" evaluation and "what can we learn" investigation.
When to Use
After completing any non-trivial task or session. The goal is continuous improvement:
- Routine review: How smooth was execution? Where did friction occur?
- Problem sessions: Things took longer than expected, multiple corrections needed
- Bug fixes: What caused it and what would prevent it next time?
- New patterns: Something worked well that should be codified
Investigation Types
Load the relevant reference based on what you're investigating:
| Situation | Load | File |
|---|---|---|
| Agent hit friction during execution (wrong files, bad assumptions, unclear conventions) | DX Friction | references/dx-friction.md |
| Documentation (READMEs, comments, API docs) was wrong, incomplete, or misleading | Documentation Gaps | references/documentation-gaps.md |
| Code was hard to understand or things were in unexpected places | Architecture Clarity | references/architecture-clarity.md |
| A bug was fixed but the root cause suggests a process gap | Bug Prevention | references/bug-prevention.md |
| Code works but diverges from best practices, idioms, or established conventions | Anti-Patterns | references/anti-patterns.md |
Skills, hooks, commands, agents, or .claude/ configs need updating | Tooling Improvements | references/tooling-improvements.md |
Load multiple references when the session spans investigation types.
Core Process
Every post-mortem follows four steps regardless of investigation type.
1. Reconstruct What Happened
Walk through the session timeline. For each significant step, note:
- What was attempted
- What actually happened
- Where corrections were needed and why
- What went smoothly (worth noting what worked, not just what didn't)
Don't editorialize yet. Just document the sequence.
2. Assess Execution Quality
Evaluate how the session went overall:
- Efficiency: Did we take a direct path or wander? Where were the detours?
- Accuracy: Were initial approaches correct, or did we need multiple corrections?
- Tooling fit: Did skills, commands, and configs help or get in the way?
- Communication: Was intent clear between user and agent throughout?
- Outcome: Did we deliver what was asked for? Is it solid or just "works for now"?
Flag anything that felt harder than it should have been, even if it ultimately succeeded.
Show full SKILL.md (251 more words)Show less
3. Identify Systemic Causes
For each friction point, ask: "What would have prevented this?"
Push past the first answer. "I should have read the file more carefully" is a symptom. "The file's name doesn't indicate what it contains" or "there's no convention documented for where this type of code lives" is a systemic cause.
Good root causes point to something fixable:
- A missing or misleading piece of documentation
- An architectural pattern that's inconsistent or undiscoverable
- A skill/config that gives wrong guidance
- A convention that exists but isn't written down
- A test gap that allowed a regression
- A workflow that worked well but isn't codified
Bad root causes are just descriptions of what went wrong:
- "I made a mistake"
- "The code was complex"
- "It took a while to figure out"
4. Propose Concrete Actions
Every finding should produce one of these:
- Documentation update - Fix incorrect docs, add missing docs, clarify ambiguous docs
- Skill/config update - Modify an existing skill or CLAUDE.md instruction
- New skill/hook - Create a new skill or hook to codify a pattern
- Architecture improvement - Refactor to make the system more discoverable
- Test addition - Add tests that would catch this class of issue
- Codify a win - Something that worked well should be made repeatable
Each action should have a specific file path and description of the change. Vague actions like "improve documentation" are not useful.
Output Format
Match the length of written documents to what the task needs: cover the substance, but do not pad with filler sections, redundant summaries, or boilerplate.
## Session Post-Mortem
### What Happened
[Timeline of the session with key decision points]
### Execution Assessment
- **Outcome:** [What was delivered vs what was asked]
- **Efficiency:** [Direct path or detours? Where and why?]
- **What worked well:** [Patterns, skills, or approaches worth repeating]
### Findings
#### Finding 1: [Title]
**What happened:** [The friction or issue, stated factually. 1-2 sentences]
**Root cause:** [The systemic issue underneath. 1-2 sentences]
**Action:** [Specific change with file path. 1-2 sentences]
**Priority:** [High/Medium/Low based on how often this would recur]
#### Finding 2: [Title]
...
### Summary
[1-2 sentences: biggest takeaway and what should change first]© rileyhilliard, MIT. 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 6 other files (references) in plugins/ce/skills/post-mortem of rileyhilliard/claude-essentials.
- SKILL.md
- references/anti-patterns.md
- references/architecture-clarity.md
- references/bug-prevention.md
- references/documentation-gaps.md
- references/dx-friction.md
- references/tooling-improvements.md
Open the folder on GitHubat commit 3a67a01
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Post Mortem this skillrileyhilliard/claude-essentials | 130 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 3 repos | ~4.3k | Automated safety check: Pass | MIT | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 5.9k | 1 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 484 | — | ~2k | Automated safety check: Pass | None | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
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.
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…
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 rileyhilliard/claude-essentials
All 17 skills in this repoHandling Errors
rileyhilliard/claude-essentials
Prevents silent failures and context loss in error handling.
Planning Products
rileyhilliard/claude-essentials
Defines product features from a PM perspective (JTBD, competitive research, scope negotiation) before technical planning.
Writing Tests
rileyhilliard/claude-essentials
Writes behavior-focused tests using Testing Trophy model with real dependencies.
Optimizing Performance
rileyhilliard/claude-essentials
Measure-first performance optimization that balances gains against complexity.
Architecting Systems
rileyhilliard/claude-essentials
Guides clean, scalable system architecture during the build phase.
Design
rileyhilliard/claude-essentials
Enforces precise, minimal design for dashboards and admin interfaces.
Related
Categories
Questions about Post Mortem
What does Post Mortem do?
Review a completed session to extract actionable improvements. Post Mortem is an agent skill from rileyhilliard/claude-essentials. Review a completed session to extract actionable improvements.
When should I use Post Mortem?
Post Mortem fits situations like: tasks that involve Runbooks and postmortems.
How do I install Post Mortem in Claude Code?
Run `npx skills add rileyhilliard/claude-essentials --skill post-mortem -a claude-code`. Or copy the skill folder (plugins/ce/skills/post-mortem in rileyhilliard/claude-essentials) 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 rileyhilliard/claude-essentials --skill post-mortem -a codex`. Or copy the skill folder (plugins/ce/skills/post-mortem in rileyhilliard/claude-essentials) 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 rileyhilliard/claude-essentials --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 1.3k tokens (SKILL.md is roughly 5.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 5.1k tokens, read only when the agent opens those files.
What are the alternatives to Post Mortem?
Skills that share tags, products or a category with Post Mortem: 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 Post Mortem?
rileyhilliard (a GitHub user) maintains it in rileyhilliard/claude-essentials, which has 130 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on August 18, 2026.
Source: rileyhilliard/claude-essentials on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.