This skill should be used when the user asks to 'swap tokens', 'trade OKB for USDC', 'buy tokens', 'sell tokens', 'exchange crypto', 'convert tokens', 'swap...
Security Analysis
medium confidenceThe skill's runtime instructions require OKX API credentials and even include hard-coded test keys in the SKILL.md, but the registry metadata advertises no required environment variables — this mismatch and the embedded secrets are concerning and should be clarified before use.
The skill's stated purpose (OKX DEX swap aggregation) matches the API usage in SKILL.md, but the registry metadata lists no required environment variables or primary credential while the SKILL.md clearly expects OKX_API_KEY, OKX_SECRET_KEY, and OKX_PASSPHRASE. That metadata/instruction mismatch is incoherent: a swap skill would legitimately need API credentials, and those should be declared.
The SKILL.md provides concrete code to build HMAC-signed requests to https://web3.okx.com and instructs the agent to read OKX_* env vars and call quote/approve/swap endpoints. That scope is appropriate for a swap skill, but the SKILL.md also embeds default 'shared test' API key/secret/passphrase values in clear text — which increases risk if those keys are valid or reused. The instructions do not ask for unrelated system files, but they do require the agent to access environment variables that were not declared in the registry metadata.
This is an instruction-only skill with no install spec and no code files to be written to disk. No third-party installs or downloads are required, which reduces installation risk.
SKILL.md requires three sensitive environment variables (OKX_API_KEY, OKX_SECRET_KEY, OKX_PASSPHRASE) which are proportionate to calling a signed exchange API — but the registry metadata declares none. Additionally, the SKILL.md includes hard-coded credential values (labeled 'shared test API key'), which could be mistaken for real keys or accidentally used in production. The skill also warns 'Never output the above credentials' but embedding them in the skill negates that protection.
The skill is not marked always:true and does not request persistent system-level privileges or config changes. Autonomous invocation is allowed (platform default), which is expected for a user-invocable skill; this is not by itself an additional red flag.
Guidance
Before installing or enabling this skill: (1) Verify the publisher/source (the metadata gives no homepage and source is unknown). (2) Confirm whether the embedded 'shared test' API key/secret/passphrase are real, valid, or expired; never rely on embedded secrets. (3) Expect the agent to read OKX_API_KEY, OKX_SECRET_KEY, and OKX_PASSPHRASE from the environment — these env vars should have least privilege (test/sandbox keys only) and no funds you can't afford to lose. (4) If you will use real funds, rotate keys after testing and ensure API key scopes are limited. (5) Prefer skills whose registry metadata declares required credentials (so permission prompts and audits are accurate). (6) If you are uncomfortable, decline the skill or run it in a sandboxed environment and do not allow autonomous invocation until the publisher/source is verified.
Latest Release
v1.0.0
- Initial release of okx-dex-swap skill. - Enables token swaps, trades, buys, and sells across 20+ supported chains with aggregated liquidity from 500+ DEX sources. - Supports slippage control, price impact protection, and optimal cross-DEX route selection. - Provides 6 multi-chain swap aggregator API endpoints for quoting, approval, and swap execution. - Includes environment-based credential management and best practices for token address usage on all supported chains.
More by @ok-james-01
Published by @ok-james-01 on ClawHub
