BC cex-trader
Unified CEX trading capability layer for AI agents. Supports OKX and Binance spot and futures trading, account balance queries, order management, position queries, leverage settings, margin mode configuration, market data, and guided API key setup flow. MCP tools: cex-spot-place-order, cex-spot-cancel-order, cex-spot-get-orders, cex-futures-place-order, cex-futures-cancel-order, cex-futures-get-positions, cex-futures-set-leverage, cex-futures-close-position, cex-account-get-balance, cex-account-get-info, cex-market-get-instruments, cex-market-get-kline, cex-market-get-orderbook, cex-market-get-ticker, cex-setup-check, cex-setup-save, cex-setup-verify. Supports action semantics (open_long/open_short/close_long/close_short) and native side+posSide parameters. Built-in idempotency check, rate limiting, and risk controls (margin monitoring, position limits). Supports OKX and Binance exchanges. Swap tokens, buy crypto, sell crypto, CEX trade, exchange order, spot order, futures order, perpetual contract, leverage trading, close position, binance trade, okx trade.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1075 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 951 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1074: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 18 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 38.