okx-ai-guide
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 / quickstart / help, or types the product name in any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, mis-typed Chinese like 啥是okxai) — e.g. what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, and any paraphrase in any language. Detects the runtime platform, introduces the three roles (User / ASP / Evaluator), and routes the user into identity registration. NOT for generic onchain-OS onboarding, nor for direct task operations (publishing / accepting / delivering / disputing a task — a separate task-lifecycle flow).
- Installs
- 1.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/okx/onchainos-skills --skill okx-ai-guide- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads okx-ai-guide automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
OKX.AI Guide
The OKX.AI onboarding entry. Introduces OKX.AI (the Agent economic system), detects whether the current runtime can run OKX.AI, and routes the user into one of the three identity-registration flows — or, on an incompatible platform, tells them how to get a compatible one.
Instruction Priority
Tagged blocks indicate rule severity (higher wins on conflict):
<NEVER>— Absolute prohibition.<MUST>— Mandatory step.<SHOULD>— Best practice.
Scope & Boundary
This skill owns: OKX.AI intro + platform detection + login & identity detection (new vs returning user) + routing into registration. It does NOT:
- own the Onchain OS welcome banner — that is
okx-how-to-play. - implement registration — delegated to
okx-agent-identity(see §Step 5). - own the wallet-login flow — Step 1 only checks login via
wallet statusand hands off tookx-agentic-wallet's existing login flow when needed; the registration playbooks also run their own preflight.
Step 0 — Platform detection
<MUST> Run the detection function below and read its single-line output. `compatible` = output is NOT `unknown`. </MUST>detect_harness() {
if [ "${CLAUDECODE:-}" = "1" ]; then
echo "Claude Code"
elif [ -n "${HERMES_INTERACTIVE:-}" ] || [ -n "${HERMES_SESSION_SOURCE:-}" ] \
|| [ -n "${HERMES_YOLO_MODE:-}" ] || [ -n "${HERMES_QUIET:-}" ]; then
echo "Hermes"
elif [ -n "${OPENCLAW_CLI:-}" ] || [ -n "${OPENCLAW_SHELL:-}" ]; then
echo "OpenClaw"
elif [ -n "${CODEX_THREAD_ID:-}" ] || [ -n "${CODEX_CI:-}" ]; then
echo "Codex"
else
echo "unknown"
fi
}
detect_harness
- Output ∈ {
Claude Code,Hermes,OpenClaw,Codex} → compatible → Step 1. - Output =
unknown→ incompatible → Step 3.
Step 1 — Compatible: login + identity detection (routing gate)
Reached only when Step 0 is compatible. This step decides which page to show — by checking login first, identity second. The order is mandatory: agent get-my-agents requires a logged-in session, so never query identity before login is confirmed.
The branch is decided solely by whether agent get-my-agents returns any agent — never show the role page (Step 2) to a user who already has an identity, nor the registered home (Step 4) to a user with none.
Step 2 — Compatible & unregistered: role selection page
Reached from Step 1 when the user is logged in but has no OKX.AI identity. Render the role-selection page (Variant A) and route the 1/2/3 reply per references/unregistered-role-selection.md (contains Step 2 page + Step 5 routing). Load it when this branch is hit.
Step 3 — Incompatible: intro + install guide
Reached from Step 0 when the platform is incompatible (unknown). No login / identity check applies — OKX.AI cannot run here.
Free zone (1–5 sentences): answer the user's OKX.AI question, then segue.
Fixed zone: render Variant B from references/intro.md in the user's language; substitute {install_doc_url}. Do not offer numbered picks; end the turn.
Step 4 — Compatible & registered: user home
Reached from Step 1 when the user is logged in and already has ≥1 OKX.AI identity. Render the registered-user home (Variant C, filled field-exact from the agent get-my-agents result) and handle its menu replies (Step 6: 1 + Agent ID → that Agent's current tasks; 2 → top ASPs; Register a <role> → register a missing role) per references/registered-home.md. Load it when this branch is hit.
Step 5 — Routing after role pick
Handled in references/unregistered-role-selection.md alongside Step 2 (the 1/2/3 reply → wait-state line + registration playbook).
Step 6 — Registered-home menu routing (from Step 4)
Handled in references/registered-home.md — covers 1 + Agent ID → agent task-in-progress with status mapping, 2 → top ASPs by sales via agent search --query '按销量从高到低排序', and "Register a <role> identity" reroutes.
Acceptance Criteria
detect_harnessreturns the right platform for each marker set; everything else →unknown→ incompatible branch (Step 3).- Compatible branch (Step 1) checks login (
wallet status) before identity (agent get-my-agents) — identity is never queried while logged out.- Not logged in → hand off to the existing wallet-login flow, then resume the check.
- Logged in + no identity → role selection page (Step 2); replying
1/2/3renders the right wait-state and loads the right registration playbook (Step 5). - Logged in + ≥1 identity → registered user home (Step 4), filled from the
agent get-my-agentsresult; the home menu (Step 6) routes1+ an Agent ID → that Agent's current tasks viaagent task-in-progress, mapping each task'sstatusto a label (e.g.2submitted = delivered/awaiting acceptance) rather than blanket-labeling everything "in progress" (withcode=3001→ "not your Agent, re-enter"),2→ top ASPs by sales viaagent search --query '按销量从高到低排序'(backend semantic sort-by-sales).
- Incompatible branch (Step 3) shows the three-role intro (no picks) + install heads-up +
{install_doc_url}; ends the turn. OKX.AI 快速开始/OKX.AI quick starttriggers this skill.- Fixed-zone copy renders in the user's language; emojis / numbers / URLs / placeholders stay literal.
- Zero
onchainos agent createcalls in this skill (only read-onlywallet status/agent get-my-agents); zero Rust changes.
FAQ
What does the okx-ai-guide skill do?
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 / quickstart / help, or types the product name in any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, mis-typed Chinese like 啥是okxai) — e.g. what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, and any paraphrase in any language. Detects the runtime platform, introduces the three roles (User / ASP / Evaluator), and routes the user into identity registration. NOT for generic onchain-OS onboarding, nor for direct task operations (publishing / accepting / delivering / disputing a task — a separate task-lifecycle flow).
How do I install okx-ai-guide?
Run npx skills add https://github.com/okx/onchainos-skills --skill okx-ai-guide in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/okx-ai-guide/ (personal) or .claude/skills/okx-ai-guide/ (project).
Which AI agents can use okx-ai-guide?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is okx-ai-guide safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains okx-ai-guide?
It is published by okx in okx/onchainos-skills. It has 1,609 recorded installs.
More from okx/onchainos-skills
okx-dex-market
okx/onchainos-skills
Query read-only DEX token, market, signal, social, trenches, and WebSocket data. Use for token search, rankings, liquidity, holders, risk metadata, clusters, and trades; prices, K-lines/OHLC, indexes, and wallet PnL; smart-money/KOL/whale signals; news, sentiment, and token vibe; meme-launch, developer, bundle/sniper, and co-investor research; or DEX WebSocket clients. Triggers include hot tokens, holder concentration, smart money, top-trader leaderboards, pump.fun research, new token launches, on-chain token scanning, bundled or sniper activity, and WebSocket.
okx-agentic-wallet
okx/onchainos-skills
Operate OKX Onchain OS wallets and execute or inspect on-chain transactions. Use for wallet login/status/accounts/addresses/balances/holdings; receive/send/transfer; swaps, bridges, limit orders, contract calls, gas estimation, simulation, broadcast, and tracking; Bitcoin UTXO/BRC-20/inscriptions; signing, approvals, wallet policy/export, public-address portfolios, security checks, and audit logs.
okx-dapp-discovery
okx/onchainos-skills
Discover supported third-party DApps and route protocol-specific requests to OKX plugins without signing or broadcasting. Use for DApp discovery or comparison; a named protocol's operations or analytics; Polymarket/UpDown prediction markets, bets, and positions; protocol-native actions involving HYPE/HLP, stETH/wstETH, CAKE, CRV, COMP, RAY, GHO, or PT/YT; pump.fun writes; and unsupported-DApp alternatives. Supported DApp names include Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, and pump.fun. Requests to find, buy, or subscribe to a signal or signal service are OKX.AI marketplace workflows, even when they name Polymarket or another DApp.
okx-agent-payments-protocol
okx/onchainos-skills
Handle agent payments and paid endpoints via x402, MPP, payment links, a2a-pay, and HTTP-payment recurring or metered billing. Use for HTTP 402/payment-required; paid Agent or A2MCP endpoints; x402/Permit2; MPP channels, vouchers, or sessions; HTTP-payment subscriptions; or paymentId/link operations or status. Trigger phrases: x402/x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, x402 exact/exact+Permit2/upto/aggrdeferred, MPP charge/session, channelId/channelid, payment-channel voucher/topup/settle/refund, metered billing, paymentId, a2a, payment link, A2MCP, paid endpoint, and HTTP 402 period/permit2subscription.
okx-growth-competition
okx/onchainos-skills
List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners.
okx-guide
okx/onchainos-skills
Guide users through installing or updating Onchain OS, getting started, OKX.AI introduction and role-registration routing, and customer support. Use when someone wants to install or update the Onchain OS CLI or skills, is new or asks what Onchain OS or OKX.AI is, wants a quick start, needs to register a User, ASP, or Evaluator role, or asks for Help Center, support, feedback, or FAQs.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。