OKX OnChainOS — Skills Directory

What this file is: a directory page that points to OKX's official onchainos-skills repo. It contains no logic of its own — every sub-skill below lives upstream at okx/onchainos-skills and is fetched fresh on install, so you always get the latest version.

OKX OnChainOS is a suite of 8 specialized sub-skills covering on-chain trading, market analytics, smart-money signals, DeFi investing & positions, wallet ops, security scanning, payment protocols, agent identity & task marketplace, and crypto news & sentiment across 20+ blockchains (Ethereum, Solana, XLayer, Base, BSC, Arbitrum, Polygon, Optimism, Avalanche, TRON, …).

Most sub-skills drive a single binary, onchainos, which is downloaded on first use. A subset of capabilities (read-only data) can also be accessed without the binary, via Starchild's sc-proxy — see Authentication options below.

How install actually works

# Install one sub-skill (recommended — pulls just what you need)
npx skills add okx/onchainos-skills@<sub-skill-name>

# Or via long form
npx skills add https://github.com/okx/onchainos-skills --skill <sub-skill-name>

# Install everything (auto-detects your environment and installs accordingly)
npx skills add okx/onchainos-skills

Each sub-skill ships its own SKILL.md + reference docs + trigger phrases, so you can pull just what you need.

Plugin marketplace (alternative):

/plugin marketplace add okx/onchainos-skills
/plugin install onchainos-skills

CLI install (the onchainos binary — auto-detects platform, verifies SHA256, installs to ~/.local/bin or %USERPROFILE%\.local\bin):

# macOS / Linux
curl -sSL https://raw.githubusercontent.com/okx/onchainos-skills/main/install.sh | sh
# add `-s -- --beta` for the latest pre-release (opt-in only; never downgrades)

# Windows
irm https://raw.githubusercontent.com/okx/onchainos-skills/main/install.ps1 | iex

Wallet — default to the user's Agent Wallet

Use the platform wallet skill for signing and broadcasting. OKX DEX endpoints return unsigned calldata ({to, value, data, ...}); feed it to wallet_transfer(data=<calldata>) and you're done. No separate OKX wallet needed.

Only use the OnchainOS TEE wallet (onchainos wallet login <email>) when the user explicitly asks for it.

Authentication options (read this before invoking anything)

There are two distinct paths. Pick based on what the agent needs to do:

Path A — Direct HTTP via Starchild sc-proxy (no API Key needed)

For read-only data lookups (prices, K-line, smart-money signals, token analytics, security checks, public-address portfolios — ≈ 80 % of OnchainOS capabilities), the agent can skip the CLI entirely and call https://web3.okx.com/... directly through sc-proxy:

from core.http_client import proxied_get
r = proxied_get(
    "https://web3.okx.com/api/v6/dex/aggregator/supported/chain",
    headers={"SC-CALLER-ID": f"chat:{thread_id}"},
)

sc-proxy auto-injects platform OKX credentials, signs each request with HMAC-SHA256, and bills the caller's Starchild credits.

• Cost: $0.001 / request
• Rate limit: 60 req/min
• Setup: none
• Limits: data only — cannot send transactions or manage wallets

Path B — onchainos CLI with your own OKX Web3 API Key

For wallet ops (wallet login, wallet send, wallet contract-call), DEX swaps that need execution, payments, and any other CLI-driven workflow.

The onchainos CLI ships with built-in sandbox API keys that work out of the box for local testing — no setup required. These keys are shared, rate-limited, and for evaluation only: do NOT use them in production or with real assets. Any failures or losses from using the built-in keys are the caller's responsibility.

For production, bring your own credentials:

1. Apply at web3.okx.com → OnchainOS → Dev Portal
2. Set env vars (or a .env in the project root — never commit it):

   export OKX_API_KEY=<your key>
   export OKX_SECRET_KEY=<your secret>
   export OKX_PASSPHRASE=<your passphrase>
   

3. Run any sub-skill's CLI commands.

Why the CLI can't use sc-proxy