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, x402 payment, HTTP 402 Payment Required, pay a known x402 API, check approvals, view token approvals, revoke approval, manage approvals, wallet approvals, authorization management, token authorization, or any on-chain wallet operation.

62

Quality

73%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/binance-web3/binance-agentic-wallet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is an excellent skill file that serves as a comprehensive command routing hub for a complex CLI tool. It is concise yet thorough, with a well-structured routing table mapping user intents to exact commands and reference files. The security policy, error handling guidelines, display rules, and common token address tables add significant practical value without unnecessary verbosity.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. Every section serves a clear purpose — command routing table, preflight checks, build steps, display rules, security policy, error handling, and token addresses. There is no unnecessary explanation of what wallets are, how blockchains work, or other concepts Claude already knows.

3 / 3

Actionability

The command routing table provides exact CLI commands for every user intent. The 'Build the Command' section gives a concrete, step-by-step process. Token address tables provide copy-paste-ready contract addresses. The skill delegates detailed syntax to reference files, which is appropriate for a routing/overview skill.

3 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced: preflight checks first, then read reference file, build command, append --json, confirm before execution. Security pre-checks are explicitly required before swaps/orders. Error handling has clear rules. The confirmation step acts as a validation checkpoint for state-changing operations, and the security swap pre-check provides a feedback loop before risky operations.

3 / 3

Progressive Disclosure

The skill is an exemplary overview that routes to well-organized reference files (authentication.md, wallet-view.md, send.md, market-order.md, limit-order.md, prediction.md, x402-payment.md, security.md, preflight.md, approvals.md). References are one level deep, clearly signaled in the routing table, and cover all command categories. Content is appropriately split between the overview and detailed references.

3 / 3

Total

12

/

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 comprehensive, the complete absence of a capability summary ('what does this do') severely undermines its quality. It needs a concise opening statement describing the skill's concrete actions before the trigger term list.

Suggestions

Add a clear capability summary at the beginning, e.g., 'Manages Web3 wallet connections, executes on-chain token transfers and swaps, places DEX orders, interacts with prediction markets, handles x402 payments, and manages token approvals.'

Restructure the description to separate 'what it does' from 'when to use it' — lead with concrete actions, then follow with the 'Use when...' trigger list.

Consider grouping the trigger terms by category (wallet ops, trading, predictions, approvals) for better readability and to help Claude understand the skill's scope more clearly.

DimensionReasoningScore

Specificity

The description lists many keywords and domains (wallet operations, DEX trading, prediction markets, x402 payments, token approvals) but doesn't clearly describe concrete actions the skill performs. It reads more like a keyword list than a capability description — there's no 'what this does' statement like 'Connects wallets, executes trades, manages token approvals.'

2 / 3

Completeness

The description only addresses 'when' (via 'Use when the user mentions...') but completely lacks a 'what does this do' section. There is no explanation of the skill's capabilities, purpose, or what actions it performs. Per the rubric, this is 'Missing what OR when, or both very weak.'

1 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say: 'connect wallet', 'send BNB', 'swap tokens', 'check balance', 'how much crypto do I have', 'transaction history', 'revoke approval', etc. Includes both technical terms and casual phrasing.

3 / 3

Distinctiveness Conflict Risk

The description covers a very broad scope (wallet management, DEX trading, prediction markets, x402 payments, token approvals) which makes it somewhat distinctive in the web3/crypto domain, but the breadth is so wide it could overlap with more specialized crypto skills. The prediction market and x402 payment triggers help differentiate it somewhat.

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.