okx-ai

द्वारा okx

ERC-8004 Agent पहचान: agent पंजीकृत/अद्यतन/सूचीबद्ध/हटाना/खोजना, register/update/activate/deactivate/search — User/ASP/Evaluator(खरीदार/विक्रेता/मध्यस्थ); मेरे agent/ASP, X करने वाले ASP/agent खोजें, क्या सेवाएँ हैं/endpoint कैसे भरें/प्रतिष्ठा देखें/अवतार अपलोड करें. + Task Marketplace: प्रकाशित करें/कार्य बनाएँ/कार्य लें/बातचीत करें/स्वीकृति/deliver/dispute/मध्यस्थता/अस्वीकार/stake/unstake/प्रदाता बदलें/बजट बदलें/विक्रेता बदलें/बजट संशोधित करें/draft/ड्राफ़्ट/मेरे कार्य/my tasks/what am I working on/बंद करें/कार्य रद्द करें/निर्णय सूची/decision list/निर्दिष्ट सेवा प्रदाता/browse marketplace. + task watch: कार्य प्रगति सुनें/इतिहास संदेश/अपठित संदेश/अनिर्णीत/outstanding decisions. + okx-a2a अनुपलब्ध/अप्रारंभित. अर्थ से मिलान करें....

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 की और Skills

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 to Hindi, preserving the name "okx-agent-identity" 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 translate the text inside <text> to Hindi. The text includes technical terms like ERC-8004, XLayer, agent, ASP, evaluator, etc. We should keep those as is or transliterate if needed. Also includes Chinese characters, which should be preserved as they are? The instruction says preserve product names, protocol names, URLs, numbers, technical terms. Chinese characters are part of the text, likely as alternative terms. We should keep them as is. So we translate the English parts to Hindi, but keep the Chinese characters unchanged. Let's break down the text: "ERC-8004 on-chain Agent identity on XLayer: register / create / update / activate / deactivate / search agents; view ratings; list agent services; set avatar. Roles: user (User
developmentapi
okx-agent-payments-protocol
okx
जब कोई एजेंट HTTP 402 / payment-required का सामना करता है, या उपयोगकर्ता x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, मीटर्ड बिलिंग, भुगतान चैनल / वाउचर / सत्र, channelId / channel_id, चैनल खोलना / बंद करना / टॉप अप करना / निपटाना / रिफंड करना, paymentId या a2a_ लिंक, भुगतान लिंक बनाना / जांचना, A2MCP / एक A2MCP एंडपॉइंट, या किसी ठोस एंडपॉइंट के साथ एजेंट के एंड
okx-agent-task
okx
We need to translate the given text from English to Hindi. The text is a description of conditions for activating an agent skill. It mentions specific patterns and keywords. We must preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-agent-task" appears in the text, so we preserve it. Also preserve terms like "agentId", "message", "source", "event", "jobId", "msgType", "a2a-agent-chat", "sender", "role", "COUNTERPARTY", "SKILL.md", and the Chinese keywords. The translation should be in Hindi script. We need to translate the entire text inside <text> tags. No extra labels. Just the translation. Let's break it down: "MUST ACTIVATE on inbound envelopes: (1) {agentId, message:{source:"system", event, jobId, ...}} — system event; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — agent-to-agent task chat (fields
developmentapicommunication
okx-ai-guide
okx
We need to translate the given text from English to Hindi. The text is a description of an agent skill for OKX.AI. We must preserve the product name "okx-ai-guide" as per instruction, but it's not in the text. The text includes "OKX.AI" and various spellings. We need to translate the entire content inside <text> to Hindi, keeping product names, URLs, numbers, technical terms unchanged. Also preserve the examples like "what is OKX.AI" etc. but translate the surrounding words. The instruction says "Do not include the name unless it appears in the source text." The name "okx-ai-guide" does not appear in the source text, so we don't include it. We just translate the text. Let's translate paragraph by paragraph. Source: "OKX.AI (the Agent economic system) intro & onboarding entry. Use whenever the user asks what OKX.AI is, what it can do, how to use or get started with it, wants an OKX.AI tutorial
researchapidocument
okx-ai-support
okx
उपयोगकर्ताओं को OKX.AI ग्राहक सहायता / सहायता केंद्र तक पहुँचाएँ। इसका उपयोग तब करें जब उपयोगकर्ता सहायता से संपर्क करना चाहता हो, किसी मानव से बात करना चाहता हो, शिकायत दर्ज कराना चाहता हो, प्रतिक्रिया देना चाहता हो, सिस्टम त्रुटि या बग की रिपोर्ट करना चाहता हो, या FAQ / सहायता दस्तावेज़ ढूँढना चाहता हो। ट्रिगर: 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback', 'help center', 'FAQ', 'user guide', 'system error', 'system
communicationresearchdocument
okx-audit-log
okx
इस कौशल का उपयोग तब करें जब उपयोगकर्ता ऑडिट लॉग निर्यात करने, ऑडिट लॉग स्थान खोजने, कमांड इतिहास देखने, 导出日志, 查看日志, 日志路径, 操作记录, 调用记录, 命令历史 के लिए कहे। वॉलेट बैलेंस, टोकन खोज, स्वैप या किसी अन्य ऑन-चेन ऑपरेशन के लिए इसका उपयोग न करें — इसके बजाय संबंधित कौशल का उपयोग करें।
securitydata-analysisapi