binance
Binance exchange integration. Trade spot, futures, and manage portfolio on the world's largest crypto exchange.
48
52%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/binance/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (Binance exchange integration) and mentions key trading types (spot, futures), giving it good distinctiveness. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and the capability listing is too brief to fully convey the range of supported actions.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'Binance', 'buy crypto', 'sell crypto', 'check balance', 'trading', 'BTC', 'crypto order'.
Expand the capability list with more specific actions such as 'place limit/market orders, check account balances, view open positions, manage stop-losses, withdraw funds'.
Include common file or data references users might mention, such as 'API keys', 'trading pairs', or specific coin tickers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Binance exchange) and some actions (trade spot, futures, manage portfolio), but doesn't list comprehensive specific actions like placing limit orders, checking balances, viewing order history, etc. | 2 / 3 |
Completeness | Describes what it does (trade spot, futures, manage portfolio on Binance) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also not very detailed, placing this at 1-2. Given the missing 'when' clause entirely, scoring at the cap boundary minus the weak 'what' yields a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Binance', 'spot', 'futures', 'crypto exchange', and 'portfolio', but misses common user terms like 'buy/sell crypto', 'trading', 'BTC', 'order', 'balance', or 'withdrawal'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Binance specifically, which is a distinct niche. The mention of 'Binance exchange' makes it unlikely to conflict with other crypto exchange skills or general trading skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with complete, executable curl commands covering the full range of Binance API operations. However, it includes unnecessary marketing content (referral section, feature list, popular pairs table) that wastes tokens, and lacks a structured workflow for the critical order-execution path where verification and confirmation steps should be explicitly sequenced as a feedback loop.
Suggestions
Remove the referral/commission section, 'Features' marketing list, and 'Popular Trading Pairs' table—these don't help Claude execute tasks and waste context window tokens.
Add an explicit order execution workflow: 1) Check balance → 2) Display order preview to user → 3) Wait for confirmation → 4) Execute → 5) Verify order status, with error recovery steps.
Split futures trading, convert operations, and order type details into separate referenced files to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete code examples, but includes unnecessary content like the referral/commission section (irrelevant to Claude's task execution), the 'Popular Trading Pairs' table (Claude already knows these), and the 'Features' bullet list which is marketing fluff rather than actionable guidance. | 2 / 3 |
Actionability | The skill provides fully executable bash/curl commands for every operation—authentication, placing orders, checking balances, canceling orders, futures positions, and conversions. All examples are copy-paste ready with proper variable substitution and jq formatting. | 3 / 3 |
Workflow Clarity | Safety rules mention verifying details and checking balances before trading, but there's no explicit workflow sequence tying these together (e.g., check balance → display order preview → get confirmation → execute → verify result). For destructive financial operations like placing orders, the lack of a structured validate-then-execute feedback loop is a notable gap. | 2 / 3 |
Progressive Disclosure | The content is reasonably organized with clear section headers, but it's a long monolithic file (~200 lines) that could benefit from splitting futures, convert, and advanced order types into separate referenced files. No bundle files exist to offload detailed content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.