What problem does it solve? Deciding whether a user request belongs to prediction-market analysis and handing it off cleanly is error-prone: routing keys get paraphrased, equity and prediction-market intents get mixed, and terminal specialist output gets overwritten. This Skill gives the Hub explicit rules for detecting prediction-market intent, preserving identifiers, and relaying terminal output verbatim. ## Core Features & Use Cases - Intent Detection: Classifies requests involving Polymarket odds, YES/NO pricing, market discovery, wallet or leaderboard analysis, and prediction-market backtesting, while excluding equity strategy backtesting. - Handoff Discipline: Preserves the user's request verbatim and passes routing keys (market_url, slug, condition_id, token_id) unchanged to prediction_market_analysis. - Terminal Output Relay: Treats prediction_market_analysis as a terminal author, relaying its output directly without Hub-authored summaries, and handling errors without inventing market data. - Use Case: A user asks "Is this 30¢ Polymarket contract mispriced versus historical base rates?" The Hub loads this Skill, routes the request to prediction_market_analysis with prior slugs intact, and relays the specialist's analysis verbatim. ## Quick Start Ask the Hub to compare current Polymarket odds on an event or analyze a specific market by pasting its Polymarket URL.
