Performance Review (trading-review)
Turn the journal into decisions: what to do more of, what to stop.
python3 scripts/review.py # all closed trades
python3 scripts/review.py --period week # weekly digest (also month, quarter, year)
python3 scripts/review.py --since 2026-01-01 --report review.html
python3 scripts/review.py --setup VCP # one setup
python3 scripts/review.py --csv trades.csv # trading-backtest --trades-csv or a broker export
What it reports
- Core stats: net P&L, win rate, avg win/loss, payoff ratio, profit factor, expectancy,
avg/median/total R, SQN, max drawdown, win/loss streaks, hold time of winners vs losers.
- Breakdowns: by setup, side, month, weekday, top symbols.
- Coaching (rule-based, explained): negative expectancy, losses larger than 1R (stops not
honoured), holding losers longer than winners, early profit-taking, best/worst setup,
losing-streak behaviour, process grade vs results, missing stops, profit concentration.
How to run a review with the user
- Run the review (offer
--report for a shareable HTML file).
- Lead with 3 things: expectancy (are they making money per trade?), the biggest leak
(first coaching point), and the best setup.
- Turn insights into one or two concrete rule changes, e.g. "risk 0.5% on breakout trades until
avg R > 0 over the next 20", and offer to save them with trading-setup.
- Suggest trading-odds
trades --journal to see what the current edge implies for drawdowns.
Be direct about losing results, without moralising. Fewer than ~20 trades -> say conclusions are tentative.
1---2name: trading-review3description: Analyse trading performance from the journal or any trades CSV - win rate, payoff, profit factor, expectancy, R-multiples, SQN, drawdown and streaks, broken down by setup, side, symbol, weekday and month - plus rule-based coaching that flags cutting winners early, holding losers, stops not honoured, weak setups and luck concentration, with an HTML report. Use when the user asks "how am I doing", "review my trades", for a weekly or monthly review, "what's my best setup", "why am I losing", or wants a trading report card.4license: MIT5metadata:6 source: https://skillmd.com/skills/jiayaoqijia/trading-review7 author: reddygopalkrishna8 version: "0.2.0"9 pack: trading-skills10---1112# Performance Review (`trading-review`)1314Turn the journal into decisions: what to do more of, what to stop.1516```bash17python3 scripts/review.py # all closed trades18python3 scripts/review.py --period week # weekly digest (also month, quarter, year)19python3 scripts/review.py --since 2026-01-01 --report review.html20python3 scripts/review.py --setup VCP # one setup21python3 scripts/review.py --csv trades.csv # trading-backtest --trades-csv or a broker export22```2324## What it reports2526- **Core stats:** net P&L, win rate, avg win/loss, payoff ratio, profit factor, expectancy,27 avg/median/total R, SQN, max drawdown, win/loss streaks, hold time of winners vs losers.28- **Breakdowns:** by setup, side, month, weekday, top symbols.29- **Coaching** (rule-based, explained): negative expectancy, losses larger than 1R (stops not30 honoured), holding losers longer than winners, early profit-taking, best/worst setup,31 losing-streak behaviour, process grade vs results, missing stops, profit concentration.3233## How to run a review with the user34351. Run the review (offer `--report` for a shareable HTML file).362. Lead with 3 things: expectancy (are they making money per trade?), the biggest leak37 (first coaching point), and the best setup.383. Turn insights into one or two concrete rule changes, e.g. "risk 0.5% on breakout trades until39 avg R > 0 over the next 20", and offer to save them with trading-setup.404. Suggest trading-odds `trades --journal` to see what the current edge implies for drawdowns.4142Be direct about losing results, without moralising. Fewer than ~20 trades -> say conclusions are tentative.