binance

Binance exchange integration. Trade spot, futures, and manage portfolio on the world's largest crypto exchange.

Install with Tessl CLI

npx tessl i github:Demerzels-lab/elsamultiskillagent --skill binance

What are skills?

Review — 48%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

32%

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 the platform and core trading capabilities but lacks explicit trigger guidance for when Claude should select this skill. It would benefit from a 'Use when...' clause and more specific action verbs. The Binance branding provides some distinctiveness but more natural user keywords would improve selection accuracy.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Binance', 'buy crypto', 'sell bitcoin', 'check crypto balance', 'futures trading'

Expand specific actions to include 'place orders', 'check balances', 'view trading history', 'set stop-loss' for better capability coverage

Include common crypto terms users would naturally say: 'BTC', 'ETH', 'trading pairs', 'limit order', 'market order'

Dimension	Reasoning	Score
Specificity	Names the domain (Binance exchange) and some actions ('Trade spot, futures, and manage portfolio'), but lacks comprehensive specific actions like order types, balance checking, or withdrawal capabilities.	2 / 3
Completeness	Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Binance', 'spot', 'futures', 'crypto exchange', and 'portfolio', but missing common variations users might say like 'buy crypto', 'sell bitcoin', 'check balance', 'trading', or 'BTC'.	2 / 3
Distinctiveness Conflict Risk	Binance-specific naming provides some distinctiveness, but 'crypto exchange' and 'trade' could overlap with other exchange integrations (Coinbase, Kraken, etc.) without clearer differentiation.	2 / 3
	Total	7 / 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.

This skill provides solid, actionable API integration examples with executable curl commands and proper authentication handling. However, it includes unnecessary marketing content (referral section) and lacks explicit validation workflows critical for financial operations. The monolithic structure could benefit from splitting advanced topics (futures, error handling) into separate files.

Suggestions

Remove or minimize the referral configuration section - it's marketing content, not instructional guidance for Claude

Add explicit validation workflows for trading operations: check order status after placement, verify balance changes, handle partial fills

Split futures trading and advanced error handling into separate referenced files (e.g., FUTURES.md, TROUBLESHOOTING.md) for better progressive disclosure

Remove the 'Popular Trading Pairs' and 'Order Types' tables - Claude already knows these concepts

Dimension	Reasoning	Score
Conciseness	Generally efficient with executable code examples, but includes some unnecessary content like the referral configuration section (marketing-focused, not instructional) and explanatory tables for popular trading pairs and order types that Claude already knows.	2 / 3
Actionability	Provides fully executable bash/curl commands with proper authentication, signature generation, and jq parsing. All examples are copy-paste ready with clear variable substitution patterns.	3 / 3
Workflow Clarity	Safety rules mention verification steps but lack explicit validation workflows. For trading operations (destructive/financial), there's no feedback loop showing how to verify order placement succeeded or how to handle partial fills. Steps are listed but checkpoints are implicit.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but it's a monolithic file with no references to separate detailed documentation. The futures trading section is minimal and could benefit from a separate detailed guide. External links are provided but internal progressive disclosure is absent.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 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

Reviewed: 8 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.