trade-performance-coach
Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns.
Install / Use
npx skills add tradermonty/claude-trading-skills --skill trade-performance-coachInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of trade-performance-coach
trade-performance-coach scores 93/100 on our quality scale, 673rd of 4,698 Development & Engineering skills we index (top 15%).
Its SKILL.md is 9.4 KB long, well organised into 18 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so trade-performance-coach is actively maintained.
- Our last check on 2026-10-04 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
trade-performance-coach compared with similar skills
All 4 of these similar skills score higher than trade-performance-coach; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| trade-performance-coach (this skill)by tradermonty | 93 | 2.9k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install trade-performance-coach?
- Run
npx skills add tradermonty/claude-trading-skills --skill trade-performance-coach. The install tabs above show the steps for each supported agent. - Which AI agents does trade-performance-coach work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is trade-performance-coach safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is trade-performance-coach still maintained?
- The repository was last updated about 2 months ago, so trade-performance-coach is actively maintained.
Skill content
View source on GitHubname: 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
Overview
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:
- process adherence
- risk discipline
- execution quality
- possible trading-behavior patterns
- next-session operating rules
- coach questions for reflection
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.
When to Use
Use this skill when any of the following are true:
- A trade has been closed and the user wants a post-trade coaching review.
- A partial close occurred and the user wants to inspect sizing, stop, or exit behavior.
- The user has
trader-memory-corethesis records andsignal-postmortemfindings and wants next-session operating rules. - The user wants a monthly review of recurring process, risk, execution, or behavior patterns.
- The user asks for a risk-manager style review of their own recorded trades.
- The user asks whether a loss was a process error, execution error, market environment issue, or acceptable variance.
- The user wants possible FOMO, revenge-trade, overconfidence, hesitation, stop-moving, or size-creep patterns flagged with evidence.
When Not to Use
Do not use this skill to:
- Pick stocks or rank trade candidates.
- Approve or reject a live trade as financial advice.
- Place orders or draft broker instructions.
- Provide therapy, mental-health diagnosis, or personality assessment.
- Infer private psychological traits beyond the trade evidence supplied.
- Shame the user for losses or rule violations.
- Replace
trader-memory-core; this skill consumes journal/thesis records and produces coaching findings.
If the input is incomplete, default to REVIEW_REQUIRED or journal_only mode and ask for missing records rather than inventing evidence.
Prerequisites
Recommended upstream records:
trader-memory-coreclosed thesis record or journal entrysignal-postmortempostmortem findings- original trade plan or trade ticket
- actual entry / exit / partial-close actions
- user-defined risk plan, if available
- optional
market-regime-daily/exposure-coachcontext
No paid API key is required. The deterministic script works from local JSON/YAML-like records.
Inputs
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.
Workflow
Step 1 — Collect source records
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
Step 2 — Evaluate process adherence
Compare actual actions against the user's documented plan and rules. Check for:
- missing pre-entry thesis
- setup confirmation skipped
- trade taken against market-regime gate
- stop moved without a pre-defined rule
- exit / partial close inconsistent with plan
- incomplete record quality
Step 3 — Evaluate risk discipline
Compare actual risk and heat against the risk plan. Check for:
- per-trade risk above max
- portfolio heat above max
- weekly loss or consecutive-loss escalation
- oversized trade after a winner or loser
- correlated exposure if provided
Step 4 — Evaluate execution quality
Classify entry, stop, exit, add, trim, and review behavior. Separate clean-process losses from execution mistakes.
Step 5 — Detect possible behavior patterns
Use evidence from journal notes and action flags to tag possible trading behavior patterns. Always tie a tag to evidence and use non-diagnostic language.
Supported MVP tags:
fomo_entryrevenge_tradepremature_exitoverconfidence_after_winnerstop_movedsize_creephesitationrule_driftno_pattern_detected
Step 6 — Produce next-session operating rules
Convert findings into temporary, concrete guardrails. Examples:
- require thesis record and screenshot before the next entry
- cap risk at 0.5R for the next two trades after a rule violation
- switch to review-only mode after repeated revenge-trade evidence
- do not chase a missed entry; add to watchlist for the next valid setup
Step 7 — Human decision gate
End every report with a human decision gate. The default action is journal_only.
Allowed actions:
accept_rules / modify_rules / defer / journal_only
Output
The skill produces a JSON report and optionally a Markdown report.
Required top-level JSON fields:
schema_versionreview_typereview_idoverall_verdictsummaryscoresprocess_adherence_findingsrisk_manager_notesexecution_quality_assessmentbehavioral_pattern_tagsnext_session_operating_rulescoach_questionshuman_decision_gatedisclaimer
Verdicts:
| Verdict | Meaning |
|---|---|
| OK | No material process violation found. Outcome appears compatible with the plan. |
| WARN | Minor process or record-quality concern. |
| REVIEW_REQUIRED | Meaningful process, risk, or behavior finding before next similar trade. |
| RULE_VIOLATION | Explicit user rule appears to have been broken. |
| COOL_DOWN | Repeated violations, drawdown/revenge pattern, or escalation suggests review-only mode. |
Example Command
python3 skills/trade-performance-coach/scripts/review_trade_performance.py \
--input skills/trade-performance-coach/scripts/tests/fixtures/single_trade_rule_violation_loss.json \
--output-dir reports/trade-performance-coach \
--markdown
Resources
Read these selectively when invoked:
references/review-framework.md— five-axis review model, scoring, verdictsreferences/behavior-tags.md— behavior tag definitions and evidence rulesreferences/risk-review-checklist.md— risk manager checklist and severity rulesreferences/output-contract.md— JSON output contract and schema notesreferences/hermes-integration.md— suggested Hermes/post-trade-coachand monthly coaching integrationassets/performance_coach_report.schema.json— machine-readable output schemascripts/review_trade_performance.py— deterministic local reviewer
Guardrails
- This is process-review support, not financial advice.
- Do not recommend buying, selling, shorting, holding, or sizing a specific security.
- Do not provide therapy or mental-health diagnosis.
- Do not infer personality traits.
- Do not shame or moralize the user.
- Tie every behavior tag to evidence.
- Use "possible pattern" language for behavior tags.
- Always include a human decision gate.
- Default to journal/review mode when data is incomplete.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
