CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

79%

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 ./a_全网优秀资源/10_大模型/07_skill包/vibe_trading_skills/okx-market/SKILL.md
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.

The body is an efficient, highly actionable overview: executable code, concrete parameter formats, and a clean endpoint index that pushes all per-endpoint detail into one-level-deep reference files and scripts. Only minor improvements are available — trimming the marketing line and adding an explicit response-code validation step to the inline workflow.

DimensionReasoningScore

Conciseness

The body is lean: a short overview, a quick-start with install command and one working example, compact parameter-format bullets, and an endpoint table. Minor trimmable padding remains — "The data comes from OKX, the world's second-largest cryptocurrency exchange" is marketing filler, and the Overview partially restates the frontmatter description. Not a 5 due to those few unnecessary tokens; well above a 3 since virtually all content adds non-obvious API-specific knowledge.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: a working `pip install` command, a correct spot-ticker Python example, concrete parameter formats (instId patterns per instrument class, bar values, timestamp format), response semantics ("code=0 indicates success, and data is returned in the data field"), and links to two real, complete, error-handling scripts. The common cases (ticker, batch tickers, funding rates, candles) are covered by the verified script and reference files.

5 / 5

Workflow Clarity

Quick Start lays out a clear sequence — install dependencies → note no auth needed → locate the endpoint in the table → retrieve data with Python — and the Response Format bullet documents code=0 as a success checkpoint. Not a 5 because the workflow itself has no explicit validation/feedback step (the inline example indexes data[0] without checking code; error checking only appears in the linked scripts), and above a 3 because the sequence is complete and the success-checkpoint semantics are documented inline.

4 / 5

Progressive Disclosure

Textbook structure: SKILL.md is a concise overview whose endpoint table routes each of the 13 endpoints to a one-level-deep reference file (all verified to exist on disk), with script examples split into scripts/ and clearly signaled by link. Navigation is easy and no detail content is inlined that belongs in references.

5 / 5

Total

18

/

20

Passed

Description

66%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 solid, concrete description that clearly communicates what the skill does and is well-branded to OKX, with good natural keyword coverage. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and limits when-to-use guidance.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for crypto prices, candlestick/OHLC data, funding rates, or open interest, or mentions OKX or cryptocurrency market data."

Include a few more natural synonyms users say, such as "ticker", "order book", "K-line", or "trading pairs", to broaden trigger coverage.

Drop the vague "and more" tail and replace it with the remaining concrete capabilities (e.g. mark price, order book depth, index prices) to remove filler.

DimensionReasoningScore

Specificity

The description lists several concrete data-retrieval capabilities ("retrieve spot, derivatives, index, and other crypto market data, including real-time prices, candlesticks, funding rates, open interest") grounded in a named API ("OKX V5 REST API"). It falls short of a 5 because the trailing "and other crypto market data ... and more" is vague filler, and above a 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

The "what" is clearly and concretely answered (retrieve OKX spot/derivatives/index market data: prices, candlesticks, funding rates, open interest), but there is no "Use when..." clause or equivalent trigger guidance anywhere — the description only adds "No authentication required, free to use", which is a constraint, not a "when". Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good coverage of natural domain terms users would say: "cryptocurrency market data", "crypto", "real-time prices", "candlesticks", "funding rates", "open interest", "spot", "derivatives". Not a 5 because common variations like "ticker", "order book", "K-line", "OHLC", or "trading" are missing; not a 3 because the keyword set is broad and natural, not merely "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The explicit "OKX" branding plus derivative-specific terms ("funding rates", "open interest") establish a clear niche distinct from generic data skills. Not a 5 because the generic trigger phrases (crypto prices, candlesticks) overlap with market-data skills for other exchanges, so it could trigger alongside a Binance/Bybit skill; well above a 3 since OKX is explicitly named.

4 / 5

Total

15

/

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
charliedream1/ai_quant_trade
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.