execution-model

Apply backtest-only slippage, market impact, and execution-delay models to trading backtests.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/GGwujun/SigmX --skill execution-model-ggwujun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-model
Source: https://github.com/GGwujun/SigmX/tree/main/agent/src/skills/execution-model
Command: npx skills add https://github.com/GGwujun/SigmX --skill execution-model-ggwujun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backtest authors often fail to account for real-world execution costs, leading to overly optimistic performance. This skill provides slippage models, market-impact estimation, and execution-delay logic to simulate realistic fills.

Core Features & Use Cases

  • Slippage models: fixed, linear, and square-root to reflect different liquidity conditions.
  • VWAP and TWAP execution logic to mimic intraday order slicing and price attainment.
  • Market-impact cost estimation and configurable execution-assumption parameters to calibrate backtests against historical data.
  • Use Case: A quant testing a large order can compare performance under different execution assumptions to assess robustness.

Quick Start

Load the execution-model and apply a 5bp fixed slippage with a 1-day delay to a sample backtest.

Frequently Asked Questions about execution-model

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

FAQPage Schema
How do I model slippage and market impact in backtested trading strategies?

Model slippage and market impact in backtests by applying configurable fixed, linear, or square-root cost models using explicit volatility, average daily volume, and order size parameters to simulate realistic transaction fills.

What is the difference between VWAP and TWAP execution schemes for backtest cost estimation?

VWAP and TWAP execution schemes simulate intraday order slicing and price attainment differently, allowing you to compare large order performance under varying execution assumptions to assess strategy robustness.

Can I apply execution delay rules to a crypto or equities backtest engine?

Apply execution delay rules to backtests across equities, crypto, and other assets by integrating simple configuration parameters into an existing backtest engine to simulate realistic transaction costs deterministically.

How to configure square-root slippage models for large order backtests?

Configure square-root slippage models by defining explicit parameters for volatility, average daily volume, and order size, then integrate the settings via simple config to estimate market impact costs deterministically.

Why do my backtested trading strategies show overly optimistic performance?

Backtested trading strategies show overly optimistic performance when authors fail to account for real-world execution costs like slippage, market impact, and execution delays, which this modeling approach corrects.

Does backtest slippage modeling require deterministic results across multiple runs?

Backtest slippage modeling requires deterministic results across multiple runs by applying explicit model parameters and fixed execution-delay rules, ensuring consistent quantification of transaction costs.