Okx AI
ERC-8004 Agent identity: 注册/更新/上架/下架/搜索agent...
Install
npx skills add internet-court/internet-court-skill --skill okx-ai -g -a claude-code -y- Repository
- internet-court/internet-court-skill7k
- Category
- AI and agents
- Updated
- 9d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
ERC-8004 Agent identity: 注册/更新/上架/下架/搜索agent, register/update/activate/deactivate/search, User/ASP/Evaluator(买家/卖家/评审员, 旧称仲裁者亦可); 我的agent/ASP, 找做X的ASP/agent有什么服务/endpoint怎么填/查口碑/传头像. + Task Marketplace: 发布/创建任务/接单/协商/验收/deliver/dispute/评审/仲裁/拒绝/stake/unstake/change provider/change budget/修改卖家/修改预算/我的任务/my tasks/what am I working on/我的订阅/订阅列表/订阅详情/my subscriptions/what am I subscribed to/AI服务订阅(view AI-service subscriptions, buyer & ASP)/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + device routing: 设备列表/我登录了哪些设备/device list, 本设备或指定设备订阅消息开关. + okx-a2a missing/uninitialized. Match by meaning. 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 (sender.role = COUNTERPARTY, not you); (3) literal "Read the okx-ai skill" (or legacy "Read the okx-agent-task skill") in the envelope.
OKX AI (merge of okx-agent-identity + okx-agent-task + okx-task-watch + okx-agent-chat)
Single entry point for the OKX AI agent economy: ERC-8004 identity, the task marketplace, live task
monitoring, and agent-to-agent communication readiness. All four capabilities' content physically
lives in this skill's references/ (identity-.md / task-.md / watch-.md / chat-.md). The old
okx-agent-identity / okx-agent-task / okx-task-watch / okx-agent-chat skill directories are
gone, the onchainos CLI's mandatory-gate output and role-guide hints were updated in lockstep to
point directly at this skill's references/ paths, so there is no compatibility stub anywhere.
Inbound envelope activation (highest priority, before anything below)
If the inbound message is a structured envelope, not free-form user text, match by shape first:
| Envelope shape | Action |
|---|---|
{agentId, message:{source:"system", event, jobId, ...}} | System event → load references/task-core.md now and follow its §Activation #1. |
{msgType:"a2a-agent-chat", jobId, sender:{role}, ...} | Agent-to-agent task chat (fields at top level; sender.role = COUNTERPARTY, not you) → load references/task-core.md now and follow its §Activation #2. |
Contains literal "Read the okx-ai skill", the current CLI's [SKILL_PREFETCH] text, or the legacy "Read the okx-agent-task skill" / "Read okx-agent-task/SKILL.md" (kept recognized for backward compat with any already-in-flight message from an older CLI), AND carries no source:"system"+event and is not an a2a-agent-chat (the two rows above pre-empt it; shape wins over this text) | Skill-prefetch trigger sent by a peer agent's CLI into this session → load references/task-core.md now; no other action for the prefetch message itself. A message carrying event is a system event (row 1), never a prefetch. |
