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

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

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-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-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
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-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-security
okx
इस कौशल का उपयोग सुरक्षा स्कैनिंग के लिए करें: लेन-देन सुरक्षा जांचें, क्या यह लेन-देन सुरक्षित है, निष्पादन-पूर्व जांच, सुरक्षा स्कैन, टोकन जोखिम स्कैनिंग, हनीपॉट पहचान, DApp/URL फ़िशिंग पहचान, संदेश हस्ताक्षर सुरक्षा, दुर्भावनापूर्ण लेन-देन पहचान, अनुमोदन सुरक्षा जांच, टोकन अनुमोदन प्रबंधन। ट्रिगर: 'क्या यह टोकन सुरक्षित है', 'टोकन सुरक्षा जांचें', 'हनीपॉट जांच', 'इस
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