Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Install Incident Postmortem
$ npx skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oxbshw/LLM-Agents-Ecosystem-Handbook incident-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/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/catalog/incident-postmortem .claude/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .claude/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oxbshw/LLM-Agents-Ecosystem-Handbook incident-postmortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/catalog/incident-postmortem .agents/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .agents/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oxbshw/LLM-Agents-Ecosystem-Handbook incident-postmortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/catalog/incident-postmortem .cursor/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .cursor/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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/oxbshw/LLM-Agents-Ecosystem-Handbook.git --path skills/catalog/incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oxbshw/LLM-Agents-Ecosystem-Handbook incident-postmortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/catalog/incident-postmortem .gemini/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .gemini/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/catalog/incident-postmortem .github/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .github/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-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 oxbshw/LLM-Agents-Ecosystem-Handbook incident-postmortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/catalog/incident-postmortem .opencode/skills/incident-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 "incident-postmortem" agent skill from https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/tree/main/skills/catalog/incident-postmortem into .opencode/skills/incident-postmortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-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
incident-postmortem- GitHub stars
- 552
- Token cost
- ~461 tokens
- SKILL.md length
- 208 words
- Files
- 2 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
- Works in 7 steps: Reconstruct the timeline (UTC), one row… → State impact in user-facing terms… → Identify the direct cause in one… → …
- Tasks that involve Runbooks and postmortems
- SKILL.md covers When to use, When NOT to use, Inputs and Outputs, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Incident Postmortem is an agent skill from oxbshw/LLM-Agents-Ecosystem-Handbook. Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/postmortem-template.md`).
It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: One-stop handbook for building, deploying, and understanding LLM agents with 60+ skeletons, tutorials, ecosystem guides, and evaluation tools. The licence is MIT.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/incident-postmortem”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Reconstruct the timeline (UTC), one row per notable event
- State impact in user-facing terms (requests failed, dollars lost, customers affected)
- Identify the direct cause in one sentence — what specifically broke
- List contributing factors (the conditions that made the incident possible / hard to mitigate)
- Separate what went well (genuine wins, not platitudes) and what didn't
- Owners + dates on every action item; hard fail if missing
- Tone: blameless. Describe systems failing, not people.
What it can do on your machine
Read from SKILL.md and the folder at commit 7f8ee3c. 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
Incident Postmortem loads about 461 tokens when it runs, and up to ~636 if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 208 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 oxbshw/LLM-Agents-Ecosystem-Handbook at commit 7f8ee3c, republished under its MIT licence (© oxbshw). 208 words, ~461 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-postmortem/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- incident-postmortem
- description
- Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
- version
- 0.1.0
- status
- experimental
- risk
- low
- tags
- ops, writes-files
Incident Postmortem
When to use
- After an incident with customer impact
- After a near-miss worth documenting
- For drills / GameDay exercises
When NOT to use
- Live incidents (use
incident-runbookinstead) - Pure private learnings (use a personal log)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
timeline | text or paths | yes | Source notes, alert links, chat extracts |
severity | S0–S3 | yes | Severity at peak |
incident_id | string | yes | e.g. INC-2026-04-12-001 |
Outputs
postmortem.md with: Summary, Impact, Timeline, Direct cause, Contributing factors, What went well, What didn't, Action items.
Workflow
- Reconstruct the timeline (UTC), one row per notable event
- State impact in user-facing terms (requests failed, dollars lost, customers affected)
- Identify the direct cause in one sentence — what specifically broke
- List contributing factors (the conditions that made the incident possible / hard to mitigate)
- Separate what went well (genuine wins, not platitudes) and what didn't
- Owners + dates on every action item; hard fail if missing
- Tone: blameless. Describe systems failing, not people.
References
Success criteria
- Every action item has an owner and a date
- Direct cause is one sentence
- No names attached to fault; only roles / systems
- Timeline times in UTC
Failure modes
- Missing source data → list gaps explicitly; don't fill with guesses
- Conflicting timelines → record both, flag for review
© oxbshw, 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 1 other file (references) in skills/catalog/incident-postmortem of oxbshw/LLM-Agents-Ecosystem-Handbook.
- SKILL.md
- references/postmortem-template.md
Open the folder on GitHubat commit 7f8ee3c
Compare with similar skills
Incident 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 |
|---|---|---|---|---|---|---|
| Incident Postmortem this skilloxbshw/LLM-Agents-Ecosystem-Handbook | 552 | — | ~461 | 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 oxbshw/LLM-Agents-Ecosystem-Handbook
API Design Reviewer
oxbshw/LLM-Agents-Ecosystem-Handbook
A skill your agent uses when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Dataset Profiler
oxbshw/LLM-Agents-Ecosystem-Handbook
A skill your agent uses when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
PR Summarizer
oxbshw/LLM-Agents-Ecosystem-Handbook
A skill your agent uses when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Adr Writer
oxbshw/LLM-Agents-Ecosystem-Handbook
A skill your agent uses when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
Sprint Planner
oxbshw/LLM-Agents-Ecosystem-Handbook
A skill your agent uses when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
Related
Categories
Questions about Incident Postmortem
What does Incident Postmortem do?
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads. Incident Postmortem is an agent skill from oxbshw/LLM-Agents-Ecosystem-Handbook. Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
When should I use Incident Postmortem?
Incident Postmortem fits situations like: tasks that involve Runbooks and postmortems.
How do I install Incident Postmortem in Claude Code?
Run `npx skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a claude-code`. Or copy the skill folder (skills/catalog/incident-postmortem in oxbshw/LLM-Agents-Ecosystem-Handbook) into .claude/skills/incident-postmortem in your project. Claude Code loads it when a task matches its description.
How do I install Incident Postmortem in Codex?
Run `npx skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-postmortem -a codex`. Or copy the skill folder (skills/catalog/incident-postmortem in oxbshw/LLM-Agents-Ecosystem-Handbook) into .agents/skills/incident-postmortem in your project. Codex loads it when a task matches its description.
Can I use Incident 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 oxbshw/LLM-Agents-Ecosystem-Handbook --skill incident-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/incident-postmortem, .gemini/skills/incident-postmortem, .github/skills/incident-postmortem and .opencode/skills/incident-postmortem in your project.
What does Incident Postmortem need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Postmortem is instructions for the agent only.
Does Incident 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 Incident 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 Incident Postmortem use?
Incident 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 Incident Postmortem use?
About 461 tokens (SKILL.md is roughly 1.8k 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 175 tokens, read only when the agent opens those files.
What are the alternatives to Incident Postmortem?
Skills that share tags, products or a category with Incident 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 Incident Postmortem?
oxbshw (a GitHub user) maintains it in oxbshw/LLM-Agents-Ecosystem-Handbook, which has 552 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 30, 2026.
Source: oxbshw/LLM-Agents-Ecosystem-Handbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.