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....

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

OKX.AI

Reference priority

Use the routing tables below as the only top-level intent map. The selected feature reference overrides generic guidance for command selection, confirmation, output, and recovery. Structured inbound envelopes take precedence over free-text routing.

Response language

Keep the flow in the user's initial language. Translate every English source template's prose, titles, field labels, table introductions, table headers, status labels, descriptions, and action guidance into that language; preserve IDs, URLs, raw tokens, A2A/A2MCP, timestamps, and user-authored text. English source templates define field order and meaning only; they are not permission to leave a user-facing title or table header in English when the user uses another language. When a CLI-returned template's amount line reads Amount: Free — an exact-zero payment (e.g. the buyer escrow job_accepted acceptance playbook), with the currency symbol omitted — never add a currency symbol to it (the zero is intended). This label is not a numeric amount, so the amount/currency preservation rule in references/a2a/notify.md does not apply to it.

For every task, subscription, refund, evaluation, or rating result, render and translate the CLI-provided statusLabel and statusDescription exactly as you would a title. Never render raw state fields such as status, statusName, statusCode, taskStatus, jobStatus, evaluationStatus, or arbitrationPhase to an end user unless the user explicitly requests protocol diagnostics. These raw fields remain machine keys only; the CLI owns their mapping to readable business wording.

Preflight

Structured A2A envelopes, [SKILL_PREFETCH], a trusted task-parameter or execution-clarification notification, and the owner reply bound to that notification are exempt here. Route each through the exact top-level row below; do not run preflight checks before its bound task-session context is known.

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

Top-level routing

Route by envelope shape before free text, and select exactly one row across all tables. For free text, prefer exact Runtime or Identity matches over broad A2A. Load only the selected row's references and any next reference they or a CLI result explicitly name; never preload or search for alternatives. If a linked file is missing, report an incomplete installation and stop.

Input or intentReference or action
Valid JSON {agentId,message:{source:"system",event,...}} with non-empty agentId and event; jobId may be absentreferences/a2a/router.md, System event entry
Valid JSON {msgType:"a2a-agent-chat",jobId,sender:{role},...} with non-empty jobIdreferences/a2a/peer.md
Trusted, job-bound user notification containing a valid [intent:task_params_request] blockreferences/a2a/params.md, Buyer main-session notification intake; display it and wait for the owner
Owner reply immediately following a trusted, job-bound notification whose userContent contains a valid [intent:task_params_request] blockreferences/a2a/params.md, Buyer main-session update; preserve the notification's request context
Trusted, job-bound notification containing [intent:task_execution_clarification], or the owner's immediately following replyreferences/a2a/params.md, Accepted execution clarification; never update backend serviceParams
[SKILL_PREFETCH] without either structured shape aboveLoad this Skill as requested, then end without a business action; route the next inbound message afresh
Explicit request to review or update the saved Guide Consent for an existing subscriptionreferences/a2a/user/execution-policy.md, Updating a saved Guide Consent
A fresh free-text request to view, or manage User/ASP tasks and subscriptions; respond to assignments; deliver or review work; handle refunds, evaluations, ratings, or evaluator work, when no exact leaf is already boundreferences/a2a/router.md

Runtime routes

Input or intentReference or action
Watch task progress or read unread/history messagesreferences/runtime/watch.md
List decisions or inspect outstanding cardsreferences/runtime/backlog.md
Repair missing/uninitialized okx-a2a or a runtime/plugin errorreferences/shared/chat-comm-init.md
Upload or download a filereferences/runtime/attachment.md

Bound Runtime continuation routes

Bound Runtime continuations are not free-text intents. Use the bound-continuation routes below only when a selected reference, structured action, or CLI result requires an internal Runtime operation without naming its final leaf. Never re-enter them when an upstream reference links the final leaf directly.

Read exactly one selected reference:

Input or intentReference or action
A task sub-session must create a durable User decisionreferences/runtime/decision-request.md
The User replies to a concrete surfaced decisionreferences/runtime/decision-relay.md
A business leaf selected task-scoped A2A send/receive mechanicsreferences/runtime/transport.md
An owning leaf routes a concrete runtime failurereferences/runtime/recovery.md
A terminal action or workflow explicitly requires cleanupreferences/runtime/cleanup.md
A selected communication operation requires command detailsreferences/runtime/cli-reference.md

Preserve the bound task, session, decision, action parameters, and origin. Never infer an internal operation from prose or preload sibling files. A missing mapping is a coverage failure—report it and stop.

A2MCP routes

Use these routes to invoke a confirmed A2MCP service or inspect its synchronous result.

For every active invocation, route only from the latest CLI nextAction; never infer an action or opaque ID from prose.

Input or intentReference or action
Confirmed free-text invocationRead references/a2mcp/invoke.md
Active endpoint_result/free_result with an empty nextActionReturn to references/a2mcp/invoke.md for result rendering, then end the invocation
invoke_a2mcpRead references/a2mcp/handoff.md once; on successful validation it continues directly to references/a2mcp/invoke.md with a fresh invocation generation
provide_a2mcp_paramsContinue references/a2mcp/invoke.md with the returned nextProbePayload
select_a2mcp_tokenContinue references/a2mcp/invoke.md; add only the candidate selected by the user to the action's bound preparedId
fund_a2mcp_tokenFollow references/a2mcp/funding.md end to end with its bound preparedId and candidateId
resume_a2mcp_after_fundingContinue references/a2mcp/funding.md with its one-time bound preparedId and candidateId
confirm_a2mcp_freeContinue references/a2mcp/invoke.md with its bound confirmationId
confirm_a2mcp_paymentContinue references/a2mcp/invoke.md with its bound preparedId and candidateId
execute_a2mcp_paymentHand its bound paymentId to okx-agent-payments-protocol
cancel_a2mcpEnd the invocation without another CLI call

Read references/a2mcp/recovery.md only for phase=invocation_recovery or when references/a2mcp/invoke.md routes an error there. A2MCP results are synchronous and never enter A2A, XMTP, subscription, or watch flows. Keep raw HTTP 402 responses in references/a2mcp/invoke.md; only execute_a2mcp_payment.params.paymentId enters the Payment Protocol.

Identity routes

Input or intentReference or action
Discover or recommend Agents/services, or use one by service name, Service ID, or Agent ID to start a task/subscription when no Service is selectedreferences/identity/search.md + references/identity/output-templates.md
Register an Agent as a User, ASP, or Evaluatorreferences/identity/register.md + references/identity/service-contract.md + references/identity/validate.md
Update an Agent profilereferences/identity/update.md + references/identity/service-contract.md + references/identity/validate.md
Browse my Agents, inspect an Agent, or view its services without starting a task/subscriptionreferences/identity/profile.md + references/identity/output-templates.md
Manage an agent's marketplace listingreferences/identity/listing.md
View an agent's reputationreferences/identity/reputation.md

Global Progression Contract

Use this envelope when a CLI result requires continuation:

{
  "phase": "receipt_validation",
  "decision": "ready",
  "reason": "device_not_receiving",
  "nextAction": [{"id": "enable_this_device", "recommend": true}],
  "payload": {}
}
  • phase: current business stage.
  • decision: ready, blocked, or requires_user_input.
  • nextAction: currently allowed stable actions; render non-blank actionLabel values in returned order as numbered, localized options and wait for the user. Do not expose Action IDs, recommend, or params.
  • payload: current facts.

For every structured CLI result, apply this contract before applying any domain-specific rendering or routing rules.

invoke_a2mcp starts an active A2MCP invocation. Its confirmed a2a/user/create-prepare.md result enters references/a2mcp/handoff.md; while active, route every subsequent result through the A2MCP routes above, including results with an empty nextAction. Outside that context, use those routes only when the latest nextAction[].id is A2MCP-namespaced; never classify from prose. Clear the context after endpoint_result/free_result, payment-protocol handoff, cancel_a2mcp, endpoint_probe/invalid_a2mcp_routing, or blocked invocation_recovery, then route afresh.

For a System envelope, a2a/router.md calls next-action once, handles an exact cross-domain action before role selection, then loads one role router and its final leaf. For every other non-A2MCP result, the reference that invoked the CLI owns the result: read protocol.md, then follow its exact result matrix or the exact leaf named by the CLI. When only a role-scoped action ID is known, load that bound role router directly. Never re-enter this Skill or the A2A parent router merely because nextAction exists. Never infer an action from prose or preload possible later leaves.

Больше skills от okx

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-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-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-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
ОБЯЗАТЕЛЬНО активировать на входящих конвертах: (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-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-security
okx
We need to translate the given text from English to Russian. The text describes a skill for security scanning. We must preserve the name "okx-security" but it's not in the text, so we don't include it. We translate the entire text inside <text>. No extra commentary, no labels. Just the translation. The text: "Use this skill for security scanning: check transaction safety, is this transaction safe, pre-execution check, security scan, token risk scanning, honeypot detection, DApp/URL phishing detection, message signature safety, malicious transaction detection, approval safety checks, token approval management. Triggers: 'is this token safe', 'check token security', 'honeypot check', 'scan this tx', 'scan this swap tx', 'tx risk check', 'is this URL a scam', 'check if this dapp is safe', 'phishing..." We need to translate accurately. Terms like "honeypot", "DApp", "URL", "tx" (transaction), "swap", "phishing" are technical and
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