backtesting-frameworks

Evaluate trading strategies with event-driven and vectorized backtesting frameworks.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/haxlys/skills --skill backtesting-frameworks-haxlys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backtesting-frameworks
Source: https://github.com/haxlys/skills/tree/main/vendored/wshobson-agents/plugins/quantitative-trading/skills/backtesting-frameworks
Command: npx skills add https://github.com/haxlys/skills --skill backtesting-frameworks-haxlys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build robust, production-grade backtesting systems that avoid common pitfalls and provide reliable estimates of strategy performance for quantitative traders.

Core Features & Use Cases

  • Pattern 1: Event-Driven Backtester: Step through data with orders, fills, and portfolio updates to validate strategies under realistic execution and costs.
  • Pattern 2: Vectorized Backtester: Fast, scalable backtesting with signal generation and cost-aware returns for rapid experimentation.
  • Pattern 3: Walk-Forward Optimization: Evaluate parameter stability across multiple windows to guard against overfitting.
  • Pattern 4: Monte Carlo Analysis: Use bootstrap simulations to assess robustness and drawdown risk.
  • Use cases include testing new trading ideas, validating risk controls, and comparing strategies under realistic costs and assumptions.

Quick Start

Initialize a backtesting workflow that mitigates look-ahead bias, includes costs, and runs a walk-forward assessment.

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 biases in trading strategy backtesting?

Robust backtesting mitigates look-ahead and survivorship biases by enforcing deterministic execution and using structured data inputs, ensuring accurate evaluation of trading strategies without inflating historical performance.

What is the difference between event-driven and vectorized backtesting frameworks?

Event-driven backtesting steps through data with orders, fills, and portfolio updates for realistic execution, while vectorized backtesting provides fast, scalable signal generation and cost-aware returns for rapid experimentation.

How do I use walk-forward optimization and Monte Carlo simulations to test trading strategies?

Walk-forward optimization evaluates parameter stability across multiple windows to guard against overfitting, while Monte Carlo analysis uses bootstrap simulations to assess strategy robustness and drawdown risk.

Can I incorporate realistic transaction costs and custom cost models into a backtest?

Yes, the backtesting framework supports clear cost models and cost-aware returns to evaluate strategies under realistic transaction costs and assumptions, providing reliable estimates of actual trading performance.

Does this backtesting framework require specific dependencies or external libraries?

No, the backtesting framework has no external dependencies. It relies on a modular design and extensible pattern implementations to deliver reproducible results without requiring specific external libraries.