agent-instructions
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what…
Use when reviewing trading performance and decisions. Covers what to record, separating process from outcome, identifying real patterns in your own behavior, and turning a review into a rule change. Trigger on "review my trades from last month", "help me set up a trading
Claude Code
$ npx -y skills add nimadorostkar/Claude-Skills-collection --skill trade-journal --agent claude-code
Codex
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a codex -y
Cursor
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a cursor -y
Gemini CLI
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a gemini-cli -y
GitHub Copilot
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a github-copilot -y
OpenCode
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a opencode -y
Windsurf
$ npx skills add nimadorostkar/Claude-Skills-collection --skill trade-journal -a windsurf -y
name: trade-journal description: Use when reviewing trading performance and decisions. Covers what to record, separating process from outcome, identifying real patterns in your own behavior, and turning a review into a rule change. Trigger on "review my trades from last month", "help me set up a trading journal", "i keep losing on the same kind of trade". Do not use for writing the risk rules themselves — see the risk-management skill. metadata: category: finance version: 1.0.0 tags: [journal, review, process, postmortem, discipline]
Learn from your own decisions rather than from your outcomes. A profitable trade taken against your rules is a bad trade that will be repeated; a losing trade taken correctly is a good one. Without a journal, these are indistinguishable.
1. **Record the thesis before the outcome** — At entry, in writing: why, where the stop is, where the target is, and what would prove the thesis wrong. Written afterwards, this is a rationalization, and it will be a flattering one. 2. **Grade the process, not the profit and loss** — Did you follow your rules? That is a binary question with a clear answer, and it is the only one you control. 3. **Categorize by setup and by mistake** — Not by outcome. "Chased an extended entry" is a category. "Lost money" is not. 4. **Review a sample large enough to be meaningful** — Twenty trades minimum. Any five trades can be attributed to anything. 5. **Look for the pattern, not the story** — Are the losses concentrated in one setup? One time of day? Trades taken after a loss? These are behavioral patterns and they recur. 6. **Change one rule, and date it** — Then measure whether it helped. Changing five rules at once means learning nothing.
**A trade record that permits an honest review:**
## 2026-06-14 | LONG NVDA | Momentum breakout
**Written at entry, before the outcome.**
Thesis : Breaking out of an 8-week base on 2.3x average volume. Relative
strength +6% vs SPY over 63 days. Earnings are 5 weeks away.
Entry : 118.40
Stop : 112.80 (below the base low; the breakout is invalid below it)
Target : 134.00 (the measured move; 2.8:1 reward-to-risk)
Size : 340 shares. Risk $1,904 = 0.95% of equity. Within the rules.
Invalidation: A close below 112.80, or a failed breakout that closes back
inside the base.
Regime check: trend up, volatility contracting. Breakouts are favored. PASS.
Pre-trade gate: PASS (stop set, risk within limit, sector exposure 18%/30%).
---
**Written at exit.**
Exit : 113.10 on 2026-06-21. Stopped out. -$1,802 (-0.90%).
Process grade: A. The setup met every criterion. The stop was where the thesis
was invalidated. The size was correct. It was executed as
planned and it did not work.
Outcome : Loss.
Lesson : NONE. This is what a losing trade taken correctly looks like.
Do not change anything on the basis of this trade. The breakout
failed. Some do.**The review that finds the actual pattern:**
Q2 review: 47 trades. By outcome: 21 winners, 26 losers. Net +2.1%. By process grade: 38 followed the rules, 9 did not. The finding is in the second line, not the first: Rule-following trades (38): +8.4% win rate 55% avg R +0.31 Rule-breaking trades (9): -6.3% win rate 22% avg R -0.70 Every rule-breaking trade shares one characteristic: it was entered within 90 minutes of closing a losing position. Seven of the nine were in a setup graded "C" or worse. Six were oversized. This is a revenge-trading pattern. It is not a strategy problem; the strategy made 8.4% this quarter. It is a behavioral problem that cost 6.3%. Rule change, effective 2026-07-01: No new position within 2 hours of closing a losing trade. No exceptions, no override. This is a hard gate, enforced in the pre-trade checklist, not a resolution to be more disciplined. Measure: count rule-breaking trades next quarter. Target: zero.
A curated library of 137 production-grade skills for Claude and other AI coding agents. Every skill follows one structure, speaks with one voice, and earns its place by changing what the agent does.
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what…
Use when an agent needs state that survives a session or a context compaction. Covers what to persist, file-based memory,…
Use when automating agent behavior with lifecycle hooks. Covers hook events, deterministic enforcement of rules the model should…
Use when packaging skills, commands, hooks, and MCP servers into a distributable plugin. Covers manifest structure, bundling,…
Use when writing a new skill for an AI agent. Covers scoping, description writing for reliable triggering, progressive…
Use when reviewing or improving an existing agent skill. Covers triggering accuracy, content quality, redundancy with the base…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.