skills.rest
xingwudao
xingwudaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

audit-runtime-semantics

Audit compiled quant strategy runtime plans against original specifications.

116|38|Updated Feb 26, 2026
Search Tags:#quant-research#runtime-audit#open-xquant#backtest-validation#strategy-compilation#execution-semantics#reproducible-backtest
One-click install
npx skills add https://github.com/xingwudao/open-xquant --skill audit-runtime-semantics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-runtime-semantics
Source: https://github.com/xingwudao/open-xquant/tree/main/agent/skills/audit-runtime-semantics
Command: npx skills add https://github.com/xingwudao/open-xquant --skill audit-runtime-semantics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a quant strategy is compiled from its declarative spec into a runtime plan, silent changes to execution semantics (like rebalance intervals, fee structures, or fill pricing) can make backtest results completely invalid and untrustworthy for trading decisions. This skill eliminates that risk by rigorously comparing material runtime fields between the original spec and compiled plan before any backtest is run.

Core Features & Use Cases

  • Compile Preview Generation: Creates a deterministic compile preview of the strategy spec using the exact same inputs as the formal backtest to ensure consistency.
  • Material Runtime Field Auditing: Checks critical execution parameters including rebalance frequency, execution timing, fee/slippage settings, validation periods, and initial cash values for mismatches or omissions.
  • Backtest Gating: Blocks formal backtest execution if any material runtime semantics are altered or missing, preventing wasted compute on invalid results and ensuring only reproducible, trustworthy backtests are run.
  • Use Case: A quant researcher using open-xquant can run this skill after validating their strategy spec to catch cases where the compiler silently changes a 10-day rebalance interval to a daily interval, which would completely invalidate their backtest performance metrics.

Quick Start

Use the audit-runtime-semantics skill to validate that your compiled strategy plan matches the original spec before running a formal backtest.

Frequently Asked Questions about audit-runtime-semantics

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

FAQPage Schema
How do I verify execution semantics in a compiled quant strategy before running a backtest?▼

You verify execution semantics in a compiled quant strategy by auditing the runtime plan against the original strategy spec to detect mismatches in rebalance intervals, fee structures, or execution timing before backtest execution.

What causes invalid backtest results when compiling a quant strategy spec into a runtime plan?▼

Invalid backtest results occur when the compilation process silently alters or omits critical runtime parameters, such as changing a 10-day rebalance interval to a daily interval or dropping fill pricing settings from the original strategy spec.

How do I block formal backtest execution if compiled runtime parameters contradict the original spec?▼

You block formal backtest execution by implementing a gating mechanism that compares material runtime fields between the strategy spec and compiled plan, stopping execution when critical parameters like initial cash values or validation periods are missing or altered.

Does open-xquant support deterministic backtest validation for quant research workflows?▼

Yes, open-xquant supports deterministic backtest validation by generating a compile preview using the exact same inputs as the formal backtest, ensuring that material runtime semantics are preserved and reproducible backtests are gated correctly.

What specific runtime parameters should I audit for reproducible backtests?▼

You should audit rebalance frequency, execution timing, fee and slippage settings, validation periods, and initial cash values to ensure the compiled strategy plan preserves all material execution semantics from the source specification.

When should I run a runtime semantics audit in a quant research pipeline?▼

You should run a runtime semantics audit between strategy spec validation and formal backtest execution, ensuring the compiled plan matches the source spec before any compute resources are spent generating performance metrics.

Related Skills

Explore More Finance & Accounting Skills→
ahastudioahastudio
186

analyze-article

Fetch a web article and generate a Korean TIL document with summary, analysis, critique, and insights.

Community
Advanced
xingwudaoxingwudao
116

run-authorized-backtest

Execute authorized quant backtests with provenance tracking and post-run validation.

Community
Advanced
xingwudaoxingwudao
116

monitor-strategy-run

Audit open-xquant backtest runs and generate integrity reports.

Community
Advanced
xingwudaoxingwudao
116

configure-trade-execution

Configure open-xquant strategy execution parameters including fees, slippage, and lot size.

Community
Intermediate