Build a concise crypto market briefing from live TraderSpy data in a handful of tool calls — BTC/ETH/SOL price and 24h change, funding and open interest on the majors, which way top traders and the crowd lean, the freshest AI signals with their recent hit rate, and what the market screener flags right now (top movers, oversold / overbought names, squeezes). Use this whenever the user asks "what's happening in crypto", "market update", "morning brief", "how's the market today", "anything interesting right now", "give me an overview", "weekly recap", or opens a conversation with a vague "so, crypto?" — even casually. Not for a deep dive on one coin (technical-analysis), one trader (smart-money) or one signal (trading-signals).
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
A briefing is a fixed set of questions answered with fresh numbers, in an order a trader can scan in thirty seconds: where are the majors, how is the market positioned, what is the signal engine seeing, what stands out on the screener. The value is in the selection and the brevity, not in the volume of data — every tool call costs the user quota, so the playbook below is deliberately tight.
get_price with ["BTCUSDT","ETHUSDT","SOLUSDT"] plus any coins the user has
mentioned in the conversation (≤ 20 per call). Price, 24h change, 24h range.get_derivatives with ["BTC","ETH","SOL"] (add up to two of the user's
coins). Funding label and annualized rate, open-interest change and regime, top-trader long
share, taker flow. The notes[] are written to be quoted.screen_symbols with no conditions, sortBy: "change24h", limit: 50, universe: 50, interval: "4h". One call returns all 50 most-traded pairs sorted by 24h change: the top
five are the gainers, the last five the losers.screen_symbols with [{"metric":"rsi","op":"lt","value":30}] on 4h,
limit: 5. If it returns nothing, flip to rsi gt 70 — one of the two usually has names.get_signal_stats with period: "24h" (or 7d for a weekly recap).get_signals with limit: 5.Smart-money lean is already in step 2 (positioning.topTraderLongPct); add get_positions
(status: open, limit: 20) only when the user asks who specifically is positioned how.
Quota-aware variants. If the user is on a free key or asks for "just the headline", run steps
1, 2 and 5 only (three calls) and say what you skipped. For a weekly recap use 7d in step 5 and
interval: "1d" in steps 3–4.
If any call fails or returns empty, keep the section with a one-line "unavailable right now" note rather than dropping it silently — a briefing with a hole is more honest than one that quietly narrowed.
openInterest.regime): new_longs (OI up, price up), short_covering
(OI down, price up), new_shorts (OI up, price down), long_liquidation (OI down, price down),
flat. This is the one line that explains WHY the majors moved.long_heavy at a long/short ratio ≥ 1.5 (≈ 60%+
long) and short_heavy at ≤ 0.67 (≈ 40% or less); in between call it balanced. Top-trader
positioning is the more informative one; the all-account ratio shows the crowd.winRate is hits ÷ (hits + stops) on signals created in the window; say
total and pending next to it, and treat a 24h window with fewer than ~10 resolved signals as
a small sample.ALWAYS use this structure, in this order, with real numbers from the calls — no placeholders:
Crypto brief — <date, UTC time of the calls>
note.total signals in the window, hit rate with the resolved count, then the
five freshest signals as one line each: coin, side, timeframe, preset, status.Keep it under ~350 words. Numbers beat adjectives: "BTC −2.1% to 77,300, funding neutral, OI −2.7% with price flat" is a briefing; "BTC looks weak" is not.
target1m/traderspy-mcp
3631399
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.