okx-ai

작성자: okx

ERC-8004 에이전트 신원: 에이전트 등록/업데이트/상장/하장/검색, register/update/activate/deactivate/search — User/ASP/Evaluator(구매자/판매자/중재자); 내 에이전트/ASP, X를 하는 ASP/에이전트 찾기, 어떤 서비스가 있는지/endpoint 입력 방법/평판 확인/아바타 업로드. + Task Marketplace: 게시/작업 생성/수주/협상/검수/deliver/dispute/중재/거절/stake/unstake/공급자 변경/예산 변경/판매자 수정/예산 수정/draft/초안/내 작업/my tasks/현재 진행 중인 작업/종료/작업 취소/결정 목록/decision list/서비스 제공자 지정/마켓플레이스 탐색. + task watch: 작업 진행 상황 모니터링/과거 메시지/읽지 않은 메시지/미결정/outstanding decisions. + okx-a2a 누락/초기화 안 됨. 의미에 따라 매칭....

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.

okx의 다른 스킬

okx-agent-identity
okx
We need to translate the given text into Korean while preserving the name "okx-agent-identity" (but it's not in the text, so ignore). The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. Just translate the content inside <text> to Korean. The text includes technical terms like ERC-8004, XLayer, agent, ASP, evaluator, etc. Also includes Chinese characters and English terms. We need to translate the English and Chinese parts appropriately into Korean, but preserve the technical terms and numbers. Let's break it down: "ERC-8004 on-chain Agent identity on XLayer: register / create / update / activate / deactivate / search agents; view ratings; list agent services; set avatar." Translate: "XLayer에서의 ERC-8004 온체인 에이전트 신원: 에이전트 등록/생성/업데이트/활성화/비활성화/검색; 평점 보기; 에이전트 서
developmentapi
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-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-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:"a2
developmentapicommunication
okx-agent-payments-protocol
okx
We need to translate the given text from English to Korean. The text describes when to use an agent skill related to HTTP 402 and various payment-related terms. We must preserve the name "okx-agent-payments-protocol" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra commentary, labels, etc. 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..." Translate carefully. Keep
okx-security
okx
이 스킬을 보안 스캔에 사용하세요: 거래 안전성 확인, 이 거래가 안전한지 확인, 사전 실행 점검, 보안 스캔, 토큰 리스크 스캔, 허니팟 탐지, DApp/URL 피싱 탐지, 메시지 서명 안전성, 악성 거래 탐지, 승인 안전성 점검, 토큰 승인 관리. 트리거: '이 토큰 안전한가요', '토큰 보안 확인', '허니팟 확인', '이 tx 스캔', '이 스왑 tx 스캔', 'tx 리스크 확인', '이 URL 사기인가요', '이 dapp 안전한지 확인', '피싱...
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