Install
npx skills add okx/onchainos-skillsWho is it for
If you want an AI coding assistant to connect to OKX OnchainOS for token search, market data, and wallet balances instead of assembling REST calls yourself, this skill set is a better fit. The page also says it can execute swaps, broadcast transactions, view rankings, perform token-clustering analysis, and route users to third-party DApps, covering more than 20 chains.
The prerequisite is that you already have OKX API credentials. All skills require them; apply at
https://web3.okx.com/onchain-os/dev-portal
Then create .env in the project root and enter the three variable names OKX_API_KEY, OKX_SECRET_KEY, and OKX_PASSPHRASE. The page gives an assignment example with placeholders; those placeholder values are not repeated here. Without these three items, the skills that follow will not work. If you only want to browse the capability list and do not plan to provide keys, do not install it.
Complete your first attempt in 3 minutes
There is only one official installation command:
npx skills add okx/onchainos-skills
It automatically detects the environment and installs the package; the page says it can be used with several coding assistants that support skills. This changes the local Agent configuration. Before running it, confirm that npx is available, that the .env above already exists in the current directory, and that this is the environment you intend to write to. Do not paste keys into the conversation.
After installation, perform only a read-only check: have the assistant use okx-dex-market to find a token, or only query wallet balances. A successful signal is a token lookup or balance result, rather than a missing-credentials message. Stop there. The official flow describes “Search and Buy” as okx-dex-market (find a token) followed by okx-agentic-wallet (check funds and execute a transaction). Do not perform the second half on your first attempt. A swap or transaction broadcast submits an on-chain operation; before running one, have the assistant repeat the chain, token, amount, and skills it will call, then continue only after you confirm.
Use cases
Case one: search for a token first, then decide whether to check balances. Use okx-dex-market to search by name or contract, and if needed have okx-agentic-wallet check funds only, without executing a transaction. The page names XLayer, Solana, Ethereum, Base, BSC, Arbitrum, and Polygon among the supported chains, along with more than 20 other chains. It does not specify search fields or pagination. So the conclusion you can draw is limited: the lookup occurs within the listed chain range; the exact response fields depend on the actual response. If the assistant goes straight to execute trade, it has already left this use case.
Case two: swapping or broadcasting. The latter half of okx-agentic-wallet is check funds + execute trade; the capability list also includes transaction broadcasting. This uses the wallet and puts a transaction on-chain, so it is not a demonstration. The page does not mention slippage, approval limits, or how to revoke them. Use it only when you genuinely intend to place an order, and first confirm that the .env contains your own credentials. Rankings, token clustering, and third-party DApp routing appear in the capabilities, but there is no corresponding short skill name or command; those capabilities cannot be treated as provided operating steps.
Usage boundaries
Without all three OKX API credentials, none of the skills can be used. The page provides only the application entry point and .env variable names; it does not describe permission scopes, read-only keys, or what to do after a key is exposed. Do not treat the conversation history as required configuration.
The installation path is npx skills add okx/onchainos-skills. It installs automatically according to the environment. The page gives several client examples; do not interpret them as a closed list, and do not add another installer in parallel.
Use the chain names written on the page as the reference; do not expand “20+” into networks that are not named. On your first attempt, stop at token search or balance lookup. Any swap, broadcast, approval, or third-party DApp redirect must first be preceded by the assistant repeating the on-chain side effects that will occur; continue only after you confirm.