What problem does it solve? Deciding whether a user request belongs to Coinbase spot crypto analysis—and how to hand it off without losing context—is error-prone. This Skill defines exactly when to route crypto market data, backtesting, and artifact follow-up requests to the crypto_analysis specialist, and how to handle its terminal output. ## Core Features & Use Cases - Routing Decisions: Directs Coinbase spot product lookup, OHLCV, order book, latest trade, and bid/ask requests to crypto_analysis, while excluding equities, options, Polymarket, DeFi, and derivatives. - Handoff Discipline: Preserves the user's request verbatim and passes only factual resolved context such as product IDs, timeframes, strategy rules, and prior job IDs or artifact fingerprints. - Terminal Output Handling: Relays marked __TERMINAL_TOOL_OUTPUT__:crypto_analysis: results unchanged, and answers MISSING_CRYPTO_INPUTS: pre-flight signals directly without repeating the call. - Use Case: A user asks to backtest a mean-reversion strategy on BTC-USD with a 1.5% stop over the last year; the Hub routes the request to crypto_analysis with the resolved product ID and relays the specialist's terminal output verbatim. ## Quick Start Ask the Hub to backtest a Coinbase spot strategy or fetch crypto market data, for example: backtest an RSI mean-reversion strategy on BTC-USD over the past year.
