Backtest Expert 0.1.0
v1.0.0Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies...
⭐ 2· 637·21 current·22 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (systematic backtesting guidance) matches the contents of SKILL.md and the reference documents. There are no unrelated requirements (no cloud creds, binaries, or config paths) that would be inconsistent with an educational/methodology skill.
Instruction Scope
SKILL.md contains step-by-step methodology, checks and diagnostics for backtesting and explicitly references the included reference documents. It does not instruct the agent to read arbitrary system files, access environment variables, contact external endpoints, or perform actions outside of advising on testing practices.
Install Mechanism
No install spec or code is included; this is an instruction-only skill. That minimizes surface area because nothing will be downloaded or written to disk by the skill package itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance given does not rely on or request secrets or unrelated service tokens.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not request persistent presence, nor does it ask to modify other skills or system-wide configuration.
Assessment
This skill is an educational, instruction-only package that explains how to run robust backtests and avoid common pitfalls. It does not install software or request credentials, so the package itself is low-risk. Practical notes before you install/use it: 1) The guidance is methodological — the skill cannot run backtests or access your data by itself. If the agent later asks for access to your data files, broker/exchange API keys, or to execute code, treat those requests as separate security decisions and do not share credentials without verifying the destination. 2) Backtesting advice can influence real-money trading decisions; follow recommendations cautiously and validate them in your own environment. 3) Watch for future versions or similar skills that add install scripts, network endpoints, or environment variables — those would require a fresh security review. 4) If you want the agent to perform backtests on your behalf, prefer explicit, auditable workflows (local data files, sandboxed environments, or vetted services) rather than granting broad access.Like a lobster shell, security has layers — review code before you run it.
latestvk97eqjbrmxytg0zgtaykmfsg0181mxfj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.