Agent skill · Data & Analytics

query-token-info

Per-token details for a specific token identified by keyword, symbol, or contract address: (1) search — find tokens by keyword/symbol/contract; (2) meta — static info: name, symbol, logo, social links, creator, official website; (3) dynamic — real-time market data: price, 24h change, volume, holder count, liquidity; (4) kline — OHLCV candlestick data for technical analysis. Use for: "price of $X", "search for token Y", "kline chart for $Z", "who created $W", "social links for $V", "holder count of $U", "candlestick data", "find the contract address of <token>".

binancegithub.com/binanceGitHub ↗
claude-codeships scripts
Install
npx skills add binance/binance-skills-hub --skill query-token-info --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 4 KB
Bundled scripts: yes
Version: 2.0
Declared author: binance-web3-team
Path: skills/binance-web3/query-token-info/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 947
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Query Token Info Skill ## Overview Four read-only token endpoints fronted by one CLI. The agent picks a subcommand and passes a JSON blob; with this skill user can: Search Tokens: Find tokens by name, symbol, or contract address across chains. Token Research: Get token metadata, social links, and creator info. Market Analysis: Real-time price, volume, holder distribution, and liquidity data. Chart Analysis: K-Line candlestick data for technical analysis. ## When to Use This Skill | User intent | Command | |-------------|---------| | Search a token by keyword, symbol, or contract address | `search` | | Get static metadata (name, symbol, logo, social links, creator) | `meta` | | Get real-time market data (price, volume, holders, liquidity) | `dynamic` | | Get candlestick chart / OHLCV data | `kline` | ## Supported Chains | Chain | `chainId` | |-------|-----------| | Ethereum | `1` | | BSC | `56` | | Base | `8453` | | Solana | `CT_501` | All four commands (`search`, `meta`, `dynamic`, `kline`) use the same `chainId` values. ## How to Call APIs ```bash node <skill-dir>/scripts/cli.mjs <command> '<json_params>' ``` Example: ```bash node <skill-dir>/scripts/cli.mjs search '{"keyword":"

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Supported Chains
  4. How to Call APIs
  5. Commands
  6. Rules
  7. Full CLI Reference
Ships with 2 files
  • references/cli.md
  • scripts/cli.mjs
Commands it runs
node <skill-dir>/scripts/cli.mjs <command> '<json_params>'
node <skill-dir>/scripts/cli.mjs search '{"keyword":"<keyword>","chainIds":"56"}'
More from binance-skills-hub
All skills →
About this skill
What does the query-token-info skill do?

Per-token details for a specific token identified by keyword, symbol, or contract address: (1) search — find tokens by keyword/symbol/contract; (2) meta — static info: name, symbol, logo, social links, creator, official website; (3) dynamic — real-time market data: price, 24h change, volume, holder count, liquidity; (4) kline — OHLCV candlestick data for technical analysis. Use for: "price of $X", "search for token Y", "kline chart for $Z", "who created $W", "social links for $V", "holder count of $U", "candlestick data", "find the contract address of <token>".

How do I install it?

Run `npx skills add binance/binance-skills-hub --skill query-token-info --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.

Keep going