← ClaudeAtlas

backtest-a-rulelisted

Backtest a trading rule the user describes in words on QuanterLab and say plainly whether it beat simply holding the stock. Use when the user wants to test, check or backtest a strategy on a stock or ETF, asks "would this have worked", or names a rule such as an RSI level, a moving-average crossover or a breakout on a ticker.
quanterlab-ug/quanterlab-claude-plugin · ★ 0 · AI & Automation · score 72
Install: claude install-skill quanterlab-ug/quanterlab-claude-plugin
# Backtest a rule ## When QuanterLab is not connected yet This skill works through QuanterLab's connector (`https://quanterlab.com/mcp`). If none of its tools is available in this conversation (no `get_started`, no `search`, no `start_test`), the person has the plugin but has not signed in to QuanterLab yet. Do not answer from memory and do not make up a result. Say in one sentence that QuanterLab has to be connected once, and how: in Claude, open this plugin's page, press Connect on the QuanterLab connector and sign in; in Claude Code, run `/mcp`, choose quanterlab and sign in. Signing in makes a QuanterLab account; a new account starts with a free trial and no card is asked for. Then offer to run what they asked as soon as it is connected, and stop there. The user has an idea. Turn it into one clear rule, run it on QuanterLab straight away, and tell them what happened in words they can act on. ## 1. Run first A request that names no stock and no rule, whatever its verb (make a backtest, test something, show me what it does), is never filled in with defaults: call `get_started`, which shows three setups from QuanterLab's Library, and play its first one at once with its `call`. It plays from its stored result and uses none of the user's runs. Ask nothing before the first run. What the request leaves open gets a sensible default: - the ticker: a US stock or ETF, such as SPY or AAPL; SPY when a rule is named without a stock; - the entry rule and the exit rule (an exit ca