Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
Install Nw Post Mortem Framework
$ npx skills add nWave-ai/nWave --skill nw-post-mortem-framework -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nWave-ai/nWave nw-post-mortem-framework --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/nWave-ai/nWave.git skills-src && mkdir -p .claude/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .claude/skills/nw-post-mortem-framework && 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 "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .claude/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-frameworkType 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 nWave-ai/nWave --skill nw-post-mortem-framework -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nWave-ai/nWave nw-post-mortem-framework --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .agents/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .agents/skills/nw-post-mortem-framework && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .agents/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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 nWave-ai/nWave --skill nw-post-mortem-framework -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nWave-ai/nWave nw-post-mortem-framework --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .cursor/skills/nw-post-mortem-framework && 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 "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .cursor/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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/nWave-ai/nWave.git --path nWave/skills/nw-post-mortem-framework--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 nWave-ai/nWave --skill nw-post-mortem-framework -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nWave-ai/nWave nw-post-mortem-framework --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .gemini/skills/nw-post-mortem-framework && 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 "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .gemini/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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 nWave-ai/nWave nw-post-mortem-frameworkInstalls 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 nWave-ai/nWave --skill nw-post-mortem-framework -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .github/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .github/skills/nw-post-mortem-framework && 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 "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .github/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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 nWave-ai/nWave --skill nw-post-mortem-framework -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nWave-ai/nWave nw-post-mortem-framework --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nWave-ai/nWave.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/nWave/skills/nw-post-mortem-framework .opencode/skills/nw-post-mortem-framework && 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 "nw-post-mortem-framework" agent skill from https://github.com/nWave-ai/nWave/tree/main/nWave/skills/nw-post-mortem-framework into .opencode/skills/nw-post-mortem-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nw-post-mortem-framework", 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
nw-post-mortem-framework- GitHub stars
- 617
- Token cost
- ~759 tokens
- SKILL.md length
- 173 words
- Files
- 1
- Skills in repo
- 106
- Repo updated
- First seen
- Licence
- MIT
At a glance
Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
- Works in 2 steps: Monitoring alerts/dashboards… → Communication channels (Slack, email,…
- Tasks that involve Runbooks and postmortems
- SKILL.md covers Principles, Post-Mortem Document Structure, Incident Timeline Reconstruction and Response Effectiveness…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nw Post Mortem Framework is an agent skill from nWave-ai/nWave. Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
Its SKILL.md is about 760 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: AI agents that guide you from idea to working code, with you in control at every step. The licence is MIT.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/nw-post-mortem-framework”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Monitoring alerts/dashboards (timestamps) | 2. Deployment logs/CI-CD records
- Communication channels (Slack, email, incident) | 4. VCS (commits, merges, deploys) | 5. User reports/support tickets
What it can do on your machine
Read from SKILL.md and the folder at commit da401a8. 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
Nw Post Mortem Framework loads about 759 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 173 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 nWave-ai/nWave at commit da401a8, republished under its MIT licence (© nWave-ai). 173 words, ~759 tokens.
Download SKILL.mdSave it as
.claude/skills/nw-post-mortem-framework/SKILL.md (or your agent's skills folder).- name
- nw-post-mortem-framework
- description
- Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning
- user-invocable
- false
- disable-model-invocation
- true
Post-Mortem Framework
Principles
- Blameless: focus on systems/processes, not individuals. People make reasonable decisions given available info.
- Evidence-based: every finding backed by logs, metrics, or documented actions
- Action-oriented: every finding produces concrete, assigned action item
- Learning-focused: capture what worked alongside what failed
Post-Mortem Document Structure
# Post-Mortem: [Incident Title]
**Date**: [incident date]
**Duration**: [start to resolution]
**Severity**: [P0-P3]
**Author**: [analyst]
## Summary
[2-3 sentence overview: what happened, impact, resolution]
## Timeline
| Time | Event | Source |
|------|-------|--------|
| HH:MM | [event] | [log/metric/report] |
## Impact
- Users affected: [number/percentage]
- Duration of impact: [time]
- Business impact: [quantified if possible]
- Systems affected: [list]
## Root Cause Analysis
[5 Whys analysis with evidence at each level]
## Detection and Response
- Time to detect: [duration] -- [how detected]
- Time to respond: [duration] -- [first action]
- Time to mitigate: [duration] -- [mitigation applied]
- Time to resolve: [duration] -- [permanent fix]
## What Went Well
- [positive observations about detection, response, recovery]
## What Could Be Improved
- [areas where detection, response, recovery fell short]
## Action Items
| ID | Action | Owner | Priority | Due Date |
|----|--------|-------|----------|----------|
| 1 | [specific action] | [team/person] | [P0-P3] | [date] |
## Lessons Learned
- [key takeaways for the organization]Incident Timeline Reconstruction
Sources
- Monitoring alerts/dashboards (timestamps) | 2. Deployment logs/CI-CD records
- Communication channels (Slack, email, incident) | 4. VCS (commits, merges, deploys) | 5. User reports/support tickets
Quality Checks
Events chronological with verified timestamps | gaps >5 min noted/explained | decision points identified with available info | causal relationships noted
Response Effectiveness Evaluation
Detection
Detected by monitoring or users? | Duration onset-to-detection? | Existing alerts relevant? Missing?
Escalation
Right team at right time? | Procedures followed? | Communication clear to stakeholders?
Resolution
Mitigation effective? | Rollback considered/viable? | Duration mitigation-to-permanent-fix?
Organizational Learning
Knowledge Capture
Document root causes as reusable patterns | update runbooks | share in retrospectives
Process Improvements
Update monitoring/alerting per detection gaps | revise deployment per rollback effectiveness | strengthen testing for failure scenario
Action Item Tracking
Every item has owner + due date | track in standups/sprint reviews | verify effectiveness post-deployment
© nWave-ai, 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 nWave/skills/nw-post-mortem-framework of nWave-ai/nWave.
Open the folder on GitHubat commit da401a8
Compare with similar skills
Nw Post Mortem Framework 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 |
|---|---|---|---|---|---|---|
| Nw Post Mortem Framework this skillnWave-ai/nWave | 617 | — | ~759 | 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 nWave-ai/nWave
All 106 skills in this repoNw Deliver Orchestration
nWave-ai/nWave
DELIVER wave orchestration workflow -- 9 phases from baseline to finalization.
Nw Diagram
nWave-ai/nWave
Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML.
Nw Diverge
nWave-ai/nWave
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence.
Nw Document
nWave-ai/nWave
Creates evidence-based documentation following DIVIO/Diataxis principles.
Nw Execute
nWave-ai/nWave
A skill your agent uses when a DELIVER roadmap already exists and you need to dispatch exactly one identified step through its TDD cycle.
Nw Refactor
nWave-ai/nWave
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring.
Related
Categories
Questions about Nw Post Mortem Framework
What does Nw Post Mortem Framework do?
Blameless post-mortem structure, incident timeline reconstruction, response evaluation, and organizational learning. Nw Post Mortem Framework is an agent skill from nWave-ai/nWave.
When should I use Nw Post Mortem Framework?
Nw Post Mortem Framework fits situations like: tasks that involve Runbooks and postmortems.
How do I install Nw Post Mortem Framework in Claude Code?
Run `npx skills add nWave-ai/nWave --skill nw-post-mortem-framework -a claude-code`. Or copy the skill folder (nWave/skills/nw-post-mortem-framework in nWave-ai/nWave) into .claude/skills/nw-post-mortem-framework in your project. Claude Code loads it when a task matches its description.
How do I install Nw Post Mortem Framework in Codex?
Run `npx skills add nWave-ai/nWave --skill nw-post-mortem-framework -a codex`. Or copy the skill folder (nWave/skills/nw-post-mortem-framework in nWave-ai/nWave) into .agents/skills/nw-post-mortem-framework in your project. Codex loads it when a task matches its description.
Can I use Nw Post Mortem Framework 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 nWave-ai/nWave --skill nw-post-mortem-framework -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nw-post-mortem-framework, .gemini/skills/nw-post-mortem-framework, .github/skills/nw-post-mortem-framework and .opencode/skills/nw-post-mortem-framework in your project.
What does Nw Post Mortem Framework need to run?
SKILL.md names no scripts, command-line tools or credentials: Nw Post Mortem Framework is instructions for the agent only.
Does Nw Post Mortem Framework 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 Nw Post Mortem Framework 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 Nw Post Mortem Framework use?
Nw Post Mortem Framework 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 Nw Post Mortem Framework use?
About 759 tokens (SKILL.md is roughly 3k 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 Nw Post Mortem Framework?
Skills that share tags, products or a category with Nw Post Mortem Framework: 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 Nw Post Mortem Framework?
nWave-ai (a GitHub organization) maintains it in nWave-ai/nWave, which has 617 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on September 16, 2026.
Source: nWave-ai/nWave on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.