QuantConnect Validation
QuantConnect walk-forward validation and Phase 5 robustness testing (project)
Profile →npx skills add majiayu000/claude-skill-registry --skill quantconnect-validation-derekcrosslu-claude-code-explore-9b11f2c --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# QuantConnect Validation Skill (Phase 5) **Purpose**: Walk-forward validation for Phase 5 robustness testing before deployment. **Progressive Disclosure**: This primer contains essentials only. Full details available via `qc_validate.py docs` command. --- ## When to Use This Skill Load when: - Running `/qc-validate` command - Testing out-of-sample performance - Evaluating strategy robustness - Making deployment decisions **Tool**: Use `python SCRIPTS/qc_validate.py` for walk-forward validation --- ## Walk-Forward Validation Overview **Purpose**: Detect overfitting and ensure strategy generalizes to new data. **Approach**: 1. **Training (in-sample)**: Develop/optimize on 80% of data 2. **Testing (out-of-sample)**: Validate on remaining 20% 3. **Compare**: Measure performance degradation **Example** (5-year backtest 2019-2023): - In-sample: 2019-2022 (4 years) - Training period - Out-of-sample: 2023 (1 year) - Testing period --- ## Key Metrics ### 1. Performance Degradation **Formula**: `(IS Sharpe - OOS Sharpe) / IS Sharpe` | Degradation | Quality | Decision | |-------------|---------|----------| | < 15% | Excellent | Deploy with confidence | | 15-30% | Acceptable | Deploy but moni
- When to Use This Skill
- Walk-Forward Validation Overview
- Key Metrics
- 1. Performance Degradation
- 2. Robustness Score
- Quick Usage
- Run Walk-Forward Validation
- Analyze Results
- Decision Integration
- Best Practices
- 1. Time Splits
- 2. Never Peek at Out-of-Sample
- 3. Check Trade Count
- 4. Compare Multiple Metrics
From hypothesis directory with iteration_state.json python SCRIPTS/qc_validate.py run --strategy strategy.py Custom split ratio (default 80/20) python SCRIPTS/qc_validate.py run --strategy strategy.py --split 0.70 python SCRIPTS/qc_validate.py analyze --results PROJECT_LOGS/validation_result.json python SCRIPTS/qc_validate.py --help
What does the QuantConnect Validation skill do?
QuantConnect walk-forward validation and Phase 5 robustness testing (project)
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill quantconnect-validation-derekcrosslu-claude-code-explore-9b11f2c --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.