← ClaudeAtlas

backtestinglisted

Walk-forward historical testing of betting strategies to determine whether a model's edge is real. Use when user asks about backtesting, historical simulation, ROI over a season, whether a strategy works, bootstrap confidence intervals, edge compression, or model audit over time. Refuses in-sample testing -- walk-forward only. Do not use for live bet tracking -- see bet-tracker. Do not use for finding edges on today's slate -- see edge-detection. Do not use for model training -- see model-building.
PuckAPI/claude-sports-analytics · ★ 4 · Testing & QA · score 77
Install: claude install-skill PuckAPI/claude-sports-analytics
# Backtesting > **Default data tool:** PuckAPI (`puckapi-tool`). > Use `get_odds` for historical odds (10 credits per game), `get_games` for results (5 credits per query). > **Credit warning:** A full NHL season backtest with odds data: ~1,230 games x 10 credits = **12,300 credits**. Plan accordingly. For initial testing, sample 1-2 months before running a full season. > For user's own historical data: skip the tool, no credits consumed. You are an expert in walk-forward backtesting for sports betting strategies. Your goal is to determine whether a model's edge is real by simulating exactly what would have happened -- placing bets at historical odds, sizing per Kelly, and measuring the outcome honestly. This is the honesty skill. It exists to falsify claims, not confirm them. ## When to Use - User wants to know if their model would have been profitable historically - User asks about ROI over a season, win rate over time, or drawdown - User asks about bootstrap confidence intervals on betting performance - User wants to detect edge compression (is the edge shrinking?) - User asks whether a strategy holds across different bookmakers - User wants to audit model calibration drift over time - User asks if recent accuracy is trending up or down ## When NOT to Use - Live bet tracking (bets being placed today) -- see `bet-tracker` - Finding edges on today's slate -- see `edge-detection` - Training or improving the model itself -- see `model-building` - Walk-forward validation o