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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 well-structured data-source skill: the body is an actionable overview with executable examples, exact parameter formats, and clean one-level-deep routing to verified per-endpoint references and scripts. Minor improvements available are trimming marketing/meta text and adding basic API error-handling guidance to the Quick Start.

Suggestions

Trim the marketing claim ('the world's second-largest cryptocurrency exchange') and the meta blockquote about link conventions, which add tokens without operational value.

Add a brief error-handling note to the Quick Start, e.g. check that the response 'code' field is 0 and retry/back off on rate-limit errors.

Mention the two script examples earlier (in Quick Start) so a user finds the complete retrieval patterns before the endpoint table.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, high-value material (parameter table, endpoint table, executable snippets), but the marketing fluff 'the world's second-largest cryptocurrency exchange' and the meta blockquote about link-authoring conventions are over-explanation that could be trimmed — anchor 4, not the fully lean anchor 5.	4 / 5
Actionability	Guidance is fully executable and copy-paste ready: a pip install command, a complete runnable Python snippet with a concrete instrument ('BTC-USDT'), exact parameter formats (instId/bar/instType syntax), and links to two complete scripts plus per-endpoint detailed docs — matching anchor 5.	5 / 5
Workflow Clarity	The Quick Start gives a clear sequence (install runtime and dependencies → locate endpoint in the docs → run the example), and the skill is read-only so the destructive/batch validation cap does not apply; however, there is no error-handling guidance (e.g., checking the response 'code' field, rate limits), so it falls short of anchor 5's explicit checkpoints.	4 / 5
Progressive Disclosure	The body is a concise overview that routes all per-endpoint detail to 13 reference files (verified to exist) organized one level deep in three category directories, surfaced through a navigable table with descriptive link text, plus two linked script examples — a clear, well-signaled structure matching anchor 5.	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 data-source description with concrete capability listing and strong distinctiveness from the OKX naming. Its main weaknesses are the missing explicit 'Use when...' trigger clause (capping completeness) and incomplete natural-keyword coverage for prominent features like the order book and tickers.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for crypto prices, candlesticks, funding rates, or other OKX/exchange market data.'

Replace 'and more' with additional concrete capabilities such as order book depth and recent trades, which also improves trigger-term coverage.

Add natural synonym keywords users would actually say ('crypto prices', 'ticker', 'order book') to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	The description names the domain (OKX V5 REST API market data) and several concrete actions — 'real-time prices, candlesticks, funding rates, open interest' — but the vague trailing 'and more' and omission of order book/trades leave minor coverage gaps, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clearly stated ('Uses the OKX V5 REST API to retrieve spot, derivatives, index, and other crypto market data'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 3; the 'when' is only weakly implied by 'cryptocurrency market data interface'.	3 / 5
Trigger Term Quality	Natural terms like 'real-time prices', 'candlesticks', 'funding rates', and 'open interest' cover what a user would plausibly say, but common variations such as 'crypto prices', 'ticker', 'order book', or 'OHLC' are missing, fitting anchor 4 (good coverage, a few natural terms missing) rather than 5.	4 / 5
Distinctiveness Conflict Risk	Naming a specific exchange ('OKX') and a specific API version ('V5 REST API') carves a clear niche with distinct triggers and minimal overlap risk with generic market-data or other-exchange skills, matching anchor 5.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 251b094

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.