How do I install the Okx Trading skill?

Run npx skillmds@latest add jasonviipers/okx-trading in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Okx Trading safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Okx Trading?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Okx Trading free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Okx Trading?

jasonviipers (@jasonviipers) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Okx Trading by jasonviipers — Agent Skill

Name: Okx Trading
Author: jasonviipers

Okx Trading

Implement and maintain the OKX broker/provider integration for this workspace using okx-api SDK best practices, including auth/signing, spot/margin/futures/options trading, market/account endpoints, rate limiting, websocket subscriptions, and OKX error handling. Use when adding or changing any code under src/providers/okx or when an LLM needs canonical SDK usage patterns derived from .trae/okx-api-llm.txt.

jasonviipers bcc63a4 3 files · 6.6 KB Updated Sep 17, 2026

File contents

OKX Provider Broker Skill

Use this workflow when editing src/providers/okx/*.

1. Load only needed references

For SDK usage patterns and method names, read references/okx-sdk-usage.md.
For error-to-action mapping, read references/okx-error-map.md.
For full source context, consult .trae/okx-api-llm.txt only for missing details.

2. Keep architecture compatibility

Preserve compatibility with src/providers/types.ts (BrokerProvider, MarketDataProvider, OptionsProvider).
Put OKX-specific expanded APIs behind OKX provider interfaces (for example OkxTradingProvider) while keeping generic provider methods working.
Ensure src/providers/broker-factory.ts can return OKX providers without adapter breakage.

3. Enforce auth and signing rules

Require all three credentials: API key, secret, passphrase.
Use OKX signing prehash: timestamp + UPPERCASE_METHOD + requestPathWithQuery + rawBody.
Use HMAC SHA256 base64 signing for both REST and private websocket auth via customSignMessageFn.
Pass demoTrading: true for simulated trading.

4. Trading and market coverage minimums

Trading: spot, margin, swap/futures, options order placement + cancel/query + list.
Account: balances, positions, bills/transactions, fills.
Market data: ticker(s), order book, trades, candles, instruments.
Websocket: ticker, orderbook, trades, candles, account/orders/positions subscriptions.

5. Error and rate-limit behavior

Parse and map OKX code + msg errors into internal error categories.
Handle known auth/order/risk/rate-limit codes explicitly.
Apply request throttling + retry with exponential backoff and jitter for retryable failures.
Avoid retrying invalid input/auth failures.

6. Documentation requirements for code changes

Update src/providers/okx/README.md with examples that match current method names.
Include one example each for: spot order, futures order, option order, account history, websocket subscription.
Keep examples SDK-realistic and aligned with references/okx-sdk-usage.md.

---name: okx-tradingdescription: Implement and maintain the OKX broker/provider integration for this workspace using okx-api SDK best practices, including auth/signing, spot/margin/futures/options trading, market/account endpoints, rate limiting, websocket subscriptions, and OKX error handling. Use when adding or changing any code under src/providers/okx or when an LLM needs canonical SDK usage patterns derived from .trae/okx-api-llm.txt.---# OKX Provider Broker SkillUse this workflow when editing `src/providers/okx/*`.## 1. Load only needed references- For SDK usage patterns and method names, read `references/okx-sdk-usage.md`.- For error-to-action mapping, read `references/okx-error-map.md`.- For full source context, consult `.trae/okx-api-llm.txt` only for missing details.## 2. Keep architecture compatibility- Preserve compatibility with `src/providers/types.ts` (`BrokerProvider`, `MarketDataProvider`, `OptionsProvider`).- Put OKX-specific expanded APIs behind OKX provider interfaces (for example `OkxTradingProvider`) while keeping generic provider methods working.- Ensure `src/providers/broker-factory.ts` can return OKX providers without adapter breakage.## 3. Enforce auth and signing rules- Require all three credentials: API key, secret, passphrase.- Use OKX signing prehash: `timestamp + UPPERCASE_METHOD + requestPathWithQuery + rawBody`.- Use HMAC SHA256 base64 signing for both REST and private websocket auth via `customSignMessageFn`.- Pass `demoTrading: true` for simulated trading.## 4. Trading and market coverage minimums- Trading: spot, margin, swap/futures, options order placement + cancel/query + list.- Account: balances, positions, bills/transactions, fills.- Market data: ticker(s), order book, trades, candles, instruments.- Websocket: ticker, orderbook, trades, candles, account/orders/positions subscriptions.## 5. Error and rate-limit behavior- Parse and map OKX `code` + `msg` errors into internal error categories.- Handle known auth/order/risk/rate-limit codes explicitly.- Apply request throttling + retry with exponential backoff and jitter for retryable failures.- Avoid retrying invalid input/auth failures.## 6. Documentation requirements for code changes- Update `src/providers/okx/README.md` with examples that match current method names.- Include one example each for: spot order, futures order, option order, account history, websocket subscription.- Keep examples SDK-realistic and aligned with `references/okx-sdk-usage.md`.

Frequently asked questions