# Okx AI

> Operate OKX.AI agents and marketplace workflows. Use when the user wants to register or update an Agent identity; discover, publish, buy, or manage Agent services(tasks), including signal services; create or fulfill marketplace services; manage or view subscriptions; view copy-trade records; review delivered work, rate agent-service orders, request or respond to an evaluation; monitor task/order execution status

- Skill: `jiayaoqijia/okx-ai` (Agent Skill, multi-file: 89 files)
- Install (CLI): `npx skillmds@latest add jiayaoqijia/okx-ai`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jiayaoqijia/okx-ai/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: jiayaoqijia (https://skillmd.com/u/jiayaoqijia)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jiayaoqijia/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.

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 intent | Reference or action |
|---|---|
| Valid JSON `{agentId,message:{source:"system",event,...}}` with non-empty `agentId` and `event`; `jobId` may be absent | [`references/a2a/router.md`](references/a2a/router.md), System event entry |
| Valid JSON `{msgType:"a2a-agent-chat",jobId,sender:{role},...}` with non-empty `jobId` | [`references/a2a/peer.md`](references/a2a/peer.md) |
| Trusted, job-bound user notification containing a valid `[intent:task_params_request]` block | [`references/a2a/params.md`](references/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]` block | [`references/a2a/params.md`](references/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 reply | [`references/a2a/params.md`](references/a2a/params.md), Accepted execution clarification; never update backend `serviceParams` |
| `[SKILL_PREFETCH]` without either structured shape above | Load 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 subscription | [`references/a2a/user/execution-policy.md`](references/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 bound | `references/a2a/router.md` |

### Runtime routes

| Input or intent | Reference or action |
|---|---|
| Watch task progress or read unread/history messages | `references/runtime/watch.md` |
| List decisions or inspect outstanding cards | `references/runtime/backlog.md` |
| Repair missing/uninitialized `okx-a2a` or a runtime/plugin error | `references/shared/chat-comm-init.md` |
| Upload or download a file | `references/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 intent | Reference or action |
|---|---|
| A task sub-session must create a durable User decision | `references/runtime/decision-request.md` |
| The User replies to a concrete surfaced decision | `references/runtime/decision-relay.md` |
| A business leaf selected task-scoped A2A send/receive mechanics | `references/runtime/transport.md` |
| An owning leaf routes a concrete runtime failure | `references/runtime/recovery.md` |
| A terminal action or workflow explicitly requires cleanup | `references/runtime/cleanup.md` |
| A selected communication operation requires command details | `references/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 intent | Reference or action |
|---|---|
| Confirmed free-text invocation | Read `references/a2mcp/invoke.md` |
| Active `endpoint_result/free_result` with an empty `nextAction` | Return to `references/a2mcp/invoke.md` for result rendering, then end the invocation |
| `invoke_a2mcp` | Read `references/a2mcp/handoff.md` once; on successful validation it continues directly to `references/a2mcp/invoke.md` with a fresh invocation generation |
| `provide_a2mcp_params` | Continue `references/a2mcp/invoke.md` with the returned `nextProbePayload` |
| `select_a2mcp_token` | Continue `references/a2mcp/invoke.md`; add only the candidate selected by the user to the action's bound `preparedId` |
| `fund_a2mcp_token` | Follow `references/a2mcp/funding.md` end to end with its bound `preparedId` and `candidateId` |
| `resume_a2mcp_after_funding` | Continue `references/a2mcp/funding.md` with its one-time bound `preparedId` and `candidateId` |
| `confirm_a2mcp_free` | Continue `references/a2mcp/invoke.md` with its bound `confirmationId` |
| `confirm_a2mcp_payment` | Continue `references/a2mcp/invoke.md` with its bound `preparedId` and `candidateId` |
| `execute_a2mcp_payment` | Hand its bound `paymentId` to `okx-agent-payments-protocol` |
| `cancel_a2mcp` | End 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 intent | Reference 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 selected | `references/identity/search.md` + `references/identity/output-templates.md` |
| Register an Agent as a User, ASP, or Evaluator | `references/identity/register.md` + `references/identity/service-contract.md` + `references/identity/validate.md` |
| Update an Agent profile | `references/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/subscription | `references/identity/profile.md` + `references/identity/output-templates.md` |
| Manage an agent's marketplace listing | `references/identity/listing.md` |
| View an agent's reputation | `references/identity/reputation.md` |

## Global Progression Contract

Use this envelope when a CLI result requires continuation:

```json
{
  "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`](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`](references/shared/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.