CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trading-signals

Query, explain and evaluate TraderSpy's AI crypto futures signals — the newest signals, signals for one coin, what a signal's entry / take-profit / stop levels and triggered conditions mean, whether a signal still stands at the current price, and how signals have performed (hit rate, hits vs stops) over the last 4h to 7d. Use this whenever the user mentions crypto signals, AI alerts, "any setups", "what is the AI seeing", long/short ideas, TraderSpy alerts, signal performance or track record — even when they never say the word "signal". Not for placing trades (no tool can), not for whale or top-trader positioning (smart-money), not for indicator reads on a coin (technical-analysis).

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

Low

Low-risk findings worth noting

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.

The body is a lean, tool-first reference: exact arguments and their non-obvious semantics, field meanings with conversion math, intent-to-tool workflows with edge-case handling, and a defined presentation format — with the glossary correctly deferred to a real reference file. No dimension shows a substantive weakness.

DimensionReasoningScore

Conciseness

Every section adds domain knowledge Claude cannot have — inclusive-downward "importance", prefix-match "coin", "resolutionStatus" semantics, the 24×timeframe tracking window, the sub-1 R:R caveat — with zero padding or explanation of known concepts. Not level 4 because I found no trimmable over-explanation; the only repetition (decision stays with the user, ~3 short clauses across 114 lines) is deliberate reinforcement of a compliance-critical point in a high-risk domain.

5 / 5

Actionability

Fully concrete for an instruction-only skill: a tool table with argument ranges and defaults ("limit 1–50 (default 20)"), exact conversion formulas ("TP = price × (1 + pct/100)"), a status table, and a literal answer skeleton (table columns; headline → levels → triggers → current price → outcome → risk note). Not level 4 because guidance is copy-paste executable for every common case, including null-field and empty-result handling.

5 / 5

Workflow Clarity

Four workflows each map a user intent to a named tool with argument choices ("get_signals with the limit the user implies (default 10 if they gave no number)") and explicit checkpoints: check each row's coin field before presenting, handle empty results by saying so, detect stale pending signals, and compare livePrice against levels in the same units. Not level 4 because edge-case handling is explicit throughout, and read-only tool calls carry no destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Frequently-needed material lives inline while the full glossary is split to a clearly signaled, one-level-deep, verified-existing reference: "For the full field glossary, including the indicatorValues keys, read references/signal-fields.md." Not level 4 because navigation is unambiguous and no content that belongs in the reference is inlined.

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.

The description states concrete capabilities, natural trigger phrases quoted as users would say them, an explicit use-when clause, and explicit exclusions that separate it from sibling skills. It is a model description with no fluff despite its length.

DimensionReasoningScore

Specificity

"Query, explain and evaluate" plus enumerated concrete capabilities — "the newest signals, signals for one coin", "entry / take-profit / stop levels and triggered conditions", "whether a signal still stands at the current price", "hit rate, hits vs stops over the last 4h to 7d" — matches the anchor for multiple specific concrete actions with comprehensive coverage; not level 4 because no meaningful capability gap remains.

5 / 5

Completeness

Explicitly answers both: what ("Query, explain and evaluate TraderSpy's AI crypto futures signals" with subtasks) and when ("Use this whenever the user mentions... even when they never say the word 'signal'"). This mirrors the anchor-5 example structure exactly; not level 4 because the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Natural user phrasings are quoted verbatim ("any setups", "what is the AI seeing") alongside synonyms ("crypto signals", "AI alerts", "long/short ideas", "signal performance or track record", "TraderSpy alerts"), matching the anchor for comprehensive natural-term coverage including synonyms. Not level 4 because even colloquial variations users actually say are present.

5 / 5

Distinctiveness Conflict Risk

A named product niche (TraderSpy AI signals) plus explicit negative boundaries — "Not for placing trades... not for whale or top-trader positioning (smart-money), not for indicator reads on a coin (technical-analysis)" — gives a clear niche with minimal conflict risk. Not level 4 because adjacent-skill overlap is explicitly disambiguated.

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/trading-signals/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.