agentleFS
target1mtarget1m/traderspy-mcp/skills/market-briefing/SKILL.md

market-briefing

Skill3 starsChanged 9 days agoMITView on GitHub

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?". Not for a deep dive on one coin (technical-analysis), one trader (smart-money) or one signal (trading-signals).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. KureMaki/market-briefing-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    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 …

    line 30
  2. Distinctive:

    If any call fails or returns empty, keep the section with a one-line "unavailable right now" note rather than dropping it silently — a …

    line 34
  3. Distinctive:

    ALWAYS use this structure, in this order, with real numbers from the calls — no placeholders:

    line 57
  4. Distinctive:

    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.

    line 75
  5. Distinctive:

    Every number comes from a tool result made in this conversation.

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

The playbook (6 calls, all read-only)

  1. Majors — get_price with ["BTCUSDT","ETHUSDT","SOLUSDT"] plus any coins the user has mentioned in the conversation (≤ 20 per call). Price, 24h change, 24h range.
  2. Positioning — 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.
  3. Movers — 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.
  4. What is stretched — 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.
  5. Signal engine — get_signal_stats with period: "24h" (or 7d for a weekly recap).
  6. Freshest ideas — 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.

Reading the pieces

  • Funding: near the 0.01%/8h baseline is neutral; clearly positive means longs pay shorts (a crowded long is a risk, not a signal); negative means shorts pay. Quote the annualized figure — it is the number people feel.
  • Open interest regime (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.
  • Top-trader long share: the tool labels 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.
  • Signal stats: 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.
  • Movers are the most-traded pairs by 24h volume sorted by change — a liquid-names list, not an all-market list. Say so if a small cap the user follows is missing.

The briefing format

ALWAYS use this structure, in this order, with real numbers from the calls — no placeholders:

Crypto brief — <date, UTC time of the calls>

  1. Headline — one sentence: the majors' direction and the single most notable positioning fact.
  2. Majors — a table: Symbol · Price · 24h % · 24h range.
  3. Positioning — per major, one line: funding (label, annualized), OI regime, top-trader long %, and one quoted note.
  4. Movers — top 5 gainers and top 5 losers among the most-traded pairs (symbol, price, 24h %).
  5. Stretched — the oversold or overbought names with their RSI, or "none on the 4h" if empty.
  6. Signal engine — 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.
  7. What to watch — two or three bullets derived from the data above (a funding extreme, an OI regime worth confirming, a stretched name that is also in a signal). Facts and their implications, not instructions.
  8. One plain sentence: crypto derivatives are high-risk; this is market information for the user's own research, not financial advice.

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.

Conduct

  • A briefing reports the market; it does not tell the user what to do in it. "What to watch" names facts and what would confirm or invalidate them — never "buy the dip" or "short this".
  • Hit rates and past moves describe their sample; do not extend them into predictions.
  • Nothing in this connector trades — no order, close, transfer or withdrawal tool exists, by design. If asked to act on the briefing, say so plainly; the decision and the trade stay with the user.
  • Every number comes from a tool result made in this conversation; state the time of the calls so the user knows how fresh the brief is, and never reuse figures from an earlier brief as if they were current.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.