okx-ai

bởi 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. 按含义匹配....

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

OKX.AI

Module Description

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.

Render Rules

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.

State Routing

Route by envelope shape before free text, and select exactly one row across all 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.

Structured entry

Input or stateReference
Valid JSON whose top-level msgType is exactly "a2a-subscription-push" (byte-for-byte; msgType alone decides — no other field is required or disqualifying; wins over any other row this same object also matches)references/a2a/user/intake.md, new-version subscription-push intake
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

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 stateReference
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 continuation

Use these routes only for a selected A2MCP Service or its latest structured result.

Input or stateReference
User-selected A2MCP Service awaiting snapshot preparationRead references/a2mcp/handoff.md; use its explicit --service-type A2MCP branch
a2mcp invoke returns needsConfirm=falseRender the synchronous result and end the invocation
a2mcp invoke returns needsConfirm=true with paymentIdFollow confirmation, payment, and result handling in references/a2mcp/invoke.md

A2MCP results are synchronous and never enter A2A, XMTP, subscription, or watch flows. Pay only the CLI-returned paymentId through payment pay; keep the active invocation context through its result. Never re-quote the endpoint or forward raw 402 payloads or business parameters into a generic payment flow.

Intent Routing

For free text, prefer exact Runtime or Identity matches over broad A2A.

Task messaging & history

Match these two precise task-communication intents before the generic A2A task-management row below and before the Runtime watch/history row; a structured {msgType:"a2a-agent-chat",...} envelope still enters references/a2a/peer.md through Structured entry unchanged.

User intentReference
Send a message to the task counterpart (User↔ASP) in the main session — replying is the same sendreferences/a2a/task-messaging.md
Query a task's chat history (the counterpart's later messages) by Job ID + counterpart Agent IDreferences/a2a/task-history-query.md

A2A entry

User intentReference
Review or update the saved Guide Consent for an existing subscriptionreferences/a2a/user/execution-policy.md, Updating a saved Guide Consent
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

User intentReference
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

A2MCP invocation

User intentReference
Invoke a confirmed A2MCP ServiceRead references/a2mcp/invoke.md

Identity routes

User intentReference
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 Agent identities, 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

Action Routing

A2MCP continuation

Action IDReference
invoke_a2mcpRead references/a2mcp/handoff.md, then references/a2mcp/invoke.md

CLI Reference Access

  1. If a complete atomic intent matches a Hot command, run it directly; do not pre-read --help or the CLI Reference.
  2. Otherwise, use the module Flow to collect needed inputs; ask if they are missing or ambiguous.
  3. Read the module's CLI Reference to choose the exact command. It is authoritative for syntax, defaults, and validation.
  4. Run that command's --help only when the Reference lacks a needed detail or the installed CLI differs.

CLI Result 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.
  • reason: machine-readable reason.
  • 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 explicit MCP preparation result enters references/a2mcp/handoff.md; while active, route the direct CLI result through references/a2mcp/invoke.md. Clear the context after a free result, payment result, cancellation, or error, 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: apply the CLI Result Contract above, 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.

Thêm skills từ 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
Nguồn CHÍNH THỨC về OKX Agentic Wallet và tính năng Gas Station của nó. Gas Station = tính năng stablecoin-gas của OKX trên Solana thông qua Relayer bên thứ ba; chỉ Solana, không có EIP-7702. PHẢI gọi cho các câu hỏi về Gas Station (là gì / cách hoạt động / token hỗ trợ / phí / bật hoặc tắt gas station / thay đổi token gas mặc định / tương thích Jito Bundler) VÀ bất kỳ hành động ví nào: đăng nhập, xác minh OTP, thêm/chuyển đổi/trạng thái/đăng xuất tài khoản, số dư, tài sản, nắm giữ, địa chỉ, nạp/nhận/nạp tiền,...
apiweb-scrapingdevelopment
okx-agent-identity
okx
ERC-8004 trên chuỗi định danh Agent trên XLayer: đăng ký / tạo / cập nhật / kích hoạt / hủy kích hoạt / tìm kiếm agent; xem đánh giá; liệt kê dịch vụ agent; đặt hình đại diện. Vai trò: user (User / User Agent / Buyer / Client / 用户 / 买家 / 买方), asp (ASP / Provider / Provider Agent / Seller / Merchant / 提供者 / 商家 / 服务提供商 / 卖家 / 卖方), evaluator (Evaluator / Evaluator Agent / 仲裁者 / 评估者). Sử dụng cho: 注册agent / 注册ASP / 注册User / 注册用户 / 注册买家 / 注册卖家 / 注册服务提供商 / 注册仲裁者 / 创建用户 / 创建买家 / 创建卖家 / 我的agent / 我的ASP / 改agent / 更新agent...
developmentapi
okx-agent-payments-protocol
okx
We need to translate the given text from English to Vietnamese. The text is inside <text> tags. We must preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-agent-payments-protocol" is not in the source text, so we don't include it. We translate only 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 this into Vietnamese, keeping technical terms like HTTP
okx-agent-task
okx
PHẢI KÍCH HOẠT trên các thư đến: (1) {agentId, message:{source:"system", event, jobId, ...}} — sự kiện hệ thống; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — chat tác vụ giữa các tác nhân (các trường ở cấp cao nhất; sender.role = ĐỐI TÁC, không phải bạn); (3) chuỗi ký tự "Read okx-agent-task/SKILL.md" trong thư. CŨNG kích hoạt cho các từ khóa: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-ai-guide
okx
Giới thiệu & hướng dẫn bắt đầu về OKX.AI (hệ sinh thái Agent). Sử dụng khi người dùng hỏi OKX.AI là gì, có thể làm gì, cách sử dụng hoặc bắt đầu, muốn hướng dẫn / khởi động nhanh / trợ giúp về OKX.AI, hoặc nhập tên sản phẩm dưới bất kỳ biến thể chính tả / khoảng cách / viết hoa / lỗi gõ nào (OKXAI, okx ai, okx-ai, chữ thường okx.ai, gõ sai tiếng Trung như 啥是okxai) — ví dụ: what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, và bất kỳ diễn giải nào bằng bất kỳ
researchapidocument
okx-ai-support
okx
We need to translate the given text from English to Vietnamese, preserving the name "okx-ai-support" if it appears, but it does not appear in the text. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. Just output the translation. 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'." Translate to Vietnamese. Note: "OKX.AI" should be kept as is. "OnchainOS" also. The triggers are phrases in quotes,
communicationresearchdocument
okx-audit-log
okx
Sử dụng kỹ năng này khi người dùng yêu cầu xuất nhật ký kiểm toán, tìm vị trí nhật ký kiểm toán, xem lịch sử lệnh, 导出日志, 查看日志, 日志路径, 操作记录, 调用记录, 命令历史. KHÔNG sử dụng cho số dư ví, tìm kiếm token, swap, hoặc bất kỳ thao tác on-chain nào khác — hãy sử dụng kỹ năng tương ứng.
securitydata-analysisapi