CtrlK
BlogDocsLog inGet started
Tessl Logo

binance-futures

Binance Futures trading with DB tracking

56

Quality

64%

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/binance-futures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 actionable and concise, with copy-paste command tables covering the full command surface. Its main weakness is the absence of validation or confirmation steps for destructive trading operations like closeall and high-leverage position opens.

Suggestions

Add explicit validation/confirmation steps before destructive and batch operations, e.g. confirm position size and leverage before opening, and require explicit acknowledgement before '/bf closeall'.

Remove or consolidate the Examples section since it duplicates the command tables, or repurpose it to show full multi-step workflows with checks.

Include a brief error-handling note for common failures (insufficient margin, API errors, rejected orders).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, using command tables and brief examples rather than explaining concepts; the only trimmable redundancy is the Examples section repeating commands already in the tables, so it sits above the score-3 midpoint but not at a perfect 5.

4 / 5

Actionability

Commands are concrete and copy-paste ready (e.g. '/bf long BTCUSDT 0.01 10x'), and the Examples section covers the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

The Quick Start gives a rough sequence but the skill performs destructive/batch operations (closeall, high-leverage positions) with no validation, confirmation, or error-feedback steps, so workflow clarity is capped at 3 per the destructive-operations guideline.

3 / 5

Progressive Disclosure

Content is well organized into clearly labeled sections (Quick Start, Commands by category, Examples) with no need for external references; minor organization gaps (overlapping examples) keep it just below 5.

4 / 5

Total

16

/

20

Passed

Description

52%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 distinct and domain-specific but thin: it lacks a 'Use when' trigger clause and its actions are vague. It would benefit from naming concrete operations and an explicit usage trigger.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to trade perpetual futures on Binance, manage positions, or review trading history'.

Replace generic 'trading with DB tracking' with concrete actions like 'open/close leveraged long and short positions, set take-profit and stop-loss, and query trade and funding history'.

Include natural synonyms like 'perpetuals', 'leverage', and 'crypto' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Binance Futures trading with DB tracking' names the domain but its actions ('trading', 'DB tracking') are minimal and generic, matching the score-2 anchor rather than score-3 which requires concrete actions.

2 / 5

Completeness

It states a clear 'what' (Binance Futures trading with DB tracking) but has no 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the guidelines.

3 / 5

Trigger Term Quality

'Binance Futures' and 'trading' are relevant natural keywords, but common variations like 'crypto', 'perpetuals', 'leverage', 'long/short' are missing, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

'Binance Futures trading' names a specific platform and asset class, giving it a clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
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.