Diagnose banbot backtest failures across data loading, configuration, and strategy execution.
npx skills add https://github.com/frydaiii/manbot --skill backtest-debug
Please help me install this Agent Skill. Skill: backtest-debug Source: https://github.com/frydaiii/manbot/tree/main/.claude/skills/backtest-debug Command: npx skills add https://github.com/frydaiii/manbot --skill backtest-debug
Banbot backtests can fail to start, produce errors, place no orders, stop early, or behave differently than strategy code expects. This skill provides a structured approach to diagnosing and fixing backtest issues by guiding you through common failure modes and causative checks.
Run this skill to systematically diagnose and fix backtest problems by following the diagnostic decision tree from data and config checks to strat-loading validation.
High-intent search queries and answers about installing and using this skill.
Banbot backtests placing no orders or stopping early often result from data loading gaps, invalid configuration, or run_policy misalignment. You must systematically check BanDataDir, QuestDB data availability, and strategy execution flow to pinpoint the exact failure point.
To debug a banbot backtest that fails to start, validate your configuration settings and ensure QuestDB data availability. Trace the per-bar lifecycle from data provision to order processing to identify where unexpected results originate across different run_policy configurations.
QuestDB data availability directly impacts banbot backtesting by determining whether the required kline data can be loaded. Missing or incomplete data in QuestDB will cause backtests to fail, produce errors, or place zero orders due to empty data feeds.
Ensuring deterministic banbot backtesting results requires enforcing strict checks on BanDataDir, run_policy alignment, TF selection, and wallet or state constraints. Applying clear logging and data validation throughout the strategy execution flow guarantees reproducible outcomes.
Yes, banbot strategy backtesting requires aligning your run_policy configuration and TF selection with the loaded kline data. Mismatches between these settings and the available QuestDB data will cause backtests to fail or yield unexpected results.
When banbot backtest configuration is not working, you should check the validity of your BanDataDir, verify QuestDB kline data availability, and ensure run_policy alignment. Reviewing wallet and state constraints helps resolve execution flow errors and early stops.
questdbCreate and review QuestDB documentation with SQL syntax and quality checks.
20YN04Diagnose and repair algorithmic trading backtest failures by analyzing metrics, equity data, and signal engine code.
mmianiDesign Kotlin Multiplatform data layers with repositories, sources, suspend, and Flow APIs.
644408071-designSimulate slippage, market impact, and execution algorithms for backtesting.
