backtest-integrity

Validate trading strategy backtest results for overfitting and sample size issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lgbarn/quantdev --skill backtest-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backtest-integrity
Source: https://github.com/lgbarn/quantdev/tree/main/skills/backtest-integrity
Command: npx skills add https://github.com/lgbarn/quantdev --skill backtest-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical issue of backtest unreliability by automatically flagging potential overfitting, insufficient data, and missing validation, thereby preventing the deployment of flawed trading strategies.

Core Features & Use Cases

  • Metric Red Flagging: Identifies unrealistic Sharpe Ratios, Win Rates, and Profit Factors.
  • Sample Size Validation: Warns if trade counts are too low for statistical significance.
  • Out-of-Sample & Walk-Forward Checks: Enforces rigorous validation protocols.
  • Use Case: When reviewing a backtest with a Sharpe Ratio of 4.0, this Skill will immediately flag it as "CRITICAL" and require out-of-sample validation before it can be considered reliable.

Quick Start

Analyze the provided backtest results for potential integrity issues.

Frequently Asked Questions about backtest-integrity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my backtesting results are reliable or overfitted?

To check backtesting reliability, you must validate strategy performance metrics to identify overfitting, insufficient sample sizes, and missing out-of-sample validation. Applying a red flag checklist to unrealistic metrics like a high Sharpe Ratio ensures confidence in trading strategy results.

What is a critical red flag in trading strategy performance metrics?

A critical red flag in trading strategy performance metrics is an unrealistic Sharpe Ratio, Win Rate, or Profit Factor. For example, a backtest with a Sharpe Ratio of 4.0 is flagged immediately as critical and requires out-of-sample validation before deployment.

How do I validate out-of-sample and walk-forward test results?

You validate out-of-sample and walk-forward test results by enforcing rigorous validation protocols. This includes applying a mandatory annotation protocol and confidence ratings to ensure statistical significance and prevent deploying flawed trading strategies.

Why does my trading strategy backtest fail sample size validation?

Backtest sample size validation fails when trade counts are too low to achieve statistical significance. Warning flags are triggered to indicate insufficient data, ensuring that performance metrics lack the mathematical confidence required for reliable strategy assessment.

Can I use automated validation to flag unrealistic backtest performance metrics?

Yes, you can use automated validation to flag unrealistic backtest performance metrics. The process applies a red flag checklist to automatically identify overfitting and missing out-of-sample data, requiring adherence to confidence ratings before results are considered reliable.

When do I need out-of-sample validation for a trading strategy backtest?

You need out-of-sample validation for a trading strategy backtest whenever performance metrics trigger critical red flags, such as an unrealistic Sharpe Ratio. This validation step is mandatory to ensure confidence and prevent the deployment of flawed, overfitted strategies.