Progressive Validator
v1.0.1Multi-stage backtest validation framework — fail fast with short windows (smoke/stress/medium/full) before committing to expensive full-period backtests, sav...
⭐ 0· 119·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included code and SKILL.md. The validator implements stage orchestration, local result persistence, and command suggestion for an external backtest CLI (backtest-poller). Required binary (python3) is appropriate and proportionate.
Instruction Scope
SKILL.md and validator.py confine actions to suggesting commands, recording stage results, and printing status. They do not read unrelated system files or environment variables. However, the runtime instructions assume you will execute an external script (../backtest-poller/cli.py); executing that script is outside this skill and could run arbitrary code if the external CLI is untrusted.
Install Mechanism
No install spec or remote downloads. The package is delivered as code files (validator.py, config example) and a requirements.txt declaring no dependencies. Nothing is written to disk by an installer beyond the user's explicit run of the script.
Credentials
The skill requests no environment variables or credentials and the code does not access secrets. The only external dependency is the backtest-poller CLI (path is user-specified); ensure that CLI is the legitimate tool you expect before running suggested commands.
Persistence & Privilege
The skill persists validation_results.json (configurable) in the current working directory and will overwrite if present. It does not request persistent platform privileges nor set always:true. Running in an isolated/workspace directory is recommended to avoid accidental file overwrite.
Assessment
This skill appears coherent and self-contained: it orchestrates backtest stages and stores local results. Before using it, (1) inspect validator.py yourself (it is included) and confirm you are comfortable with it writing validation_results.json in your working directory, (2) only run the suggested backtest submission command if your backtest-poller CLI is the legitimate tool you installed (don’t run a sibling ../backtest-poller/cli.py from an untrusted location), and (3) run the tool in an isolated directory or under version control to avoid accidental overwrite of files. If you want extra assurance, run the script in a disposable environment or review the backtest-poller code it calls.Like a lobster shell, security has layers — review code before you run it.
latestvk9760fncfvhnz49at89183db7n8326ta
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎯 Clawdis
Binspython3