binance-leaderboard
On-chain wallet leaderboard and Gem Hunter analysis on Binance Web3. Query top trader rankings by PnL, win rate, volume, trade count, or token count across BSC/Solana/Base/ETH. Analyze individual wallet addresses with a 6-dimension scoring model (winrate/stability/drawdown/ tags/pnl/follow_friendly) plus AI archetype overlay. Query Gem Hunter to find wallets holding specific tokens. Save and load preset filter conditions and Gem Hunter configs. Trigger whenever the user mentions leaderboard, top traders, wallet analysis, Address Analysis, AddressScore, Gem Hunter, or wants to evaluate a wallet
npx skills add binance/binance-skills-hub --skill binance-leaderboard --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Binance Leaderboard Skill On-chain wallet leaderboard ranking and address analysis. Query top traders by PnL, win rate, and more. Evaluate wallet quality with a 6-dimension scoring model. ## Prerequisites This skill requires the `baw` CLI (`@binance/agentic-wallet` npm package). If `baw` is not found: ```bash npm install -g @binance/agentic-wallet ``` Verify: `baw --version` should print `1.6.2` or higher. If installation fails or the user doesn't have Node.js, inform them that Node.js >= 18 is required. ## When to Use | User intent | Command | |-------------|---------| | Query top traders by PnL/win rate/volume | `baw leaderboard query` | | Analyze a single wallet address (6-dim score + AI archetype) | `baw leaderboard analyze` | | Find wallets holding specific tokens (Gem Hunter) | `baw leaderboard alpha-radar` | | Save/load preset filter conditions | `baw leaderboard preset save/list` | | Save/load Gem Hunter configs | `baw leaderboard alpha-radar-config save/list` | ## Supported Chains | Chain | chainId | |-------|---------| | BSC | `56` | | Solana | `CT_501` | | Base | `8453` | | Ethereum | `1` | ## Command Tree ``` baw leaderboard query # Leaderboard query (Public, no auth)
- Prerequisites
- When to Use
- Supported Chains
- Command Tree
- Leaderboard Query
- Single Address Analyze
- Gem Hunter
- Preset & Gem Hunter Config
- Core Rules
- Scoring Model Overview
- Top-N Reverse Lookup
- Preset & Config Clearing
- Cross-Skill Scenarios
- Write-Back Confirmation
npm install -g @binance/agentic-wallet Basic query — top 20 by PnL on BSC, 7d period baw leaderboard query -c 56 -p 7d -t ALL --json Sort by win rate, KOL tag only baw leaderboard query -c 56 -p 30d -t KOL --sort-by 20 --json Pagination (page from 0, size max 20) baw leaderboard query -c 56 -p 7d --page 0 --size 20 --json Analyze a wallet address — 6-dim scoring + AI archetype Default scans top 1000 entries baw leaderboard analyze -c 56 -a 0xabc... --json
What does the binance-leaderboard skill do?
On-chain wallet leaderboard and Gem Hunter analysis on Binance Web3. Query top trader rankings by PnL, win rate, volume, trade count, or token count across BSC/Solana/Base/ETH. Analyze individual wallet addresses with a 6-dimension scoring model (winrate/stability/drawdown/ tags/pnl/follow_friendly) plus AI archetype overlay. Query Gem Hunter to find wallets holding specific tokens. Save and load preset filter conditions and Gem Hunter configs. Trigger whenever the user mentions leaderboard, top traders, wallet analysis, Address Analysis, AddressScore, Gem Hunter, or wants to evaluate a wallet
How do I install it?
Run `npx skills add binance/binance-skills-hub --skill binance-leaderboard --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From binance/binance-skills-hub, a repository with 947 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
