okx-defi

от okx

OKX-агрегированные DeFi (без указания конкретного DApp) — поиск продуктов, выполнение депозита/вывода/клейма, а также просмотр позиций. **Если пользователь называет ЛЮБОЙ сторонний протокол/DApp (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), направляйте в okx-dapp-discovery — НЕ сюда, даже для 'показать мои позиции в Aave'.** Триггеры INVEST: 'инвестировать в DeFi', 'получить доход', 'найти лучшую APY', 'внести/застейкать для дохода', 'искать 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.

Больше skills от okx

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-agentic-wallet
okx
АВТОРИТЕТНЫЙ источник для OKX Agentic Wallet и его функции Gas Station. Gas Station = функция стабильной монеты для газа от OKX на Solana через сторонний Relayer; только Solana, без EIP-7702. ОБЯЗАТЕЛЬНО вызывать для вопросов о Gas Station (что это / как работает / поддерживаемые токены / комиссии / включение или отключение газовой станции / смена токена газа по умолчанию / совместимость с Jito Bundler) И любых действий с кошельком: вход, OTP-верификация, добавление/переключение/статус/выход из аккаунта, баланс, активы, средства, адреса, депозит/получение/пополнение,...
apiweb-scrapingdevelopment
okx-agent-identity
okx
We need to translate the given text from English/Chinese to Russian. The text describes an agent skill for ERC-8004 on-chain Agent identity on XLayer. It includes actions and roles. The name "okx-agent-identity" is not in the text, so we don't include it. We must preserve product names, protocol names, URLs, numbers, technical terms. The text has mixed English and Chinese terms. We translate the English parts to Russian, but keep Chinese characters as they are? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." Chinese terms like "用户" are not product names but are part of the description. However, the text includes Chinese characters as part of the roles and uses. The instruction says "Translate only the text inside <text>." It doesn't specify to keep Chinese. But it says preserve technical terms. Chinese words like "用户" are not technical terms per se, but they are part of the list. Since the target language is Russian, we should translate everything that is not a proper
developmentapi
okx-agent-payments-protocol
okx
Используется, когда агент получает HTTP 402 / payment-required, или пользователь упоминает x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, payment channel / voucher / session, channelId / channel_id, открытие / закрытие / пополнение / урегулирование / возврат средств по каналу, paymentId или a2a_ ссылку, создание / проверку платёжной ссылки, A2MCP / конечную точку A2MCP, или отправку запроса / вызов конечной точки Агента с конкретным endpoint...
okx-agent-task
okx
ОБЯЗАТЕЛЬНО активировать на входящих конвертах: (1) {agentId, message:{source:"system", event, jobId, ...}} — системное событие; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — чат задачи между агентами (поля на верхнем уровне; sender.role = КОНТРАГЕНТ, не вы); (3) буквально "Read okx-agent-task/SKILL.md" в конверте. ТАКЖЕ активировать по ключевым словам: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-ai
okx
ERC-8004 Agent identity: 注册/更新/上架/下架/搜索agent, register/update/activate/deactivate/search — User/ASP/Evaluator(买家/卖家/仲裁者); 我的agent/ASP, 找做X的ASP/agent有什么服务/endpoint怎么填/查口碑/传头像. + Task Marketplace: 发布/创建任务/接单/协商/验收/deliver/dispute/仲裁/拒绝/stake/unstake/change provider/change budget/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + okx-a2a missing/uninitialized. Match by meaning....
apiweb-scrapingresearch
okx-ai-guide
okx
OKX.AI (экономическая система Агентов) — введение и точка входа. Используйте, когда пользователь спрашивает, что такое OKX.AI, что он может делать, как его использовать или начать работу, хочет получить учебник / краткое руководство / помощь по OKX.AI, или вводит название продукта в любом варианте написания / пробелов / регистра / опечаток (OKXAI, okx ai, okx-ai, строчные okx.ai, ошибочно набранные по-китайски типа 啥是okxai) — например, what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, а также любые перефразирования на любом языке. Определяет платформу выполнения, представляет...
researchapidocument
okx-ai-support
okx
We need to translate the given text from English to Russian. The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-ai-support" is not in the text, so we don't include it. The text is a description of an agent skill. We must translate only the text inside <text>. No extra commentary, no labels. The translation should be natural Russian. The text: "Route users to OKX.AI customer support / Help Center. Use when the user wants to contact support, talk to a human, file a complaint, give feedback, report a system error or bug, or find the FAQ / help docs. Triggers: 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback', 'help center', 'FAQ', 'user guide', 'system error', 'system bug', 'something is broken', 'find help docs', 'OKX AI support', 'OnchainOS support', 'human agent'." We need to translate the entire block. Pres
communicationresearchdocument