菜单
Use when you've just received output from a cryptozavr MCP tool (ticker, OHLCV, orderbook, trades) and need to read it correctly. Covers field meanings, staleness flags, reason_codes, and common pitfalls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | interpreting-market-data |
| description | Use when you've just received output from a cryptozavr MCP tool (ticker, OHLCV, orderbook, trades) and need to read it correctly. Covers field meanings, staleness flags, reason_codes, and common pitfalls. |
All tool outputs include:
venue, symbol — where the data came fromreason_codes: list[str] — ordered audit trail of the 5-handler chain:
venue:healthy|degraded|rate_limited|downsymbol:foundcache:bypassed (force_refresh=true)cache:hit (Supabase returned cached) OR cache:miss + provider:calledcache:write_failed (upsert couldn't persist; response still valid)staleness: "fresh"|"recent"|"stale"|"expired"confidence: "high"|"medium"|"low"cache_hit: boollast is the latest trade price. bid/ask may be None for CoinGecko (aggregator, no order book).volume_24h is in BASE units (BTC, not USDT).observed_at_ms is when the exchange stamped the data — may lag by seconds-minutes.candles: list[OHLCVCandleDTO] ordered oldest → newest.closed: bool — the last candle may be closed=false (still in-progress).range_start_ms / range_end_ms bracket the series; useful for windowing.bids sorted highest-price-first; asks lowest-price-first.spread = asks[0].price - bids[0].price.spread_bps = spread / midpoint × 10000 — 10 bps is tight, 50 bps is wide.bids or asks → spread is None.trades ordered newest → oldest.side: "buy"|"sell" from the taker's perspective (taker buy = demand).trade_id may be null for CoinGecko.staleness == "stale" or "expired" — suggest force_refresh=true.cache_hit=true on volatile prices (tick-by-tick). Warn if the caller needs fresh data.cache:write_failed in reasons — data is real, but the Supabase write didn't land. Non-fatal.venue:degraded — upstream exchange is slow/errorful. Reduce expectations.Use when the user asks a crypto-research question that needs multiple tool calls (ticker + OHLCV, comparison, trend analysis, liquidity check). This skill explains the research loop, when to call which tool, and how to structure findings.
Use when the user brings a declarative trading strategy (StrategySpec payload, a saved strategy id, or a plain-language "review my strategy" request). This skill runs the validate → explain → backtest → compare/stress → save loop against the Phase-2 MCP tools and packages the findings in a Claude-friendly order.
Use at the end of a cryptozavr research session (or when the user asks "wrap up" / "what did we do"). Produces a disciplined 3-bullet summary — artifacts produced, decisions made, what's next — so the next session starts warm.
Use when a cryptozavr tool returns degraded/stale data, times out, or reports an upstream failure (KuCoin/CoinGecko). Walks through the L2 infrastructure chain, inspects provider metrics, and pinpoints whether the issue is rate limiting, transport, provider downtime, or cache staleness.