CtrlK
BlogDocsLog inGet started
Tessl Logo

binance-tokenized-securities-info

Query Ondo tokenized US stock data on Binance Web3. Covers: supported stock token list, RWA metadata (company info, attestation reports), market and per-asset trading status (with corporate action codes for earnings, dividends, splits), real-time on-chain data (token price, holders, circulating supply, market cap), US stock fundamentals (P/E, dividend yield, 52-week range), and token K-Line/candlestick charts. Use this skill when users ask about: - Tokenized stock price, holders, or on-chain data for specific tickers - Whether a stock token is tradable, paused, or halted - Ondo RWA token list or which US stocks are available on-chain - Corporate actions affecting a token (dividends, stock splits, earnings halt) - Stock token K-Line or candlestick chart data - Comparing on-chain token price vs US stock price NOT for general crypto tokens (BTC, ETH, SOL, etc.) — use query-token-info for those.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is highly actionable and well-sequenced with executable examples, validation guidance, and clear gotchas, scoring at the top of actionability and workflow clarity. It is held back slightly by inlining the full per-API reference rather than splitting it into reference files, and by minor repetition of the multiplier/field warnings.

Suggestions

Move the per-API response-field tables and JSON examples into a separate references file (e.g. REFERENCE.md) and keep SKILL.md as an overview pointing to it, to improve progressive disclosure and reduce token load.

De-duplicate the sharesMultiplier guidance and the volume24h warning — state each once (in Notes and the relevant field table) and cross-reference rather than repeating full explanations.

DimensionReasoningScore

Conciseness

The content is largely efficient — API tables, curl examples, and field docs with no padding about what tokens/stocks are — but the 614-line body repeats the multiplier formula and several field descriptions (e.g. volume24h warning) in multiple places, leaving minor instances that could be tightened.

4 / 5

Actionability

Every API includes full executable curl commands with required headers, complete request parameter tables, realistic JSON response examples, and explicit gotchas (e.g. the volume24h misleading-field warning and URL-prefix instructions), giving copy-paste-ready guidance across the common cases.

5 / 5

Workflow Clarity

The Recommended Workflows table sequences multi-API flows (API 1 → API 5, API 3 → API 4, etc.), the 'Token ≠ Share' key concept and Notes §6 supply a validation/correctness checkpoint (compute referencePrice, read multiplier from API at query time), and reason-code/corporate-action tables provide explicit error-state interpretation and recovery.

5 / 5

Progressive Disclosure

Structure is good: a concise overview table and per-API sections with one in-file cross-reference (the Status Info → API 4 link) at one level deep. However all six APIs' full reference material is inlined into SKILL.md with no separate reference files, so bulk content that could be split out remains in the main file.

4 / 5

Total

18

/

20

Passed

Description

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

The description is exemplary: it concisely enumerates concrete capabilities, provides explicit 'Use when' trigger phrases with synonyms, and draws a clear boundary against a sibling skill. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities (stock token list, RWA metadata, trading status, on-chain data, fundamentals, K-Line charts) and specific metrics (P/E, dividend yield, 52-week range), giving comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers 'what' (the six coverage areas) and 'when' via the bulleted 'Use this skill when users ask about' trigger list with concrete phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural user phrases and synonyms comprehensively — 'tokenized stock price', 'holders', 'tradable/paused/halted', 'K-Line or candlestick chart data', plus a clear exclusion for general crypto tokens, matching the anchor's expectation of synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (Ondo tokenized US stocks on Binance Web3) with distinct triggers and an explicit 'NOT for general crypto tokens — use query-token-info' boundary, minimizing conflict risk.

5 / 5

Total

20

/

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

skill_md_line_count

SKILL.md is long (614 lines); consider splitting into references/ and linking

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.