okx-guide
Onchain OS onboarding & guide hub — the single entry for first-time, 'what is this / how do I use it', OKX.AI, and customer-support intents; classifies the intent and routes to the right sub-flow via its Intent Routing table. Covers: (1) Onchain OS onboarding + welcome banner — 'what is onchainos', 'what is onchain os', 'what can it do', 'what can onchainos do', 'what does onchainos do', 'how do I use this', 'how do I play', 'how to use onchainos', 'how to play onchainos', 'how does onchainos work', 'how do I start', 'getting started', 'tutorial', 'onboarding', 'first time', 'I just installed', 'now what', 'what do I do now', 'where do I start', 'who are you', 'what are you', 'introduce onchainos', 'tell me about onchainos', 'I'm new'; (2) OKX.AI intro & role-registration routing (the Agent economic system — roles User / ASP / Evaluator) — 'what is OKX.AI', 'OKX.AI 是什么', 'how to use OKX.AI', 'OKX.AI 快速开始', and any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, 啥是okxai); (3) customer support / Help Center — 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback', 'report a bug / system error', 'help center', 'FAQ', 'user guide', 'something is broken'. NOT for: direct on-chain actions (swap / wallet / balance / token) or Agent task lifecycle (publish / accept / deliver / dispute) — those have their own skills.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/okx-guide && cp -r /tmp/okx-guide/vendored/okx/okx-guide ~/.claude/skills/okx-guideSKILL.md
# Onchain OS — Guide Hub (Onboarding · OKX.AI · Support)
The single entry point for onboarding, OKX.AI onboarding, and customer-support intents. Classify the user's intent, load the matching reference file, and follow it to completion. Each reference file is self-contained (it carries its own flow steps and acceptance criteria).
## Pre-flight Checks
**MUST**: Run the shared preflight **only for the onboarding flow** (§1 → `references/how-to-play.md`): read `../okx-agentic-wallet/_shared/preflight.md`; if that file does not exist, read `_shared/preflight.md` instead.
- **OKX.AI** (§2 → `references/ai-guide.md`): do **NOT** run the shared preflight here. `ai-guide.md` does its own login/identity check via `onchainos wallet status`, and the registration playbooks run their own preflight. (This matches the pre-merge standalone behavior and avoids an extra CLI round-trip.)
- **Support** (§3 → `references/ai-support.md`): conversation-layer only (no CLI) — no preflight.
## Intent Routing
Match the user's intent to a row, then read the Reference file(s) **before** responding and follow them exactly.
| User Intent | Reference |
|---|---|
| First-time / "what is onchainos" / "what can it do" / how to use / how to play / getting started / tutorial / "I just installed" / "now what" / "where do I start" / "I'm new" / welcome banner + numbered-pick routing | [`references/how-to-play.md`](./references/how-to-play.md) |
| OKX.AI — "what is OKX.AI" / "how to use OKX.AI" / "OKX.AI quick start" (any spelling variant) / register a role (User / ASP / Evaluator) / platform detection / registered-user home | [`references/ai-guide.md`](./references/ai-guide.md) |
| Customer support / talk to a human / customer service / file a complaint / give feedback / report a bug or system error / Help Center / FAQ / user guide / "something is broken" | [`references/ai-support.md`](./references/ai-support.md) |
## Disambiguation
**MUST**: When an opener could match more than one row, prefer the more specific intent:
- The subject is explicitly **OKX.AI** (any spelling / spacing / casing / typo variant) → **ai-guide.md**, even when phrased as onboarding ("how do I play OKX.AI").
- Generic **Onchain OS** onboarding, or a blank "now what / where do I start / I'm new" with no product named → **how-to-play.md**.
- Intent to reach a **human / complaint / feedback / bug / FAQ / help docs** → **ai-support.md**.Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.