trade-journal
Skill0 starsChanged 7 months agoMITView on GitHub
Use when logging trades, reviewing trading performance, end of trading day, or weekly review - systematic trade logging with pattern detection for Polymarket
10 other projects use a version of this.
Adopted by
Most recently taken up by
- PatrickSUDO/fadacai-portfoliotheir own version, first seen Nov 6, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- Serennity007/claude-trading-skills-67their own version, first seen Aug 25, 2026
- NT-NinjaTrader/mcp-skillstheir own version, first seen Jul 25, 2026
- ZICXR/A-Stock-Skillstheir own version, first seen Jun 22, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- agiprolabs/claude-trading-skills★ 366same name
- PatrickSUDO/fadacai-portfolio★ 145same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- ZICXR/A-Stock-Skills★ 26same name
- jackson-video-resources/skills★ 17same name
- NT-NinjaTrader/mcp-skills★ 8same name
- tusharagg1/aifolimizer★ 2same name
- IngAs8/ClaudeSkill★ 0same name
- Serennity007/claude-trading-skills-67★ 0same name
- Yahmez3/Claude-Skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- deploy-pipelineSkill
- ecommerce-builderSkill
- hackathon-copilotSkill
- know-meSkill
- memory-managementSkill
- obsidian-memory-syncSkill
- polymarket-multi-agentSkill
- polymarket-vps-opsSkill
- researcherSkill
- self-healingSkill
- self-improvementSkill
- strategy-preflightSkill
- visual-promptingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Every trade gets logged to ~/obsidian-vault/memory/trade-journal/YYYY-MM-DD.json:
- Distinctive: line 46
Exit: Update entry with exit_price, outcome, pnl_usd, fees_usd
- Distinctive: line 47
End of day: Verify all trades logged, fill gaps from bot logs
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trade Journal
Systematic trade logging and pattern detection for Polymarket.
Trade Logging
Every trade gets logged to ~/obsidian-vault/memory/trade-journal/YYYY-MM-DD.json:
[
{
"timestamp": "2026-03-26T14:30:00Z",
"asset": "BTC > 90k by April",
"market_id": "0x...",
"strategy": "FairValueGap",
"timeframe": "1d",
"entry_price": 0.45,
"exit_price": 0.52,
"signal_type": "reversal",
"conviction": "high",
"size_usd": 5.00,
"outcome": "W",
"pnl_usd": 0.35,
"fees_usd": 0.10,
"notes": "Clean signal, good sizing"
}
]Fields
| Field | Values |
| signal_type | reversal, momentum, mean-reversion, news, arb, manual |
| conviction | low, medium, high, max |
| outcome | W, L, open, scratched |
| timeframe | 5m, 15m, 1h, 4h, 1d |
| strategy | FairValueGap, MeanReversion, MomentumBreakout, LatencyArb5m, ResolutionArb, CryptoCorrArb, SportsModelArb, manual |
When to Log
- Entry: Log immediately with outcome "open"
- Exit: Update entry with exit_price, outcome, pnl_usd, fees_usd
- End of day: Verify all trades logged, fill gaps from bot logs
Weekly Summary
Generate ~/obsidian-vault/memory/trade-journal/weekly-YYYY-WXX.md every Sunday:
# Trade Journal — Week XX, YYYY
## Stats
- Total trades: X
- Win rate: X%
- Total PnL: $X.XX (after fees: $X.XX)
- Avg win: $X.XX | Avg loss: $X.XX
- Profit factor: X.XX
## WR by Strategy
- FairValueGap: X% (N trades)
- MeanReversion: X% (N trades)
## WR by Signal Type
- reversal: X% (N trades)
- momentum: X% (N trades)
## WR by Conviction
- high: X% (N trades)
- medium: X% (N trades)
## WR by Asset (top 5)
- ...
## Patterns Detected
- ...
## Sizing Analysis
- Avg size on wins: $X.XX
- Avg size on losses: $X.XX
- Conviction-size alignment: [good/poor]Pattern Detection Rules (flag automatically)
- Any asset with WR < 40% over 5+ trades -> "Stop trading X on Y timeframe"
- High conviction WR < 50% -> "Conviction calibration is off"
- Avg win size < avg loss size -> "Sizing is inverted — cut losers faster or size winners bigger"
- Signal type with WR > 65% over 10+ trades -> "Double down on X signals"
- Strategy with negative PnL after fees over 20+ trades -> "Kill this strategy"
- Fee-to-PnL ratio > 50% -> "Fees are eating your edge"
Pulling Data from Polymarket API
POLY_ADDRESS="<bot-wallet-address>"
API_URL="https://clob.polymarket.com"
DATE=$(date +%Y-%m-%d)
OUTPUT="memory/trade-journal/${DATE}.json"
curl -s "${API_URL}/trades?maker=${POLY_ADDRESS}&limit=100" | \
python3 -c "
import json, sys
trades = json.load(sys.stdin)
formatted = []
for t in trades:
formatted.append({
'timestamp': t.get('timestamp',''),
'asset': t.get('market',''),
'market_id': t.get('asset_id',''),
'entry_price': float(t.get('price',0)),
'size_usd': float(t.get('size',0)),
'signal_type': 'bot',
'conviction': 'auto',
'outcome': 'open',
'notes': ''
})
print(json.dumps(formatted, indent=2))
" > "$OUTPUT"Lessons (from real losses)
- Low-cent positions across the board — even high-conviction got low fills. Minimum $0.50 on high conviction.
- Log conviction at signal time, not retroactively. Bot should tag each trade.
- Fees destroy marginal edges — only strategies with 70%+ WR survive 2% maker fees.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

