okx-defi

por okx

DeFi agregado pela OKX (sem DApp específico nomeado) — descoberta de produtos, execução de depósito/saque/resgate E visualização de posições. **Se o usuário nomear QUALQUER protocolo/DApp de terceiros (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), redirecione para okx-dapp-discovery — NÃO aqui, mesmo para 'mostrar minhas posições na Aave'.** Gatilhos INVEST: 'investir em DeFi', 'gerar rendimento', 'encontrar melhor APY', 'depositar/stake para rendimento', 'pesquisar produtos DeFi',...

npx skills add https://github.com/okx/onchainos-skills --skill okx-defi

OKX DeFi

Discover and manage multi-chain, OKX-aggregated DeFi products and positions through the onchainos defi CLI group.

Preflight

Preflight checks: At the start of each thread, complete the checks in ../okx-agentic-wallet/_shared/preflight.md. If missing, read _shared/preflight.md.

Intent Routing

Load only the reference files required by the selected route.

User IntentReference
Discover / search DeFi products, find best APYinvest.md
Product detail (APY, TVL, accepted tokens)invest.md
Deposit / stake / provide liquidityinvest.md
Withdraw / redeem a position (full or partial)invest.md
Claim rewards (platform / investment / V3 fee / bonus / unlocked principal)invest.md
APY history, TVL history, V3 depth / price chartsinvest.md
View DeFi positions / holdings overviewportfolio.md
Per-protocol position detailportfolio.md
Exact parameters / return schemas — invest, shared support, and charts commandsinvest-cli-reference.md
Exact parameters / return schemas — positions commandsportfolio-cli-reference.md
Errors / failed deposits / expired calldatainvest-troubleshooting.md
Errors / empty positions / address-format issuesportfolio-troubleshooting.md

Typical flow spans both: view positions (Portfolio) → redeem or claim (Invest). Read both reference files when the request chains them.

Route a named third-party DApp request—including protocol-specific APY, TVL, volume, history, or timeframe analysis—to okx-dapp-discovery. Generic cross-protocol yield/APY/TVL and V3-liquidity analysis stays here. Route token search/price/chart requests to okx-dex-market, and spot swaps, wallet balances, login, contract calls, or transaction broadcasts to okx-agentic-wallet.

Chain Name Support

The CLI resolves chain names automatically (for example, ethereum → 1, bsc → 56, solana → 501). Use the Chain Support table in portfolio.md for the DeFi-specific aliases.

Security

Address Resolution

When the user does NOT provide a wallet address, resolve it automatically from the Agentic Wallet before running any defi command:

1. onchainos wallet status          → check if logged in, get active account
2. onchainos wallet addresses       → get addresses grouped by chain category:
                                       - XLayer addresses
                                       - EVM addresses (Ethereum, BSC, Polygon, etc.)
                                       - Solana addresses
3. Match address to target chain:
   - EVM chains → use EVM address
   - Solana     → use Solana address
   - XLayer     → use XLayer address

Rules:

  • If the user provides an explicit address, use it directly — skip this step
  • If wallet is not logged in, ask the user to log in first (→ okx-agentic-wallet) or provide an address manually
  • If the user says "check all accounts" or "all wallets", use wallet balance --all to get all account IDs, then wallet switch <id> + wallet addresses for each account
  • Always confirm the resolved address with the user before proceeding if the account has multiple addresses of the same type

Address-Chain Compatibility

The --address and chain parameters must be compatible. EVM addresses (0x…) can only query EVM chains; Solana addresses (base58) can only query solana. Never mix them — the API will return error 84019 (Address format error).

  • 0x… address → only pass EVM chains: ethereum,bsc,polygon,arbitrum,base,xlayer,avalanche,optimism,fantom,linea,scroll,zksync
  • base58 address → only pass solana
  • Sui address → only pass sui; Tron address (T…) → only pass tron; TON address → only pass ton
  • If the user wants positions across both EVM and Solana, make two separate calls with the respective addresses

Global Notes

  • The wallet address parameter for ALL defi commands is --address
  • defi positions uses --chains (plural, comma-separated); defi position-detail uses --chain (singular)
  • Before reporting completion, verify the selected command succeeded, apply the output format and safety checks from its routed reference, and report any partial or failed on-chain step explicitly.

Mais skills de okx

okx-agent-identity
okx
Identidade de agente on-chain ERC-8004 na XLayer: registrar / criar / atualizar / ativar / desativar / pesquisar agentes; visualizar avaliações; listar serviços de agente; definir avatar. Funções: usuário (User / User Agent / Buyer / Client / 用户 / 买家 / 买方), asp (ASP / Provider / Provider Agent / Seller / Merchant / 提供者 / 商家 / 服务提供商 / 卖家 / 卖方), avaliador (Evaluator / Evaluator Agent / 仲裁者 / 评估者). Uso para: 注册agent / 注册ASP / 注册User / 注册用户 / 注册买家 / 注册卖家 / 注册服务提供商 / 注册仲裁者 / 创建用户 / 创建买家 / 创建卖家 / 我的agent / 我的ASP / 改agent / 更新agent...
developmentapi
okx-ai-guide
okx
We need to translate the given text from English to Brazilian Portuguese. The text is a description of an agent skill for OKX.AI. We must preserve the name "okx-ai-guide" but it's not in the text, so ignore. Preserve product names like OKX.AI, OKXAI, okx ai, okx-ai, okx.ai, etc. Also preserve URLs, numbers, technical terms. Do not add any extra commentary or labels. The translation should be natural in Brazilian Portuguese. The text: "OKX.AI (the Agent economic system) intro & onboarding entry. Use whenever the user asks what OKX.AI is, what it can do, how to use or get started with it, wants an OKX.AI tutorial / quickstart / help, or types the product name in any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, mis-typed Chinese like 啥是okxai) — e.g. what is OK
researchapidocument
okx-agentic-wallet
okx
We need to translate the given text from English to Brazilian Portuguese. The text describes an agent skill for OKX Agentic Wallet and its Gas Station feature. We must preserve the name "okx-agentic-wallet" if it appears, but it doesn't appear in the text. The text is inside <text> tags. We should not add any labels or extra commentary. Just translate the content. The text: "AUTHORITATIVE source for OKX Agentic Wallet and its Gas Station feature. Gas Station = OKX's stablecoin-gas feature on Solana via third-party Relayer; Solana only, no EIP-7702. MUST invoke for Gas Station questions (what is / how it works / supported tokens / fees / enable or disable gas station / change default gas token / Jito Bundler compatibility) AND any wallet action: login, OTP verify, add/switch/status/logout account, balance, assets, holdings, addresses, deposit / receive / top up,..." Translation: Keep technical terms like "OKX Agentic Wallet", "Gas Station
apiweb-scrapingdevelopment
okx-agent-chat
okx
Routing stub — any a2a-agent-chat envelope / agent-task system message is handled by `okx-agent-task`. For missing or uninitialized OKX A2A communication runtime/plugin, read `skills/okx-agent-chat/ensure-okx-a2a-communication-ready.md`.
developmentapicommunication
okx-agent-task
okx
DEVE ATIVAR em envelopes recebidos: (1) {agentId, message:{source:"system", event, jobId, ...}} — evento de sistema; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — chat de tarefa agente-para-agente (campos no nível superior; sender.role = CONTRAPARTE, não você); (3) literal "Read okx-agent-task/SKILL.md" no envelope. TAMBÉM ativar para palavras-chave: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-agent-payments-protocol
okx
We need to translate the given text from English to Brazilian Portuguese. The text is inside <text> tags. We must preserve the name "okx-agent-payments-protocol" but it's not in the source text, so we don't include it. We must not add any labels or extra commentary. Just translate the text. The text: "Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, a paymentId or a2a_ link, creating / checking a payment link, A2MCP / an A2MCP endpoint, or sending a request to / calling an Agent's endpoint with a concrete endpoint..." We need to translate terms like "agent", "hits", "HTTP
okx-security
okx
Use esta skill para varredura de segurança: verificar segurança de transação, esta transação é segura, verificação pré-execução, varredura de segurança, varredura de risco de token, detecção de honeypot, detecção de phishing em DApp/URL, segurança de assinatura de mensagem, detecção de transação maliciosa, verificações de segurança de aprovação, gerenciamento de aprovação de token. Gatilhos: 'este token é seguro', 'verificar segurança do token', 'verificação de honeypot', 'escanear esta tx', 'escanear esta tx de swap', 'verificação de risco de tx', 'esta URL é golpe', 'verificar se este dapp é seguro', 'phishing...
okx-task-watch
okx
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via `okx-a2a user watch` (also drains backlog of past/missed/unread events on entry) plus un-replied decision_request lister via `okx-a2a user outdated-list`. Not for wallet / gas / task-list / status queries.
developmentapiproductivity