CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trading-futures

Trade perpetual futures on Binance, Bybit, Hyperliquid, MEXC with up to 200x leverage

50

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/trading-futures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 comprehensive, mostly actionable API reference, but it fails on structure and workflow safety: a huge API surface is inlined rather than progressively disclosed, and high-risk financial operations lack any validation or feedback-loop guidance.

Suggestions

Move the per-exchange API reference (Binance, Bybit, Hyperliquid, MEXC) into separate files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Add a sequenced trading workflow with validation checkpoints (e.g. check balance → set leverage/margin → place order → verify position → set TP/SL), including a validate-then-proceed feedback loop for close-all and batch operations.

Trim redundant or rarely-used method listings to reduce token load, or gate them behind clearly signaled reference files.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and stays dense, but ~850 lines of inlined method listings is a heavy token load that could be trimmed or relocated.

3 / 5

Actionability

Concrete, copy-paste-ready TypeScript examples with real parameters cover the common cases, with only minor gaps where identifiers like orderId, walletAddress, startTime, or endTime are used without being obtained.

4 / 5

Workflow Clarity

This is a destructive/batch operation skill (real-money leveraged trading, close-all, batch orders) with no multi-step workflow, validation checkpoints, or feedback loops; the destructive-ops cap applies and the rough category grouping does not constitute a real sequence.

2 / 5

Progressive Disclosure

No bundle files exist and the entire 200+ method per-exchange API reference is inlined in SKILL.md — content that clearly belongs in separate per-exchange reference files is monolithically inlined despite section headers providing minimal structure.

2 / 5

Total

11

/

20

Passed

Description

65%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 is specific and highly distinguishable, naming concrete exchanges and leverage, but it lacks any 'when to use' trigger guidance and uses only one action verb, leaving completeness and specificity in the mid-range.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when trading perpetual futures (perps) on Binance, Bybit, Hyperliquid, or MEXC, or when the user wants leveraged long/short positions.'

Expand the single verb 'Trade' into a few concrete actions (e.g. 'place, manage, and close leveraged positions') to lift specificity.

Include common synonyms such as 'perps' and 'long/short' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('perpetual futures') and concrete specifics (four named exchanges, 'up to 200x leverage'), but offers only the single action verb 'Trade' rather than multiple distinct actions, so it does not reach comprehensive coverage.

3 / 5

Completeness

It clearly answers 'what' (trade perps on these exchanges with this leverage) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes highly natural trigger terms users would actually say — 'perpetual futures', 'Binance', 'Bybit', 'Hyperliquid', 'MEXC', 'leverage' — though common synonyms like 'perps', 'long/short', or 'crypto trading' are absent.

4 / 5

Distinctiveness Conflict Risk

The combination of named exchanges plus 'perpetual futures' and '200x leverage' carves a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (866 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/trading-futures/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.