okx

OKX exchange integration. Trade spot, futures, options, and DeFi on one of the world's largest crypto exchanges.

Install with Tessl CLI

npx tessl i github:Demerzels-lab/elsamultiskillagent --skill okx

What are skills?

Review — 48%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 platform and trading categories but lacks explicit trigger guidance and concrete action verbs. It reads more like marketing copy than a functional skill selector. The absence of a 'Use when...' clause significantly weakens Claude's ability to choose this skill appropriately.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions OKX, wants to trade on OKX exchange, or asks about OKX-specific features'

Replace vague 'Trade spot, futures...' with concrete actions: 'Place spot/futures/options orders, check account balances, view positions, set stop-losses'

Include common user phrases: 'buy crypto on OKX', 'OKX API', 'OKX wallet', 'OKX trading'

Dimension	Reasoning	Score
Specificity	Names the domain (OKX exchange) and lists trading types (spot, futures, options, DeFi), but doesn't describe concrete actions like 'place orders', 'check balances', 'set stop-losses'. The actions are implied rather than explicitly stated.	2 / 3
Completeness	Describes what (OKX trading capabilities) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all.	1 / 3
Trigger Term Quality	Includes good keywords like 'OKX', 'crypto', 'spot', 'futures', 'options', 'DeFi', and 'exchange', but misses common variations users might say like 'cryptocurrency trading', 'buy/sell crypto', 'trading bot', or 'portfolio'.	2 / 3
Distinctiveness Conflict Risk	The OKX-specific branding provides some distinctiveness, but 'crypto exchange' and trading terms could overlap with other exchange integrations (Binance, Coinbase, etc.). The description doesn't clearly differentiate when to use OKX vs other crypto 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.

This skill provides solid, executable API examples for OKX trading operations with proper authentication handling. However, it includes unnecessary marketing content (referral section), lacks explicit validation workflows for financial operations, and doesn't deliver on advertised features like futures/options trading despite mentioning them.

Suggestions

Remove or minimize the referral/commission marketing section - it doesn't help Claude execute trades

Add explicit validation workflows for trading: check balance -> display order preview -> get user confirmation -> execute -> verify execution result

Either add documentation for futures/options/DeFi features or remove them from the features list to avoid misleading

Add error recovery guidance - what to do when signature fails or order is rejected

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with executable code examples, but includes some unnecessary content like the referral/commission marketing section and feature bullet points that don't add actionable value for Claude.	2 / 3
Actionability	Provides fully executable curl commands with proper authentication, signature generation, and jq parsing. All examples are copy-paste ready with clear variable substitution patterns.	3 / 3
Workflow Clarity	Safety rules mention verification steps but lack explicit validation workflows. Trading operations (placing orders, canceling) don't show a clear sequence with checkpoints like 'verify balance -> confirm details -> execute -> verify result'.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline in one file. Advanced features like futures/options trading mentioned in features list have no corresponding documentation or references to separate files.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 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

Reviewed: 8 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.