backtesting-frameworks

Implement and validate backtesting frameworks for quantitative trading strategies.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill backtesting-frameworks-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backtesting-frameworks
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/quantitative-trading/skills/backtesting-frameworks
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill backtesting-frameworks-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Construct robust, production-grade backtesting frameworks for quantitative trading strategies, ensuring reliable performance estimates without look-ahead bias.

Core Features & Use Cases

  • Event-driven backtesting: simulate trades on real-time data with costs, slippage, and fills.
  • Vectorized backtesting: high-speed evaluation across large datasets using simple signal models.
  • Walk-forward optimization: establish robust parameter selection with anchored or rolling windows.
  • Risk and performance analysis: compute metrics like Sharpe, drawdown, and win rate to compare strategies.

Quick Start

Run a sample backtest by supplying historical data and a simple signal function to generate an initial equity curve.

Frequently Asked Questions about backtesting-frameworks

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

FAQPage Schema
How do I build a backtesting framework without look-ahead bias?

To build a backtesting framework without look-ahead bias, implement point-in-time data handling and use event-driven or walk-forward processing to ensure historical market data is evaluated strictly sequentially.

How do I run a vectorized backtest on historical market data?

Run a vectorized backtest by supplying historical market data and a simple signal function to the framework, which generates an initial equity curve through high-speed evaluation across large datasets.

What is walk-forward optimization in quantitative trading?

Walk-forward optimization in quantitative trading establishes robust parameter selection by testing strategies across anchored or rolling windows, ensuring parameters remain valid outside their original training periods.

How do I account for transaction costs and slippage in a backtest?

Account for transaction costs and slippage in a backtest by using event-driven simulation, which models real-time data execution with realistic fills, costs, and market impact to ensure reliable performance estimates.

Can I use Monte Carlo analysis to assess trading strategy risk?

Yes, you can use Monte Carlo analysis within a backtesting framework to assess trading strategy risk by simulating numerous randomized equity curve paths to evaluate the robustness of performance metrics.

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

Event-driven backtesting simulates trades sequentially with realistic costs and slippage, while vectorized backtesting performs high-speed evaluation across large datasets using simple signal models for faster initial equity curve generation.