backtest

Run backtests against the Udgaard API and save trade-by-trade results.

Updated Jun 10, 2025
One-click install
npx skills add https://github.com/skrymer/trading --skill backtest-skrymer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backtest
Source: https://github.com/skrymer/trading/tree/main/.claude/skills/backtest
Command: npx skills add https://github.com/skrymer/trading --skill backtest-skrymer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run backtests against the Udgaard API to evaluate strategy performance, capture trade-by-trade results, and delegate post-backtest analysis to the post-backtest-analyst for risk metrics and SPY correlation insights.

Core Features & Use Cases

  • Discovery endpoints for strategies, conditions, and rankers to configure tests.
  • Supports multiple entry/exit strategies, position sizing, ranking, and scenarios including walk-forward and Monte Carlo analyses.
  • Automatically saves raw backtest responses and routes results to a dedicated analyst for interpretation.

Quick Start

Post a JSON payload to the Udgaard /api/backtest endpoint to run a backtest and review the saved raw results.

Frequently Asked Questions about backtest

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

FAQPage Schema
How do I backtest trading strategies against historical stock data?

The backtest process evaluates entry and exit strategies against historical stock data via the Udgaard API. It captures trade-by-trade results, saves raw responses to disk, and delegates deeper risk metric analysis to a dedicated post-backtest analyst agent.

Can I run Monte Carlo and walk-forward analyses on trading strategies?

Walk-forward and Monte Carlo analyses are supported scenarios within the backtest framework. You can configure these tests using custom DSL strategies, position sizing, and ranking options to evaluate strategy robustness across historical stock data.

What do I need to configure before running a backtest via the API?

Running a backtest requires posting a payload with assetTypes, entryStrategy, exitStrategy, dates, and sizing or ranking options to the API endpoint. Discovery endpoints are available to help find and configure available strategies, conditions, and rankers.

How are backtest results analyzed after the API run completes?

After a backtest run, raw responses are saved to disk and delegated to a post-backtest analyst agent. This agent provides deeper interpretation of the results, calculating risk metrics and SPY correlation insights for the tested strategies.

Does the backtest framework support custom DSL strategies?

Custom DSL strategies are supported for defining entry and exit logic in the backtest framework. You can combine these custom strategies with position sizing, ranking options, and multiple scenarios to test specialized trading rules across historical data.

What are the limitations of backtesting trading strategies with historical data?

The backtest framework is limited to stock assets within configurable time ranges and requires valid API endpoint access. While it captures detailed trade-by-trade results, deeper risk metric and SPY correlation analysis is delegated to a separate post-backtest analyst agent.