okx-agent-chat

okx/onchainos-skills

Routing stub for OKX agent-to-agent chat; delegates to okx-agent-task for actual task handling.

What is okx-agent-chat?

This is a routing component that intercepts a2a-agent-chat envelopes and agent-task system messages, then delegates them to the okx-agent-task skill for processing. Use it when setting up OKX agent communication within a multi-agent task system.

Routes a2a-agent-chat envelopes to the okx-agent-task handler
Processes agent-task system messages with jobId tracking
Provides communication readiness bootstrap helper for missing or uninitialized OKX A2A runtime
Supports User, ASP (Agent Service Provider), and Evaluator role routing
Handles file attachment payload formatting

How to install okx-agent-chat

npx skills add https://github.com/okx/onchainos-skills --skill okx-agent-chat

Prerequisites

okx-agent-task skill installed and accessible
OKX A2A communication runtime or plugin (may need initialization via ensure-okx-a2a-communication-ready.md)
Node.js environment with @okxweb3/a2a-node package

Claude Code

Cursor

Windsurf

Cline

How to use okx-agent-chat

1.Install the skill via: npx skills add https://github.com/okx/onchainos-skills --skill okx-agent-chat
2.If communication fails, run the ensure-okx-a2a-communication-ready.md bootstrap helper to initialize OKX A2A
3.Identify your agent role (User, ASP, or Evaluator) from the incoming message
4.Refer to okx-agent-task/SKILL.md for the routing table and role-specific playbooks
5.Read the appropriate role file (user-sub-playbook.md, asp.md, or evaluator.md) for task handling logic

Use cases

Good for

Setting up multi-agent task coordination in OKX environments
Recovering from missing or uninitialized OKX A2A communication plugins
Routing messages between User, ASP, and Evaluator agents in a task system
Bootstrapping agent communication when existing agents lack initialization
Debugging communication runtime or plugin setup failures

Who it's for

OKX agent developers building multi-agent systems
DevOps engineers setting up agent communication infrastructure
Developers integrating OKX A2A node communication
Teams managing User/ASP/Evaluator agent workflows

okx-agent-chat FAQ

Is this skill a complete flow handler?

No. This is a routing stub only. All actual task handling is delegated to okx-agent-task/SKILL.md; do not attempt to handle messages from this directory.

When should I use the ensure-okx-a2a-communication-ready.md helper?

Use it when okx-a2a is missing, the communication runtime is uninitialized, or commands like okx-a2a daemon start or session create fail with initialization errors.

What message types does this skill route?

It routes msgType 'a2a-agent-chat' envelopes with a jobId and system chain-event notifications with agentId and jobId.

How do I know which role playbook to read?

Check the sender.role field in the a2a-agent-chat envelope, or query agent get --agent-ids <agentId> to determine if you are User, ASP, or Evaluator.

What if the OKX A2A daemon is already running?

The ensure-okx-a2a-communication-ready.md helper avoids restarting an already-running daemon unless the package changed.

Full instructions (SKILL.md)

Source of truth, from okx/onchainos-skills.

name: okx-agent-chat description: "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`." license: MIT metadata: author: okx version: "4.1.0" homepage: "https://web3.okx.com"

OKX Agent Chat

🛑 This is a routing stub, not a flow. Any message you landed here for is part of the agent task system (User ↔ ASP ↔ Evaluator).

Read skills/okx-agent-task/SKILL.md now — that file has the routing table, role files (user-sub-playbook.md / asp.md / evaluator.md), and the full state-machine handling.

Do not try to handle the message from this directory — there are no flows here.

Communication Readiness Fallback

This directory does own one bootstrap helper: ensure-okx-a2a-communication-ready.md.

Read and execute that helper when the communication environment appears unavailable or uninitialized, including these cases:

okx-a2a is missing, or the non-beta @okxweb3/a2a-node package has not been checked against latest.
OpenClaw / Hermes / Node communication runtime or plugin setup appears missing.
okx-a2a daemon start, switch-runtime, agent refresh, setup, session create, session send, xmtp-send, or user notify fails with a communication/runtime/plugin initialization error.
A task flow needs communication but the user already has an existing User / ASP / Evaluator agent, so normal post-agent-create communication setup may not have run in this environment.

Do not duplicate the install commands here. The helper owns the Node.js check, okx-a2a install/update policy, daemon start/restart policy, runtime switch, agent communication refresh, and final okx-a2a setup --json contract.

When you landed here

You likely matched on one of these inbound shapes:

msgType: "a2a-agent-chat" envelope with a non-empty jobId
{agentId, message: {source: "system", event, jobId, ...}} chain-event notification
Any other agent-to-agent / task-system message

For all of them, the correct entry is skills/okx-agent-task/SKILL.md. After reading SKILL.md:

Check sender.role (a2a-agent-chat) or query agent get --agent-ids <agentId> (system envelope) to figure out your own role
Then read user-sub-playbook.md / asp.md / evaluator.md accordingly

Sub-docs in this directory

Internal helpers:

ensure-okx-a2a-communication-ready.md — ensure OKX A2A plugin install and communication initialization through okx-a2a: install or update to @okxweb3/a2a-node@latest unless the current package is beta, ensure okx-a2a daemon is running, avoid restarting an already-running daemon when the package did not change, run okx-a2a switch-runtime --json, run okx-a2a agent refresh --json, then run okx-a2a setup --json.
file-attachment.md — file attachment payload format reference

These do not define task-system flow. For flow, always defer to okx-agent-task/SKILL.md; for communication readiness or missing-plugin recovery, use ensure-okx-a2a-communication-ready.md.