execution-model

Model trade execution assumptions with slippage, impact, delay, and cost breakdowns.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/JacobHsu/vibe-trading-agent --skill execution-model-jacobhsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-model
Source: https://github.com/JacobHsu/vibe-trading-agent/tree/main/agent/src/skills/execution-model
Command: npx skills add https://github.com/JacobHsu/vibe-trading-agent --skill execution-model-jacobhsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill makes your backtests credible by modeling slippage, market impact, execution delay, and transaction costs so that strategy performance does not overfit an idealized market.

Core Features & Use Cases

  • Granular slippage models let you select fixed, linear, or square-root formulas with recommended coefficients per market segment.
  • Execution algorithm principles capture VWAP/TWAP pacing, T+1 delay rules, volume filters, and signal buffering for different markets.
  • Cost and sensitivity analysis provides explicit and implicit cost tables, decision trees, and narrative guidance to test how fees and spreads drag returns, such as evaluating a monthly China A-share rebalance under 5bps versus 10bps slippage.

Quick Start

Use the execution-model skill to apply market-impact slippage and VWAP execution assumptions before running your daily backtest.

Frequently Asked Questions about execution-model

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

FAQPage Schema
How do I add realistic slippage and market impact to my backtest?

You can model execution delay by applying T+1 delay rules and signal buffering to handle delayed signals consistently in overnight markets. This ensures your backtest accurately reflects when trades are actually executed rather than assuming instant fills.

How do I model execution delay and T+1 rules in a daily backtest?

You can model execution delay by applying T+1 delay rules and signal buffering to handle delayed signals consistently in overnight markets. This ensures your backtest accurately reflects when trades are actually executed rather than assuming instant fills.

What is the best way to simulate VWAP and TWAP execution slicing in a backtest?

The best way to simulate VWAP and TWAP execution slicing is to apply execution algorithm principles that capture volume filters and pacing rules. This models how large orders are split over time to minimize market impact during your strategic trading backtest.

Can I analyze how different transaction costs and slippage rates drag backtest returns?

Yes, you can analyze how transaction costs drag returns by generating explicit and implicit cost tables and running sensitivity analysis. This lets you compare strategy performance under different slippage scenarios, such as 5bps versus 10bps for a monthly rebalance.

Does execution modeling work for China A-share backtests with overnight market rules?

Execution modeling supports China A-share backtests by applying T+1 delay rules, volume filters, and configurable slippage formulas tailored to specific market segments. This provides accurate transaction cost breakdowns for overnight and delayed signal handling.