binance-futures

Binance Futures trading with DB tracking

Quality

37%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/binance-futures/SKILL.md

Quality

Discovery

22%

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 extremely terse and lacks concrete actions, explicit trigger guidance, and natural keyword coverage. While 'Binance Futures' provides some domain specificity, the description fails to communicate what the skill actually does or when Claude should select it. It reads more like a project title than a functional skill description.

Suggestions

List specific concrete actions the skill performs, e.g., 'Places and manages Binance Futures orders, tracks open positions, logs trades to a database, queries trade history and PnL.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Binance Futures, crypto futures trading, opening/closing positions, leverage, or reviewing trade history.'

Clarify what 'DB tracking' means concretely, e.g., 'Stores trade records in a local database for performance analysis and reporting.'

Dimension	Reasoning	Score
Specificity	The description names a domain ('Binance Futures trading') and mentions 'DB tracking' but does not list any concrete actions like placing orders, monitoring positions, querying trade history, etc.	1 / 3
Completeness	The description weakly addresses 'what' (Binance Futures trading with DB tracking) but provides no 'when' clause or explicit trigger guidance at all, which per the rubric caps completeness at 2 at best—and since the 'what' is also very weak, a score of 1 is appropriate.	1 / 3
Trigger Term Quality	'Binance Futures trading' contains natural keywords a user might say (Binance, Futures, trading), but 'DB tracking' is vague and there are no variations or additional trigger terms like 'crypto', 'leverage', 'positions', 'orders', or 'perpetual'.	2 / 3
Distinctiveness Conflict Risk	'Binance Futures' is fairly specific and distinguishable from general trading or other exchange skills, but 'DB tracking' is vague enough to overlap with any database-related skill, and the lack of detail increases conflict risk.	2 / 3
	Total	6 / 12 Passed

Implementation

52%

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

This is a clean, well-formatted command reference that is concise and easy to scan. However, for a skill involving real financial trading with high leverage, it critically lacks safety guardrails, validation steps, error handling, and workflow guidance for multi-step trading operations. The database tracking mentioned in the description has no setup or configuration instructions.

Suggestions

Add a workflow section showing the typical trading flow (open → set TP/SL → monitor → close) with explicit validation checkpoints and confirmation steps, especially for destructive operations like closeall

Add error handling guidance: what happens when orders fail, insufficient margin, or API errors occur, and how to recover

Include safety constraints: risk limits, confirmation prompts for high-leverage trades, and warnings about closeall

Document database setup requirements and configuration since DB tracking is a core feature mentioned in the description

Dimension	Reasoning	Score
Conciseness	Every line serves a purpose. No unnecessary explanations of what futures trading is, what leverage means, or how Binance works. Tables are compact and the examples section doubles as documentation without redundancy.	3 / 3
Actionability	The commands are clearly specified with syntax patterns and inline examples, but this is a command reference rather than executable code. Key details are missing: what happens on errors, what the database setup requires, whether there are confirmation prompts for destructive operations like closeall, and how the DB tracking is configured.	2 / 3
Workflow Clarity	For a trading skill involving real money and up to 125x leverage, there are no validation checkpoints, no confirmation steps before executing trades, no error handling guidance, and no workflow for common multi-step processes like 'open position → set TP/SL → monitor → close'. The closeall command has no safety guidance. Missing feedback loops for destructive financial operations should cap this low.	1 / 3
Progressive Disclosure	Content is well-organized with clear sections (Account, Trading, Market Data, Database/History) and tables for quick scanning. However, there are no references to external files for advanced topics like database setup, risk management strategies, or API configuration details that would benefit from separate documentation.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.