Trade Journal
Structured trade logging, performance review, behavioral pattern detection, and strategy attribution for systematic improvement
Install
/plugin marketplace add agiprolabs/claude-trading-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add agiprolabs/claude-trading-skills --skill trade-journalgit clone --depth 1 https://github.com/agiprolabs/claude-trading-skills.git /tmp/claude-trading-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-trading-skills/skills/trade-journal ~/.claude/skills/trade-journalPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Trade Journal Structured trade journaling for systematic improvement. Log every trade with context, review performance at multiple cadences, detect behavioral patterns that destroy edge, and attribute returns to specific strategies. ## Why Journaling Matters Most traders fail not from bad strategies but from bad behavior. A trade journal transforms subjective "feel" into objective data: - **Strategy Attribution**: Know which setups actually make money vs. which feel profitable - **Behavioral Detection**: Catch revenge trading, FOMO entries, and premature exits before they compound - **Pattern Recognition**: Discover that your Monday morning trades lose money, or that you cut SOL winners too early - **Accountability**: Written rationale before entry forces deliberate decision-making - **Improvement Tracking**: Measure whether changes to your process actually improve results Without a journal, you optimize on noise. With one, you optimize on signal. ## Trade Record Structure Every trade record captures context at entry and outcome at exit. See `references/record_format.md` for the complete 18-field schema. ### Minimum Required Fields
Details
- Skill name
trade-journal- Repository
- agiprolabs/claude-trading-skills
- Path
skills/trade-journal/SKILL.md- License
- MIT
- Repo updated
- 3 September 2026
FAQ
What does the Trade Journal skill do?
Structured trade logging, performance review, behavioral pattern detection, and strategy attribution for systematic improvement
How do I install the Trade Journal skill?
Claude Code plugin: /plugin marketplace add agiprolabs/claude-trading-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Trade Journal popular?
It lives in agiprolabs/claude-trading-skills, which has 564 GitHub stars and 113 forks.
Related skills
Backtrader
564agiprolabs/claude-trading-skills
Event-driven backtesting with bar-by-bar execution, complex order types, multiple analyzers, and custom indicators
Birdeye API
564agiprolabs/claude-trading-skills
Solana token market data via Birdeye — prices, OHLCV, trades, token metadata, security checks, and trader activity
Coingecko API
564agiprolabs/claude-trading-skills
Broad crypto market data from CoinGecko covering 13,000+ tokens. Global market stats, historical price data going back years, exchange volumes, trending tokens, and category filters. Best for macro analysis and long-term historical data.
01 Brainstorm
564ai-driven-dev/framework
Clarify a vague idea through questions. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.
Tbd
307jlevy/simple-modern-uv
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads,
01 Usage
564ai-driven-dev/framework
Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.