okx
OKX exchange integration. Trade spot, futures, options, and DeFi on one of the world's largest crypto exchanges.
45
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/okx/SKILL.mdQuality
Discovery
32%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 identifies the specific exchange (OKX) and broadly lists tradeable instrument types, which provides some distinctiveness. However, it lacks specific concrete actions beyond 'trade', reads more like marketing copy than a functional skill description, and critically omits any 'Use when...' guidance for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user mentions OKX, wants to trade on OKX, or asks about OKX account management, orders, or positions.'
List specific concrete actions such as 'place and cancel orders, check balances, retrieve market data, manage positions, view trade history' instead of the generic 'trade'.
Include natural user terms like 'cryptocurrency trading', 'order book', 'limit order', 'market order', 'OKX API' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (OKX exchange) and lists some actions (trade spot, futures, options, DeFi), but doesn't describe specific concrete actions like placing orders, checking balances, managing positions, or retrieving market data. | 2 / 3 |
Completeness | Describes what at a high level (OKX exchange integration, trading various instruments) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also fairly shallow, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'OKX', 'spot', 'futures', 'options', 'DeFi', and 'crypto exchanges', but misses common user terms like 'trading', 'order', 'portfolio', 'market data', 'API', or 'cryptocurrency'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'OKX' specifically helps distinguish it from other crypto exchange skills, but the broad 'crypto exchanges' and 'DeFi' terms could overlap with other exchange or DeFi-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, executable curl-based API examples for OKX trading operations with proper authentication handling. However, it suffers from including promotional/referral content that wastes tokens, lacks explicit validation workflows critical for financial operations, and could better organize its extensive content through progressive disclosure into separate files for different trading modes.
Suggestions
Remove the referral/commission section entirely — it's promotional content that doesn't help Claude execute tasks and wastes context tokens.
Add explicit validation steps to trading workflows: check balance before order, verify order status after placement, confirm cancellation succeeded with a follow-up query.
Split advanced features (futures, options, earn/staking) into separate referenced files rather than listing them as features without implementation details.
Remove the 'Popular Trading Pairs' and 'Order Types' tables — Claude already knows these, and they can be discovered via the API docs link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the referral/commission section (not relevant to Claude's task execution), the 'Popular Trading Pairs' table (Claude knows these), and order type descriptions that are basic knowledge. However, the code examples themselves are lean and the structure is reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable curl commands with proper authentication, signature generation, and jq parsing. Each API operation is copy-paste ready with concrete examples including specific endpoints, headers, and request bodies. | 3 / 3 |
Workflow Clarity | Safety rules mention verifying before execution, but there are no explicit validation checkpoints in the trading workflows themselves. For destructive financial operations (placing orders, canceling orders), the skill lacks feedback loops like checking order status after placement or verifying balance before and after trades. The steps are listed but validation is implicit rather than built into the workflow. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic document with no bundle files to offload detailed API references. Advanced features like futures trading, options, staking, and DeFi are listed in the features section but never elaborated on or linked to separate files. The document could benefit from splitting authentication, trading operations, and advanced features into separate referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.