okx-ai
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/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + okx-a2a missing/uninitialized. Match by meaning. MUST ACTIVATE on inbound envelopes: (1) {agentId, message:{source:"system", event, jobId,...}} system even
Profile →npx skills add internet-court/internet-court-skill --skill okx-ai --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`](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,
- Inbound envelope activation (highest priority — before anything below)
- Pre-flight (BLOCKING — the FIRST thing you do, before ANY onchainos command)
- Language Lock (apply on EVERY turn — highest priority, before routing)
- Routing (do this FIRST, before loading any reference — free-text intent only)
- Execution Checklist (identity ops)
- Gates (non-overridable, identity ops)
- UX Red Lines (sweep every user-visible message before sending, identity ops)
- Pre-Delivery Checklist (identity ops)
- Cost (answer INLINE — never enter the register flow)
- Task Marketplace
- Task Watch
- Communication Readiness
What does the okx-ai skill do?
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/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + okx-a2a missing/uninitialized. Match by meaning. MUST ACTIVATE on inbound envelopes: (1) {agentId, message:{source:"system", event, jobId,...}} system even
How do I install it?
Run `npx skills add internet-court/internet-court-skill --skill okx-ai --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From internet-court/internet-court-skill, a repository with 1,536 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.