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。按含义匹配....

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.

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は、サードパーティのRelayerを介したSolana上のOKXのステーブルコインガス機能であり、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 Japanese. The text describes an agent identity system on XLayer using ERC-8004. It includes roles and usage examples. We must preserve the name "okx-agent-identity" but it's not in the text, so we ignore. Translate the entire text inside <text> to Japanese, keeping technical terms like ERC-8004, XLayer, agent, ASP, etc. Also keep the Chinese terms as they are? The instruction says preserve product names, protocol names, URLs, numbers, technical terms. The Chinese terms like 用户, 买家, etc. are part of the roles and usage examples. Should we translate them to Japanese? The source text has both English and Chinese. The target language is Japanese, so we should translate the English and Chinese into Japanese. But the Chinese terms are listed as alternatives for roles. For consistency, we should translate them to Japanese equivalents. However, the instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." The Chinese words like
developmentapi
okx-agent-payments-protocol
okx
We need to translate the given English text into Japanese, preserving the specified name "okx-agent-payments-protocol" but not including it unless it appears in the source text. The source text does not contain that name, so we just translate the text inside <text>. The text is a description of when to use the agent skill. We must preserve product names, protocol names, URLs, numbers, technical terms. So terms like HTTP 402, x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, paymentId, a2a_ link, creating / checking a payment link, A2MCP, A2MCP endpoint, Agent's endpoint, concrete endpoint should be kept as is or with appropriate Japanese punctuation. Also note the ellipsis at the end. We need to produce
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-guide
okx
OKX.AI(Agent経済システム)の紹介とオンボーディングエントリ。ユーザーが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
ユーザーをOKX.AIカスタマーサポート/ヘルプセンターに案内します。ユーザーがサポートへの連絡、人間との会話、苦情の申し立て、フィードバックの提供、システムエラーやバグの報告、FAQ/ヘルプドキュメントの検索を希望する場合に使用します。トリガー: 「サポートに連絡」「人間と話す」「カスタマーサービス」「苦情を申し立てる」「フィードバックを送る」「ヘルプセンター」「FAQ」「ユーザーガイド」「システムエラー」「システムバグ」「何かが壊れている」「ヘルプドキュメントを探す」「OKX AIサポート」「OnchainOSサポート」「人間のエージェント」。
communicationresearchdocument
okx-audit-log
okx
ユーザーが監査ログのエクスポート、監査ログの場所の確認、コマンド履歴の表示、ログのエクスポート、ログの確認、ログのパス、操作記録、呼び出し記録、コマンド履歴を要求した場合にこのスキルを使用します。ウォレット残高、トークン検索、スワップ、その他のオンチェーン操作には使用しないでください。代わりに対応するスキルを使用してください。
securitydata-analysisapi