strategy-optimization
Skill0 starsChanged 4 months agoMITView on GitHub
Walk-forward and out-of-sample optimization for trading strategies with overfitting protection. Use when tuning parameters, selecting models, or claiming a strategy generalizes.
In this repository11 other files it gives its agents.
- advanced-sql-timescaleSkill
- backtesting-disciplineSkill
- crypto-liquidity-flowSkill
- fastapi-best-practicesSkill
- llm-integrationSkill
- market-microstructureSkill
- qdrant-vector-dbSkill
- redis-patternsSkill
- risk-managementSkill
- senior-prompt-engineerSkill
- websocket-realtimeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Deflated Sharpe / multiple-testing correction: when scanning many combos.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strategy Optimization
Principle
Optimization that maximizes in-sample performance is curve-fitting. The goal is robust generalization, not peak historical return.
Walk-forward
- Split history into rolling windows: train (in-sample) → test (out-of-sample) → roll forward.
- Optimize parameters only on each train window; record performance on the following test window.
- Aggregate out-of-sample results — that is the honest estimate.
Anti-overfitting
- Parameter parsimony — fewer knobs = more robust. Reject params with no economic rationale.
- Plateau, not peak — prefer parameter regions where neighbors also perform well; a lone spike is noise.
- Out-of-sample gate — if OOS Sharpe < ~50% of IS Sharpe, the edge is likely fitted.
- Deflated Sharpe / multiple-testing correction when scanning many combos.
- Cross-asset / cross-regime check — does the same logic hold on a correlated pair or a different period?
Workflow
- Define hypothesis (why should this edge exist?).
- Coarse grid → identify plateau.
- Walk-forward validate the plateau center.
- Paper/forward-test before any capital.
Pairs with [[backtesting-discipline]] (bias-free measurement) and [[risk-management]] (sizing of the result).
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.

