CtrlK
BlogDocsLog inGet started
Tessl Logo

binance-agentic-wallet

Use when the user mentions connect/disconnect wallet, sign in, sign out, web3 wallet, wallet address, check balance, how much crypto do I have, send BNB/USDT/crypto, transfer tokens, swap tokens, buy/sell token, DEX trade, limit order, market order, cancel order, get a quote, transaction history, wallet settings, daily limit, slippage, MEV protection, supported chains, available networks, prediction market, predict.fun, YES/NO market, place a prediction, redeem winnings, claim payout, prediction portfolio, prediction PnL, or any on-chain wallet operation.

57

Quality

66%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/binance-web3/binance-agentic-wallet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured skill that excels as a routing and policy document for a complex CLI tool. The command routing table is an excellent pattern for mapping user intents to specific commands with clear reference file pointers. Minor verbosity in the error handling and security sections could be tightened, but overall the skill efficiently conveys critical information like token addresses, confirmation protocols, and security policies.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with its routing table and reference-based structure, but some sections like Error Handling and Security Policy contain guidance that Claude already knows (e.g., 'do not speculate', 'do not rephrase'). The Display Rules section also includes somewhat obvious formatting instructions. However, the token address tables and command routing table are genuinely useful and earn their tokens.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: exact CLI commands mapped to user intents, specific token contract addresses, explicit confirmation protocols, and clear step-by-step command building instructions. The routing table serves as a precise lookup for every supported operation, and the --json flag requirement is specific and executable.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: preflight checks → read reference file → build command → append --json → confirm with user → execute. Security pre-checks are explicitly required before swap/limit operations. The confirmation protocol includes specific acceptance criteria ('yes', 'confirm', 'go ahead') and a fail-closed security policy. Validation checkpoints are present for state-changing operations.

3 / 3

Progressive Disclosure

The skill is an excellent overview/routing document that delegates detailed command syntax to well-organized reference files (authentication.md, wallet-view.md, send.md, market-order.md, limit-order.md, prediction.md, security.md, preflight.md). References are one level deep, clearly signaled in the routing table, and each reference file covers a logical grouping of related commands.

3 / 3

Total

11

/

12

Passed

Description

47%

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 essentially a long list of trigger terms with no explanation of what the skill actually does. While the trigger term coverage is excellent and natural, the complete absence of a 'what does this do' statement is a critical weakness. It reads as a keyword dump rather than a proper skill description that would help Claude understand the skill's purpose and capabilities.

Suggestions

Add a clear 'what' statement at the beginning describing the skill's capabilities, e.g., 'Manages Web3 wallet operations including connecting wallets, checking balances, sending/receiving crypto, executing DEX trades, and participating in prediction markets.'

Restructure the description to separate the capability summary from the trigger guidance, using a format like: '[capability summary]. Use when [trigger terms].'

Consider grouping the trigger terms into logical categories (wallet management, trading, prediction markets) for better readability and to help Claude understand the scope of each capability area.

DimensionReasoningScore

Specificity

The description lists many specific trigger terms and actions (connect/disconnect wallet, send BNB/USDT, swap tokens, DEX trade, limit order, prediction market), but it reads more like a keyword list than a structured description of concrete capabilities. It never clearly states what the skill actually does — it only lists trigger phrases.

2 / 3

Completeness

The description only addresses 'when' (via trigger terms) but completely lacks a 'what does this do' component. There is no explanation of the skill's capabilities, purpose, or what actions it performs. Per the rubric, missing 'what' should result in a low completeness score.

1 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'how much crypto do I have', 'send BNB', 'buy/sell token', 'swap tokens', 'check balance', 'wallet address', 'prediction market', 'claim payout'. These are highly natural and cover many variations a user might use.

3 / 3

Distinctiveness Conflict Risk

The description covers a very broad range of web3/crypto operations including wallet management, token trading, DEX operations, AND prediction markets. This breadth could overlap with more specialized crypto skills. However, the combination of wallet + trading + prediction markets is somewhat distinctive.

2 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
binance/binance-skills-hub
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.