CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

technical-analysis

Read one crypto futures pair (or a few) properly with TraderSpy — 19 indicators (RSI, MACD, EMA/SMA stacks, Bollinger, ATR, ADX, Stochastic, OBV, VWAP, CCI, MFI, Williams %R, ROC, SuperTrend, Ichimoku, Keltner), pivot points and swing support/resistance, Fibonacci and volume profile, RSI/MACD divergence, squeezes and candle patterns, up to three timeframes and up to three coins in ONE call with a confluence verdict — plus funding rate, open interest and long/short positioning, live price and OHLCV candles. Use this whenever the user asks about a coin's chart, trend, momentum, "is X overbought / oversold", support and resistance, where the 200 EMA is, "analyse BTC", "how does SOL look", "what do the indicators say", "is this a good entry", whether funding is high or open interest is building, or wants price / candle data — even if they only name a coin and ask how it looks. For scanning MANY coins by conditions use market-screener; for whale positions use smart-money.

77

Quality

97%

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

92%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.

A dense, well-structured instruction skill: every section is tool-specific and executable, the multi-step read-and-present workflow has explicit error-handling feedback loops, and detail is correctly offloaded to two real one-level-deep reference files. The only weakness is minor duplication and an expendable framing paragraph that could be trimmed for token budget.

Suggestions

Trim the opening framing paragraph ('One good read of a chart is three things in order…') to a single directive sentence — its guidance is restated in Making the call count and Reading the response.

State the risk disclaimer and hand-back-the-decision rule once: Presenting step 7 and the Conduct bullets repeat the same two points; consolidating into the Conduct section removes ~4 lines.

In Presenting, step 7 could reference the Conduct bullet rather than restating the full disclaimer, keeping the output template shorter.

DimensionReasoningScore

Conciseness

Nearly every line is connector-specific knowledge Claude cannot know (response shapes, funding thresholds, indicator field semantics, argument limits), so it is far from the verbose anchors. But there is trimmable material: the opening framing paragraph ('One good read of a chart is three things in order…'), and the risk/decision-handback point stated twice (Presenting step 7 'crypto derivatives are high-risk; this is market information, not advice' plus Conduct bullets 'hand the decision back' / 'the decision and the trade stay with the user'). This matches the score-4 anchor ('efficient; minor instances of over-explanation that could be trimmed'); it is not a 5 because those few tokens do not earn their place, and not a 3 because none of it is generic conceptual padding.

4 / 5

Actionability

Fully executable guidance with concrete arguments and defaults: 'pass intervals: ["1h","4h","1d"]', 'symbols: ["BTCUSDT","ETHUSDT","SOLUSDT"] in ONE call', 'Default rsi, macd, ema, bollinger', 'periods ({"ema":[9,21,55,200],"rsi":7})', exact limits ('indicators (≤ 19)', 'limit ≤ 500'), symbol naming rules ('Append USDT to a bare coin'), and an exact 7-step presentation template with a label format ('RSI(14) 41.3 — neutral, falling'). Matches the score-5 anchor ('fully executable… specific examples cover the common cases').

5 / 5

Workflow Clarity

The body is a clear pipeline (Tools → Making the call count → Reading the response → Presenting → Conduct) with explicit error feedback loops: a symbol returning no data routes to 'get_tracked_symbols… only when a symbol returns no data', 'an unknown key is rejected, so use the documented names only', '{ value: null, reason: "insufficient_data" } } means the tape is too short… say so, do not substitute', and 'warnings[] lists anything that was thinned or missing'. The read-only workflow needs no destructive-operation validation cap. Matches the score-5 anchor (clear sequence, feedback loops, an explicit presentation checklist); not a 4 because the checkpoints that exist are explicit, not implicit.

5 / 5

Progressive Disclosure

SKILL.md is an overview that pushes per-indicator field detail and derivatives detail to exactly two one-level-deep references, both real files, each signaled at its point of need: 'Details in references/derivatives-guide.md' and 'Per-indicator fields and conventional readings: references/indicator-guide.md'. The Tools table keeps bulk detail out of the body. Matches the score-5 anchor ('clear overview with well-signaled one-level-deep references; content appropriately split').

5 / 5

Total

19

/

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.

A model description: concrete capability inventory, verbatim user phrasings as triggers, an explicit 'Use this whenever…' clause, and explicit boundaries against sibling skills. Third-person, no fluff or over-claims. Its only debatable trait is length, but every clause is doing trigger or capability work, so it does not trip the anti-verbosity guideline.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities exhaustively: '19 indicators (RSI, MACD, EMA/SMA stacks, Bollinger, ATR, ADX, Stochastic, OBV, VWAP, CCI, MFI, Williams %R, ROC, SuperTrend, Ichimoku, Keltner)', 'pivot points and swing support/resistance, Fibonacci and volume profile, RSI/MACD divergence', 'up to three timeframes and up to three coins in ONE call with a confluence verdict', plus 'funding rate, open interest and long/short positioning, live price and OHLCV candles'. This matches the score-5 anchor ('multiple specific concrete actions; comprehensive coverage') — nothing concrete is missing, and it is third-person ('Read one crypto futures pair'). It is not a 4 because coverage has no gaps; it is not below because no capability is vague or generic.

5 / 5

Completeness

Both halves are explicit: the 'what' opens with the full capability list and the 'when' is a long 'Use this whenever the user asks about…' clause with concrete trigger phrases — the exact shape of the score-5 anchor example. Not a 4 because the 'when' is not merely present but exhaustive and specific.

5 / 5

Trigger Term Quality

It quotes verbatim natural user phrasings: '"is X overbought / oversold"', '"analyse BTC"', '"how does SOL look"', '"what do the indicators say"', '"is this a good entry"', 'where the 200 EMA is', 'whether funding is high or open interest is building', and the catch-all 'even if they only name a coin and ask how it looks'. These are exactly the synonyms a real user would say, matching the score-5 anchor ('comprehensive coverage of natural terms including synonyms'). Not a 4: no common variation of the ask is missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (technical read of one or a few crypto futures pairs) and explicitly routes adjacent intents away: 'For scanning MANY coins by conditions use market-screener; for whale positions use smart-money.' Minimal conflict risk, matching the score-5 anchor ('clear niche with distinct triggers'). The one-bit ambiguity with a generic market-screener is resolved by the explicit boundary sentence, so it does not fall to 4.

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/technical-analysis/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.