backtest
Skill4 starsChanged 6 days agoMITView on GitHub
Runs historical and pseudo-real-time backtests with information-set checks and regime-specific performance.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- cecewu3/agent-trading-skillstheir own version, first seen Nov 8, 2026
- Seth090502/osanwe-publictheir own version, first seen Oct 20, 2026
- upbit-official/upbit-strategy-toolkittheir own version, first seen Jul 13, 2026
- marketcalls/vectorbt-backtesting-skillstheir own version, first seen Jul 12, 2026
- Starchild-ai-agent/official-skillstheir own version, first seen May 21, 2026
- jackson-video-resources/skillstheir own version, first seen May 14, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- marketcalls/vectorbt-backtesting-skills★ 200same name
- Starchild-ai-agent/official-skills★ 32same name
- jackson-video-resources/skills★ 17same name
- upbit-official/upbit-strategy-toolkit★ 8same name
- Vaibhavkkm/vkkm-aegis-plugin★ 2same name
- cecewu3/agent-trading-skills★ 0same name
- Seth090502/osanwe-public★ 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 repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- build-abmSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- equivalence-testSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 47
Verify no look-ahead with automated checks
- Distinctive: line 48
Check features, scaling, filters, hyperparameters and data vintages
- Distinctive: line 49
Run the backtest; compute point and density scores against naive benchmarks
- Distinctive: line 54
After design: confirm windows, horizons and regimes
- Distinctive: line 55
After results: confirm interpretation for use decisions
- Distinctive: line 72
Use of non-real-time data is stated where vintages are unavailable
“Common” is measured: kept by at least 6 in 10 of the 7 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
<!-- Generated from .claude/skills/backtest/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/backtest — Backtest
Category: Validation & QA · Primary agent: backtesting-specialist
Runs historical and pseudo-real-time backtests with information-set checks and regime-specific performance.
Arguments: whatever the user wrote after the command name.
Purpose
Backtest a model, forecast method, risk model or policy rule: how would it have performed if it had been used in the past with only the information then available? The output reports point and density performance against naive benchmarks, separately for calm and stress periods, with automated proof that no future information leaked in.
Use it when a forecaster, nowcaster, risk model or scenario generator is being validated or compared, or a policy rule's historical performance is in question.
Do not use it when the question is conceptual soundness of a structural model (/validate-model).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Model code
- Data vintages
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
backtesting-specialist— primary agent; coordinates the work and integrates resultsforecast-evaluation-specialist— Evaluates forecasts
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
| Window | rolling, expanding | Adaptation versus stability |
| Data | real-time vintages, latest vintage with caveat | Realism of the test |
| Re-estimation | every origin, periodically, never | Practical realism |
| Scores | RMSE, MAE, log score, CRPS, coverage | What "good" means |
| Regimes | recessions, crises, high inflation | Stress-period evidence |
Workflow
- Define windows, horizons and the information set at each origin
- Verify no look-ahead with automated checks
- Check features, scaling, filters, hyperparameters and data vintages
- Run the backtest; compute point and density scores against naive benchmarks
- Equal-accuracy tests suited to nested or non-nested models
- Report calm vs. stress-period performance
Checkpoints with the user
- After design: confirm windows, horizons and regimes
- After results: confirm interpretation for use decisions
Common pitfalls
- Final-vintage data treated as real time
- Tuning on the full sample
- Averages only
- Overstating small, insignificant differences
Output
validation/<model>/backtest-report.md
The report documents the design, look-ahead checks, scores versus benchmarks with tests, and performance by regime.
Gate / verdict
- No look-ahead verified
- Benchmarks included
- Significance tests accompany comparisons
- Use of non-real-time data is stated where vintages are unavailable
Suggested next steps
/validate-model/forecast-round
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.

