CtrlK
BlogDocsLog inGet started
Tessl Logo

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>".

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, highly actionable body: executable CLI invocations for all four commands, a useful Rules section capturing real response quirks, and clean progressive disclosure to a single reference file. The only refinements are minor redundancy in the Overview and an implied (not explicit) search-to-detail chaining step.

Suggestions

Drop or merge the Overview's four-capability bullets with the 'When to Use This Skill' table to remove the capability list stated twice in close succession.

Add a one-line workflow note that 'search' returns a contractAddress to pass into 'meta', 'dynamic', and 'kline', making the cross-command flow explicit instead of implied.

DimensionReasoningScore

Conciseness

The body uses compact tables and a concrete Rules section with no concept-padding Claude already knows, but the Overview paragraph restates the four capabilities that the 'When to Use This Skill' table immediately repeats — a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

Every command ships a copy-paste-ready invocation ('node <skill-dir>/scripts/cli.mjs search '{"keyword":"<keyword>","chainIds":"1,56,8453,CT_501"}'') with required args and real parameter values, covering all four common cases.

5 / 5

Workflow Clarity

Each subcommand is an unambiguous single read-only action and intent is mapped to command in a table, but the cross-command pattern (use 'search' to obtain a contractAddress, then feed it to 'meta'/'dynamic'/'kline') is only implied rather than sequenced — a minor gap.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview that defers per-subcommand invocations, parameter tables, return-field tables, and response samples to a clearly signaled, one-level-deep references/cli.md (a real bundle file), with scripts/cli.mjs as the executable — matching clear overview with well-signaled one-level references.

5 / 5

Total

18

/

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, well-structured description that concretely enumerates four capabilities with their fields and pairs them with natural-language trigger phrases. Its only soft spot is a slight adjacency to other crypto market-data skills, which keeps distinctiveness just short of maximal.

DimensionReasoningScore

Specificity

Names the domain and four concrete subcommands (search, meta, dynamic, kline), each enumerating specific fields (e.g. 'price, 24h change, volume, holder count, liquidity'; 'name, symbol, logo, social links, creator, official website'), giving comprehensive coverage rather than just 1-2 actions.

5 / 5

Completeness

It explicitly answers both 'what' (per-token details via four read endpoints) and 'when' (a 'Use for:' clause with concrete trigger phrases), matching the anchor that requires explicit what AND when with triggers.

5 / 5

Trigger Term Quality

The 'Use for:' clause lists natural user phrasings ('price of $X', 'search for token Y', 'kline chart for $Z', 'who created $W', 'holder count of $U') including synonyms (kline chart / candlestick data), matching comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (on-chain token info across specific chains with distinct triggers), but sits adjacent to other crypto/market-data skills so carries minor overlap risk rather than minimal — fitting 'mostly distinct; minor overlap risk' better than the 5 anchor.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.