backtest-diagnose

Diagnose and repair failed algorithmic trading backtests by analyzing artifacts and source code.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/0xZKnw/vibe-trading-tap --skill backtest-diagnose-0xzknw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backtest-diagnose
Source: https://github.com/0xZKnw/vibe-trading-tap/tree/main/agent/src/skills/backtest-diagnose
Command: npx skills add https://github.com/0xZKnw/vibe-trading-tap --skill backtest-diagnose-0xzknw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves failures and performance anomalies in trading backtests by systematically diagnosing runtime errors, logic bugs, and data issues.

Core Features & Use Cases

  • Automated Diagnosis: Classifies issues into runtime errors, logic bugs, or data-source problems using a structured taxonomy.
  • Precision Repair: Provides targeted code edits for signal engines to fix issues like zero trades, late entries, or NaN propagation.
  • Validation: Ensures all fixes pass AST syntax checks and verify results through automated backtest reruns.

Quick Start

Ask the agent to diagnose the current backtest failure by analyzing the metrics and signal engine code.

Frequently Asked Questions about backtest-diagnose

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

FAQPage Schema
How do I debug a trading backtest that produces zero trades?

Diagnose zero-trade backtests by analyzing signal engine logic and data filtering to identify entry condition failures. The skill classifies issues into runtime errors, logic bugs, or data-source problems and provides targeted code edits to repair signal generation.

Why does my algorithmic trading backtest fail with NaN propagation errors?

Algorithmic trading backtest failures with NaN propagation stem from data-source problems or logic bugs. The skill diagnoses these runtime errors by analyzing artifacts and source code, then applies precision repairs to signal engines to prevent NaN propagation.

What is the best way to fix late entry signals in a Python backtest?

Fixing late entry signals requires diagnosing logic bugs within the signal engine and data filtering rules. The skill repairs failed algorithmic trading backtests by providing targeted code edits and verifying results through automated backtest reruns.

Can I use automated diagnosis to fix runtime errors in algorithmic trading backtests?

Automated diagnosis fixes runtime errors in algorithmic trading backtests by classifying issues using a structured taxonomy. The skill analyzes backtest artifacts and source code to provide precision repairs and ensures fixes pass AST syntax checks and backtest reruns.

How do I validate backtest fixes after repairing signal engine logic?

Validate backtest fixes by running automated backtest reruns and AST syntax checks on the repaired signal engine code. The skill ensures backtest integrity and performance by iteratively validating that the targeted code edits resolve the diagnosed issues.