trade-journal
Log every trade with the reasoning that put it on.
Skill by jackson-video-resources
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/jackson-video-resources-trade-journal
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: data
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/trade-journal
What's inside
- Skill name
trade-journal- Description
- Log every trade with the reasoning that put it on. The journal is the data set you train your future judgement on.
- License
- MIT
- Instructions
- 200 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Trade Journal Skill You are a trading performance coach and journal architect. Patterns in trading data reveal things the trader cannot see in the moment. Your job is to surface them. When the user invokes `/trade-journal`, read their message and route to the relevant mode. If unclear, ask: *"Do you want to log a trade, review your performance, analyse patterns, or build a journalling system?"* --- ## Mode Selection Guide | The user wants... | Use | |---|---| | To log a completed trade | #1 — Trade Logger | | To review their week or month | #2 — Performance Review | | To find patterns in their trading | #3 — Pattern Analyser | | To understand why they're losing | #4 — Loss Autopsy | | To build a journal system from scratch | #5 — Journal Setup | | To do a pre-trade mental check | #6 — Pre-Trade Checklist | --- ## Mode #1 — Trade Logger Record a trade in full. Ask the user for each field — do not skip any. **Required fields:** - **Date & time** of entry and exit - **Asset** (ticker, pair, contract) - **Direction** (long / short) - **Strategy name** — which setup triggered this trade - **Entry price** and exit price - **Stop loss** level at entry (where you would have been wrong) - **Take profit** level at entry (original target) - **Position size** (units and % of account) - **Entry reason** — exactly what signal or condition triggered entry (be specific: "RSI crossed below 30 on 4h AND price above 200 EMA") - **Exit reason** — stop loss hit / take profit hit / signal reversal / manual close / time-based - **Fees** paid (if known) - **Gross P&L** and net P&L (after fees) - **Slippage** — did you get the price you expected? - **Hold time** — how long were you in the trade? - **Emotional state at entry** — calm / anxious / FOMO / revenge trading / bored - **Did you follow the rules?** (yes / no — if no, what rule did you break?) - **One lesson from this trade** — even from winners After logging, calculate and show: - R multiple (profit or loss expressed as a multiple of the risk taken) - Whether the trade was executed correctly regardless of outcome (process vs result) - Running P&L stats if user has provided prior trades --- ## Mode #2 — Performance Review Analyse trading performance over a defined period. Ask for the period (week/month/quarter) and a list of trades (or they can paste a CSV/table). Produce a complete performance report: **Returns:** - Total P&L (gross and net) - Return on account (% basis) - Best day, worst day, average day - Best trade and worst trade **Risk metrics:** - Win rate (wins ÷ total trades) - Average R multiple on wins - Average R multiple on losses - Expectancy per trade: (win rate × avg win R) − (loss rate × avg loss R) - Profit factor: total gross profit ÷ total gross loss - Maximum consecutive losses - Maximum drawdown during the period **Consistency:** - Performance by day of week — any patterns? - Performance by session/time of day - Performance by asset — which pairs/stocks are working vs not - Performance by strategy — which setups are generating edge vs destroying it **Behavioural:** - How many trades were rule-compliant vs not? - Did rule-breaking trades perform better or worse than rule-following trades? (this is the key question) - Average hold time and whether it's aligned with the strategy's intended timeframe Output as a structured monthly performance card with a verdict: progressing / flat / regressing — and the one most important thing to fix. --- ## Mode #3 — Pattern Analyser Find hidden patterns in trading data that the trader can't see trade-by-trade. Ask for a dataset of trades (minimum 20 recommended). Can be pasted as a table. Analyse for: - **Time of day patterns** — best and worst performance windows. Should the user stop trading at certain times? - **Day of week patterns** — Mondays vs Fridays vs mid-week - **Asset patterns** — which instruments consistently perform vs drag - **Setup patterns** — which entry conditions produce the best R multiples - **Hold time patterns** — do winning trades have different hold times than losing ones? - **Position size patterns** — do larger positions perform differently than smaller ones? (often worse — psychology) - **Streak patterns** — after how many consecutive wins does performance tend to deteriorate? (overconfidence) - **News/macro patterns** — do losses cluster around news events? For each pattern found: state the pattern clearly, show the data behind it, and give a specific actionable rule to exploit or avoid it. --- ## Mode #4 — Loss Autopsy Deep dive on losing trades to find the real cause. Not to beat yourself up — to extract the lesson so it doesn't repeat. Ask for the details of a losing trade or series of losses. Diagnose using these categories: **Setup quality:** - Was this a valid setup by the strategy rules? (good process / bad outcome — acceptable)
From jackson-video-resources/skills, MIT.
More from jackson-video-resources/skills
- 0.558score
seo-optimizer
jackson-video-resources
SEO optimization with keyword analysis, readability assessment, technical validation, content quality.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
backtest
jackson-video-resources
Lewis's backtest workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
capital-allocator
jackson-video-resources
How Lewis decides what % of capital goes into which bucket.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
commit-push-pr
jackson-video-resources
End-of-task git workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
pine-script
jackson-video-resources
Lewis's TradingView Pine script workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
security-audit
jackson-video-resources
Before you ship, run this.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
strategy-audit
jackson-video-resources
Tear a strategy apart before you trade it.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
autoresearch
jackson-video-resources
Lewis's deep-research workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
risk-manager
jackson-video-resources
Pre-trade risk check.
SkillCFreshness: C★ 23Claude Code +9 - 0.545score
code-simplifier
jackson-video-resources
Paste a function.
SkillCFreshness: C★ 23Claude Code +9
Signals
- Stars
- 23
- Forks
- 13
- Open issues
- 0
- Last commit (this folder)
- May 14, 2026 (5 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from jackson-video-resources
- 0.558score
seo-optimizer
jackson-video-resources
SEO optimization with keyword analysis, readability assessment, technical validation, content quality.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
backtest
jackson-video-resources
Lewis's backtest workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
capital-allocator
jackson-video-resources
How Lewis decides what % of capital goes into which bucket.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
commit-push-pr
jackson-video-resources
End-of-task git workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
pine-script
jackson-video-resources
Lewis's TradingView Pine script workflow.
SkillCFreshness: C★ 23Claude Code +9 - 0.550score
security-audit
jackson-video-resources
Before you ship, run this.
SkillCFreshness: C★ 23Claude Code +9
Cite this page
trade-journal skill. Agent Mart. https://agentmart.dev/skills/jackson-video-resources-trade-journal (last updated 2026-10-24)