菜单
Use when the user asks about Coinbase spot crypto products, crypto OHLCV, crypto order books, latest crypto trades or bid/ask, Coinbase spot strategy backtests, crypto strategy artifacts, or follow-ups on prior crypto backtests or artifacts. Excludes equities, options, Polymarket, DeFi, on-chain, and derivatives.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Central router for OBaI's MCP servers. Trigger this skill whenever the user asks a financial-markets question and the OBaI MCP servers (localhost ports 8001-8010) are available: stock prices, quotes, technicals, fundamentals, valuation, SEC filings, insider trades, earnings, dividends, news catalysts, options chains and Greeks, stock screening, portfolio analysis, ETF holdings, treasury rates, trading-strategy design and backtesting, qualitative company research, Polymarket prediction markets, or Coinbase spot crypto. This skill maps the question to the right OBaI specialist skill and MCP server, then enforces grounding and synthesis rules. Read the matching specialist skill before calling that server's tools.
Real-time and historical stock market data via the OBaI market-data MCP server (http://localhost:8002/mcp). Use for current prices, quotes, OHLCV candles, technical indicators (RSI, SMA, EMA, ADX), market movers, sector snapshots, pre/after-hours quotes, short volume, market hours, and commodity/futures prices (gold, oil, gas). Read before calling any market_data_* tool.
Use the OBaI CLI to answer financial and stock market questions by running `obai query` commands with `--session` for conversation memory. Trigger this skill whenever the user asks about stock prices, earnings, fundamentals, options, market movers, portfolio analysis, portfolio risk, screening, dividends, SEC filings, insider trades, backtesting strategies, commodity or futures prices, company deep dives, competitive positioning, management quality, product sentiment, thematic research, or any financial market question. The agent should autonomously run `obai query "<question>" --json --session <id>`, parse the JSON output, and present the answer — without asking the user to run commands themselves. Always use --session to maintain context across related queries. Also trigger when the user asks to check OBaI server health, run evaluations, or compare stocks.
Autonomous paper trading bot that manages a stock portfolio on Alpaca's paper trading platform. Use this skill when the user asks to: run the daily trading routine, check the portfolio or account status, execute or close trades, evaluate strategy signals, screen stocks, get technical analysis, review trading performance, deploy a new strategy, run portfolio risk analysis, or validate strategy robustness. Trigger on mentions of paper trading, Alpaca, autotrader, buy/sell stocks, portfolio check, market hours, risk limits, strategy signals, or daily routine.
Coinbase spot crypto research via the OBaI crypto MCP server (http://localhost:8010/mcp). Use for Coinbase spot product lookup, crypto OHLCV candles, order books, latest trades and bid/ask, single-product spot strategy backtests, and Coinbase paper-ledger strategy artifacts. Excludes derivatives, DeFi, on-chain analysis, other exchanges, and live order placement. Read before calling any crypto_* tool.
Polymarket prediction-market analysis via the OBaI prediction-markets MCP server (http://localhost:8009/mcp). Use for market discovery, event odds, YES/NO executable pricing and depth, price history, trade flow, holder concentration, trader leaderboards, wallet analysis, trade decision memos, calibration/longshot-bias analysis, rule backtests, edge estimation, and Kelly sizing. Excludes equity strategy backtesting (use obai-strategy). Read before calling any prediction-market tool.
| name | obai-crypto-routing |
| description | Use when the user asks about Coinbase spot crypto products, crypto OHLCV, crypto order books, latest crypto trades or bid/ask, Coinbase spot strategy backtests, crypto strategy artifacts, or follow-ups on prior crypto backtests or artifacts. Excludes equities, options, Polymarket, DeFi, on-chain, and derivatives. |
Use this skill before crypto_analysis when the request depends on Coinbase spot crypto market data, Coinbase spot backtesting, internal Coinbase paper-ledger artifacts, or a follow-up on prior crypto output.
Route to crypto_analysis for:
Do not route here for:
If crypto and equity intent are mixed, route each to its specialist in separate turns. Crypto terminal output controls final rendering once crypto_analysis fires.
Preserve the user's request verbatim. Pass only factual Hub-resolved context:
Do not invent missing strategy rules, dates, fees, risk caps, or unsupported provider data. Do not translate Coinbase spot intent into another venue.
For ambiguous symbols or asset names, either pass the ambiguity to crypto_analysis or call it with the user's original query so it can use crypto_resolve_symbol.
crypto_analysis is a terminal author. The runtime emits the specialist output directly and discards Hub-authored text after the tool returns.
If the tool result starts with __TERMINAL_TOOL_OUTPUT__:crypto_analysis:, treat the first line as a control marker. Everything after the first blank line is the user-facing output.
Relay completed, blocked, error, missing-input, job-status, and artifact-validation outputs unchanged. Do not summarize, rename sections, add deployment claims, or convert research-only data into execution-grade language.
Preserve prior crypto identifiers exactly:
job_idfingerprintproduct_idIf a follow-up asks whether an artifact can be exported, route back to crypto_analysis; the Hub must not decide export eligibility from memory.
If crypto_analysis is unavailable, say the crypto server is unavailable and do not substitute equity, prediction-market, or training-data analysis for current crypto market state.