CtrlK
BlogDocsLog inGet started
Tessl Logo

binance-agentic-wallet

Use when the user mentions wallet connect/sign in/sign out, check balance, send/transfer tokens, swap/buy/sell tokens, DEX trade, limit/market order, cancel order, get a quote, transaction history, wallet settings, daily limit, slippage, MEV protection, supported chains, prediction market, place prediction, redeem winnings, prediction PnL, x402 payment, HTTP 402 Payment Required, check/revoke/manage token approvals, DeFi protocols, staking, liquidity pool, LP, yield farming, deposit, redeem, stake, unstake, claim rewards/fees, health factor, APY, TVL, sign external transaction, contract call, sign message, EIP-712, developer mode, speed up/cancel/replace transaction, pending/stuck transactions, or any on-chain wallet operation.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

The SKILL.md body is a well-architected overview — a routing table plus concise policy sections, with command detail offloaded to one-level-deep reference files that all exist. Workflows carry explicit validation and feedback loops for destructive/signing operations, and guidance is concrete and executable throughout; the only slack is a few dense rule paragraphs that could be further tightened.

Suggestions

Move the RWA provider disambiguation and payment-token-selection nuances into their respective reference files (campaign.md / a token-resolution reference) and keep the main file to the routing summary.

Consider relocating the per-chain Common Token Address tables into a dedicated reference file, leaving only the resolution rule and a pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is largely efficient — a routing table, terse policy rules, and pointers to references instead of restating CLI details — but the Build the Command and Common Token Addresses sections carry dense prose (payment-token selection, RWA provider disambiguation, conditional-order handling) that could be trimmed or moved into references.

4 / 5

Actionability

It gives concrete executable routing ('auth signin → auth verify', 'market-order swap', 'defi deposit'), mandates an exact `--json` flag, supplies a real REST endpoint with query params, and a wei conversion example ('1 BNB is --value 1000000000000000000'); references carry copy-paste-ready syntax and examples.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced with validation checkpoints — preflight before any operation, 'read the reference file first' then build then confirm, and the external-sign two-step (check devMode → preview → confirm → execute) with an explicit 'If preview returns an error, do not attempt execute' feedback loop for destructive signing operations.

5 / 5

Progressive Disclosure

The body is a clean overview whose command-routing table maps each intent to a one-level-deep reference (all 15 referenced files verified present under references/), keeping detailed syntax/parameters in those files and signaling navigation via labeled markdown links.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive trigger list that explicitly answers both what the skill does and when to use it, using natural user phrasings and distinctive domain terms. The only weakness is a broad catch-all clause that slightly raises overlap risk with other wallet skills.

Suggestions

Tighten the trailing catch-all 'or any on-chain wallet operation' to scope it to the Binance Agentic Wallet specifically, reducing overlap risk with generic on-chain wallet skills.

DimensionReasoningScore

Specificity

The description lists many concrete on-chain wallet operations — 'check balance', 'send/transfer tokens', 'swap/buy/sell tokens', 'limit/market order, cancel order', 'check/revoke/manage token approvals', 'deposit, redeem, stake, unstake', 'claim rewards/fees', 'sign external transaction, contract call, sign message' — comprehensively covering the skill's action surface.

5 / 5

Completeness

It opens with an explicit 'Use when the user mentions ...' trigger clause (the when) and enumerates concrete operations (the what), so both questions are answered with concrete trigger phrases.

5 / 5

Trigger Term Quality

It packs natural user phrasings with synonyms — 'send/transfer', 'swap/buy/sell', 'pending/stuck transactions', 'HTTP 402 Payment Required' — alongside domain terms users actually say (EIP-712, APY, TVL, slippage, MEV protection), giving comprehensive keyword coverage.

5 / 5

Distinctiveness Conflict Risk

Distinctive Binance Web3 terms (x402 payment, prediction market, bStock context, EIP-712) carve a clear niche, but the closing catch-all 'or any on-chain wallet operation' creates minor overlap risk with other on-chain wallet skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

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.