backtesting-frameworks

Generate bias-resistant backtests on historical OHLCV data with walk-forward optimization.

6|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/archibate/archibate-skills --skill backtesting-frameworks-archibate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backtesting-frameworks
Source: https://github.com/archibate/archibate-skills/tree/main/old-skills/minor-skills/backtesting-frameworks
Command: npx skills add https://github.com/archibate/archibate-skills --skill backtesting-frameworks-archibate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backtesting-frameworks provides structured, bias-aware methods to evaluate trading strategies so you can trust historical performance estimates and avoid common pitfalls like look-ahead bias, survivorship bias, and ignored transaction costs.

Core Features & Use Cases

  • Event-driven and vectorized backtesting: Choose between detailed order-level simulation or fast vectorized execution for large datasets.
  • Walk-forward optimization and validation: Automate train/validation/test splits and rolling or anchored walk-forward analyses to prevent overfitting.
  • Robustness analysis: Run Monte Carlo or bootstrap simulations, calculate comprehensive performance metrics, and incorporate slippage and commission models.
  • Use Case: Validate a momentum strategy on daily OHLCV data, optimize parameters on rolling training windows, and produce an equity curve with realistic trading costs and max-drawdown estimates.

Quick Start

Run a backtest of your strategy on historical OHLCV data including point-in-time handling, realistic slippage and commission, and a walk-forward validation pass.

Frequently Asked Questions about backtesting-frameworks

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

FAQPage Schema
How do I prevent look-ahead and survivorship bias in backtesting?▼

Backtesting requires point-in-time data handling and bias-resistant methods to prevent look-ahead and survivorship bias. You can eliminate these biases by applying structured validation to historical OHLCV datasets.

What is walk-forward optimization for trading strategies?▼

Walk-forward optimization is a validation method that automates train/validation/test splits on rolling windows. It prevents overfitting by ensuring trading strategy parameters are validated out-of-sample.

How do I run a Monte Carlo simulation on OHLCV backtest results?▼

Monte Carlo simulation for backtesting generates robustness checks by running bootstrap simulations on historical OHLCV data. This produces comprehensive performance metrics and max-drawdown estimates.

Does vectorized backtesting support realistic slippage and commission models?▼

Vectorized backtesting supports realistic slippage and commission models for fast execution on large datasets. You can choose between this and event-driven order-level simulation for detailed cost analysis.

How do I validate a momentum strategy with out-of-sample testing?▼

Validating a momentum strategy with out-of-sample testing involves splitting historical OHLCV data into training and testing windows. Walk-forward optimization automates this process to produce reliable equity curves.

Why does my backtest equity curve ignore transaction costs?▼

Backtest equity curves ignore transaction costs when slippage and commission models are not applied. Incorporating realistic trading costs during point-in-time data handling ensures accurate max-drawdown estimates.