Keel

backtest-and-analyze

Run a backtest on an existing strategy and read it: confirm the strategy, run on the strategy's default window unless the user named one, watch to terminal, present the run's view, and interpret the mechanism behind the result. Use when the user says "run a backtest", "test this", "how does it perform", "what's the Sharpe", or names a strategy and asks about performance. Not for robustness checks (overfit-check) or for editing the strategy.

component-discovery

Find the Keel component(s) that implement a concept the user names: search by concept, batch the candidates' schemas, show what precedes and follows the best one. Use when the user asks "what component does X", "is there a way to Z", "find a component for Y", or names a trading concept and wants what implements it. Not for composing a strategy (strategy-creation) or for one already-named component (keel_components_get).

overfit-check

Probe whether a backtest result is robust or curve-fit: re-run the strategy on disjoint windows and regimes the user agrees to, optionally perturb the sensitive parameters, compare the runs once, and give one verdict (ROBUST / MIXED / OVERFIT). Use when the user asks "is this real?", "is this overfit?", "out-of-sample", "walk-forward", or asks for a robustness check; the check is most informative on an unusually strong in-sample result (Sharpe above 3.0, return above 500%). Not a substitute for the first backtest (backtest-and-analyze).

portfolio-review

Summarise the strategies running on the user's account, read-only: positions, recent fills, drawdown against backtest expectations, and anything errored or stale. It changes nothing; starting or stopping a strategy happens in the Keel web app. Use when the user asks "how are my strategies doing", "what's running", "portfolio status", or asks about several running strategies at once. Not for backtesting a candidate (backtest-and-analyze).

recover-from-error

Triage repeated keel_* tool failures: capture the errors, read keel_account_status and keel_connection_check, classify by the error's code (auth, scope, quota, sync, validation rule, handoff), and propose one specific next step. Use when the user says "this keeps failing", "what's wrong", "debug this", or pastes an error. Not for a single failure — the originating tool's error already says what to do.

strategy-creation

Author a new Keel strategy from a natural-language thesis: fix path, universe and polarity; search every concept; batch-verify component types; draft the declarations and one Pipeline; dry-run until clean; save; and, when the user wants one, backtest and read the result. Use when the user says "create / build / make me a strategy", "new strategy that ...", or describes a trading idea and wants it implemented. Not for editing an existing strategy (strategy-fork-and-iterate) or for looking up one component (component-discovery).

strategy-fork-and-iterate

Change an existing strategy with one focused edit: the user's own strategy takes the change as its next version (earlier versions and their backtests stay in its history); a shared link or a Keel Library entry is forked first. Read the whole source, choose the smallest edit that meets the intent, dry-run, save once per user-visible step, explain the change view. Use when the user names a strategy and asks for a change, or says "fork", "based on", "like that but ...", "import this share link", "start from the library". Not for authoring from scratch (strategy-creation) or for merely reading a strategy (keel_strategy_get).