CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

okx-market

OKX cryptocurrency market data interface. Uses the OKX V5 REST API to retrieve spot, derivatives, index, and other crypto market data, including real-time prices, candlesticks, funding rates, open interest, and more. No authentication required, free to use.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/okx-market/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, information-dense skill body: executable quick start, compact parameter reference, and an excellent one-level-deep endpoint index into real reference documentation. The only weaknesses are minor: unexplained environment-specific imports in the example code and a few tokens of authoring meta-commentary that could be trimmed.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanation of what exchanges, REST, or candlesticks are; parameter formats are compact lookup lists and the endpoint table is pure index. It stops short of anchor 5 because of the meta blockquote about link conventions aimed at skill authors rather than the agent, and the promotional 'world's second-largest cryptocurrency exchange' claim — tokens that earn no place.

4 / 5

Actionability

The quick start gives concrete, copy-paste-ready code with a real URL and params, and the two linked scripts plus per-endpoint reference docs are fully executable. The minor gap keeping it from anchor 5: the example imports 'src.data_gateway.reads', a module not provided or explained anywhere, while the install step only covers 'requests pandas' — the code as written will not run without that dependency.

4 / 5

Workflow Clarity

This is a simple, read-only, single-task skill, and the single action is unambiguous: pick an endpoint from the indexed table, open its reference doc for params/outputs, call 'public_http_get'. The quick start sequences setup (install, no auth needed, find endpoint, retrieve) clearly, and the per-endpoint docs include response-field tables and error-code conventions ('code=0 indicates success'), so the simple-skill exception applies. No destructive or batch operations, so no validation cap is triggered.

5 / 5

Progressive Disclosure

The body is a clean overview: a getting-started section, a compact parameter reference, and an endpoint index table that clearly signals all 13 reference docs (title, category, description) organized into three one-level-deep category folders — verified to exist with no nested references — plus two clearly linked example scripts. Content is appropriately split and navigation is trivial.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific, well-scoped description for a data-retrieval skill with good natural keyword coverage and a distinct OKX niche. Its main weakness is the missing 'when to use' guidance: there is no 'Use when...' clause or equivalent, which caps completeness. Adding explicit trigger phrasing would round it out.

Suggestions

Append a trigger clause such as 'Use when the user asks for OKX/crypto prices, tickers, candlesticks, funding rates, or open interest' to fix the missing 'when' guidance that caps completeness at 3.

Add common synonyms users actually say — 'ticker', 'OHLC/K-line', 'order book depth' — to broaden trigger-term coverage.

Drop the hedge 'and other crypto market data ... and more' in favor of one or two more concrete data types (e.g., 'order books', 'recent trades') for tighter specificity.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities tied to a named API — 'real-time prices, candlesticks, funding rates, open interest' across 'spot, derivatives, index' — matching the several-specific-actions anchor. It falls short of anchor 5 because 'and other crypto market data ... and more' hedges coverage and 'retrieve' is the only action verb, unlike the multi-verb comprehensive example.

4 / 5

Completeness

The 'what' is clear and concrete (retrieve spot/derivatives/index market data via the OKX V5 REST API), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps this dimension at 3. 'No authentication required, free to use' describes access requirements, not when to invoke the skill, so it cannot lift the score to 4.

3 / 5

Trigger Term Quality

Natural terms a crypto-data user would say are present ('cryptocurrency market data', 'candlesticks', 'funding rates', 'open interest', 'OKX'), giving good coverage. It is not anchor 5 because common synonyms and variations users plausibly say — 'ticker', 'OHLC', 'order book', 'price feed', 'crypto exchange data' — are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the specific exchange ('OKX') and API version ('OKX V5 REST API') establishes a clear niche with distinct triggers and minimal conflict risk against generic market-data or other-exchange skills. It does not exhibit the overlap-with-closely-related-skills weakness of anchor 4 because the source is uniquely identified.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 13 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/okx-market/SKILL.md

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.