CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-briefing

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

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally tight procedural skill: exact call parameters with fallbacks and quota variants, explicit failed-call handling, a fixed output template, and behavioral guardrails — all in ~85 lines with zero padding. It only teaches what is connector-specific (labels, thresholds, regimes) and never what Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it teaches by example ("'BTC −2.1% to 77,300, funding neutral, OI −2.7% with price flat' is a briefing; 'BTC looks weak' is not") and only explains connector-specific knowledge Claude cannot already know (funding baselines, OI regime labels, ratio thresholds). Every section earns its place; it does not fall to the 4 anchor since no over-explanation could be trimmed.

5 / 5

Actionability

Fully executable guidance: exact tool names with exact parameters (get_price with ["BTCUSDT","ETHUSDT","SOLUSDT"], sortBy: "change24h", limit: 50, interval: "4h"), fallback logic (rsi lt 30 → flip to rsi gt 70), quota-aware variants, and a complete copy-paste output template with a word budget. This covers the common cases end to end, matching the top anchor.

5 / 5

Workflow Clarity

The playbook is a clearly numbered 6-call sequence with explicit error handling ("If any call fails or returns empty, keep the section with a one-line 'unavailable right now' note rather than dropping it silently"), conditional variants (free-key three-call version, weekly 7d/1d settings), and a fixed 8-item output checklist. All operations are read-only, so the destructive/batch validation cap does not apply; the failed-call fallback provides the checkpoint and recovery path of the top anchor.

5 / 5

Progressive Disclosure

This is a single-file skill with no bundle files and no need for external references — the entire procedure is needed on every invocation. Content is appropriately placed in one well-sectioned file (playbook → interpretation → format → conduct) with easy navigation, which per the rubric's simple-skill note earns the top score for well-organized sections without external references.

5 / 5

Total

20

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capability list, comprehensive and natural trigger phrases including casual variants, explicit when-to-use guidance, and explicit exclusion boundaries against named sibling skills. It is dense but not padded — every clause names content or a trigger.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "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" plus screener flags (top movers, oversold / overbought names, squeezes) — comprehensively covering what the briefing contains with no notable gaps, matching the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

Both what and when are explicitly answered: the first sentence concretely states what the skill builds, and "Use this whenever the user asks..." gives explicit trigger phrases. This mirrors the anchor example that clearly and explicitly answers both what AND when with concrete trigger phrases; the when clause is explicit, so it is not the 4 anchor where when could be more specific.

5 / 5

Trigger Term Quality

Trigger phrases are natural user utterances spanning formal to casual: "what's happening in crypto", "market update", "morning brief", "how's the market today", "anything interesting right now", "give me an overview", "weekly recap", and even a vague "so, crypto?". This covers synonyms and colloquial variants comprehensively, matching the top anchor rather than merely having good coverage with a few missing terms.

5 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (market-level briefing vs. single-coin/single-trader/single-signal deep dives) and explicitly disambiguates: "Not for a deep dive on one coin (technical-analysis), one trader (smart-money) or one signal (trading-signals)". Boundaries are named rather than implied, giving minimal conflict risk per the top anchor.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

target1m/traderspy-mcp

Path

skills/market-briefing/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.