backtest-expert
Expert guidance for systematic backtesting of trading strategies. Use when developing,…
Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns. Use after trader-memory-core and signal-postmortem have produced records, or when the user asks for a
$ npx -y skills add tradermonty/claude-trading-skills --skill trade-performance-coach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/trade-performance-coachContext preview
The summary Claude sees to decide when to auto-load this skill.
Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns. Use after trader-memory-core and signal-postmortem have produced records, or when the user asks for a
name: trade-performance-coach description: >- Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns. Use after trader-memory-core and signal-postmortem have produced records, or when the user asks for a post-trade coach, risk-manager style review, rule-adherence review, next-session operating rules, or psychology-aware trading behavior feedback. This skill does not provide buy/sell advice, therapy, or broker execution.
Trade Performance Coach reviews recorded trade outcomes and journal evidence to help a human trader improve their decision process. It converts closed-trade records, postmortem findings, risk rules, and optional market-regime context into an evidence-based coaching report covering:
This skill is intended to fill the support role that a risk manager, desk lead, or trading coach might provide in a professional trading environment. It is strictly a process-review skill: it never recommends entering, exiting, buying, selling, shorting, holding, or sizing a specific security.
Use this skill when any of the following are true:
Do not use this skill to:
If the input is incomplete, default to `REVIEW_REQUIRED` or `journal_only` mode and ask for missing records rather than inventing evidence.
Recommended upstream records:
No paid API key is required. The deterministic script works from local JSON/YAML-like records.
Minimum useful input is one recorded trade or one monthly aggregate.
Preferred fields:
review_type: single_trade | partial_close | monthly_aggregate trade_id: string ticker: string outcome: win | loss | breakeven | mixed planned: thesis: string entry: number stop: number target: number risk_r: number thesis_recorded_before_entry: boolean setup_confirmed: boolean market_regime: allowed | restrictive | cash_priority | unknown actual: entry: number exit: number risk_r: number portfolio_heat_r: number stop_moved: boolean stop_move_planned: boolean entry_before_confirmation: boolean traded_against_regime: boolean risk_plan: max_risk_per_trade_r: number max_portfolio_heat_r: number max_weekly_loss_r: number postmortem: root_cause: thesis_quality | execution | risk_sizing | market_environment | rule_violation | randomness | unknown notes: [string] journal: reflection: string emotions: [string] monthly: trades: [object] consecutive_losses: number rule_violations: number
The script tolerates partial records. Missing evidence is marked as `unclear`.
For the numeric fields actually evaluated (`planned.risk_r`, `actual.risk_r`, `risk_plan.max_risk_per_trade_r`, `actual.portfolio_heat_r`, `risk_plan.max_portfolio_heat_r`, and `monthly.consecutive_losses`), supplied non-null values must be finite and nonnegative. Numeric strings and zero are accepted; consecutive losses must be a whole number. Booleans, negative values, NaN, infinity, malformed strings, and conversion overflow are rejected. An explicitly invalid maximum never falls back to planned risk. Missing/null fields retain the partial-record behavior. The CLI validates every source record, including multiple inputs, and returns exit code 2 with a field-specific error before creating or modifying reports when a numeric value is invalid.
This skill remains beta. Numeric validation does not establish production readiness; report-ID path safety and the documented shallow multi-input wrapper still require separate assessment.
Collect the most recent closed trade record, postmortem, risk plan, and journal notes.
python3 skills/trade-performance-coach/scripts/review_trade_performance.py \ --input reports/trade_memory/closed_thesis_EXMPL.json \ --output-dir reports/trade-performance-coach
Compare actual actions against the user's documented plan and rules. Check for:
Compare actual risk and heat a
Claude Trading Skills started as a personal project to use AI to improve my own trading process. Claude Trading Skills is a Claude Skills-based trading workflow toolkit for time-constrained individual investors.
Expert guidance for systematic backtesting of trading strategies. Use when developing,…
This skill should be used when analyzing market breadth charts, specifically the S&P 500…
Generate Minervini-style breakout trade plans from VCP screener output with worst-case risk…
Screen US stocks using William O'Neil's CANSLIM growth stock methodology. Use when user…
Synthesize the three Jason Shapiro contrarian-pipeline verdicts (COT crowding, news-reaction…
Detect crowded speculative positioning in CFTC futures markets (COT report analysis) to find…