Backtest Expert
v0.1.0Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
⭐ 17· 8.3k·67 current·72 all-time
byVeera@veeramanikandanr48
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content: all files are methodology and examples for backtesting. The skill requires no binaries, env vars, or config paths — appropriate for a purely advisory/backtesting guidance skill.
Instruction Scope
SKILL.md and reference docs contain procedural guidance (hypothesis, codify rules, stress tests, walk-forward validation). They do not instruct the agent to read local files, access credentials, call external endpoints, or perform actions outside the stated domain.
Install Mechanism
No install spec and no code files — the lowest-risk model. Nothing will be downloaded or written to disk by the skill itself.
Credentials
Requires no environment variables or credentials and does not reference unrelated services. The requested scope of access is minimal and appropriate for a documentation-only skill.
Persistence & Privilege
always is false and the skill does not request or modify persistent agent/system configuration. It does not ask for permanent presence or elevated privileges.
Assessment
This skill is a well-scoped, instruction-only reference for backtesting methodology and appears internally consistent. Before relying on it for trading decisions, remember: (1) the skill provides methodological guidance, not financial guarantees — validate any implementation with your own data and controls; (2) because the skill's source and homepage are unknown, prefer to use it as a checklist and corroborate recommendations with trusted sources or your own code review; and (3) if you later build automation around these rules (code that runs backtests, accesses broker APIs, or handles credentials), review that code and the required environment variables carefully — the present skill does not itself request or manage such credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97f5fb8p94t9rd7q3e3x6s9n9809emn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.