okx-guide

作成者: okx

オンチェーンOSのオンボーディング&ガイドハブ — 初めてのユーザー向けの「これは何か」「どう使うか」、OKX.AI、カスタマーサポートに関する意図の単一エントリーポイント。意図を分類し、インテントルーティングテーブルを介して適切なサブフローにルーティングします。対象範囲:(1) オンチェーンOSのオンボーディング+ウェルカムバナー — 「オンチェーンOSとは」「オンチェーンOSの機能」「何ができるか」「どう使うか」「どうプレイするか」「オンチェーンOSの使い方」「オンチェーンOSのプレイ方法」など。

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

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 IntentReference
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 routingreferences/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 homereferences/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

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 docsai-support.md.

okxのその他のスキル

okx-agent-identity
okx
We need to translate the given text from English/Chinese to Japanese. The text describes an agent identity system on XLayer using ERC-8004. It includes roles and usage examples. We must preserve the name "okx-agent-identity" but it's not in the text, so we ignore. Translate the entire text inside <text> to Japanese, keeping technical terms like ERC-8004, XLayer, agent, ASP, etc. Also keep the Chinese terms as they are? The instruction says preserve product names, protocol names, URLs, numbers, technical terms. The Chinese terms like 用户, 买家, etc. are part of the roles and usage examples. Should we translate them to Japanese? The source text has both English and Chinese. The target language is Japanese, so we should translate the English and Chinese into Japanese. But the Chinese terms are listed as alternatives for roles. For consistency, we should translate them to Japanese equivalents. However, the instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." The Chinese words like
developmentapi
okx-ai-guide
okx
OKX.AI(Agent経済システム)の紹介とオンボーディングエントリ。ユーザーがOKX.AIとは何か、何ができるか、使い方や始め方を尋ねたり、OKX.AIのチュートリアル/クイックスタート/ヘルプを求めたり、製品名を様々なスペル/スペース/大文字小文字/タイプミスのバリエーション(OKXAI、okx ai、okx-ai、小文字のokx.ai、誤入力された中国語の「啥是okxai」など)で入力した場合に使用します。例:what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始、およびあらゆる言語での言い換え。ランタイムプラットフォームを検出し、…を紹介します。
researchapidocument
okx-agentic-wallet
okx
OKX Agentic WalletとそのGas Station機能に関する信頼できる情報源。Gas Stationは、サードパーティのRelayerを介したSolana上のOKXのステーブルコインガス機能であり、Solanaのみ対応、EIP-7702非対応。Gas Stationに関する質問(概要、動作方法、対応トークン、手数料、有効化/無効化、デフォルトガストークンの変更、Jito Bundler互換性)およびウォレット操作全般(ログイン、OTP認証、アカウントの追加/切り替え/ステータス確認/ログアウト、残高、資産、保有状況、アドレス、入金/受取/チャージなど)には必ず呼び出すこと。
apiweb-scrapingdevelopment
okx-agent-chat
okx
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`.
developmentapicommunication
okx-agent-task
okx
受信エンベロープで必ず起動:(1) {agentId, message:{source:"system", event, jobId, ...}} — システムイベント;(2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — エージェント間タスクチャット(フィールドはトップレベル;sender.role = 相手側、自分ではない);(3) エンベロープ内のリテラル「Read okx-agent-task/SKILL.md」。以下のキーワードでも起動:发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-agent-payments-protocol
okx
We need to translate the given English text into Japanese, preserving the specified name "okx-agent-payments-protocol" but not including it unless it appears in the source text. The source text does not contain that name, so we just translate the text inside <text>. The text is a description of when to use the agent skill. We must preserve product names, protocol names, URLs, numbers, technical terms. So terms like HTTP 402, x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, paymentId, a2a_ link, creating / checking a payment link, A2MCP, A2MCP endpoint, Agent's endpoint, concrete endpoint should be kept as is or with appropriate Japanese punctuation. Also note the ellipsis at the end. We need to produce
okx-security
okx
We need to translate the given text from English to Japanese. The text describes a skill for security scanning. We must preserve the name "okx-security" but it's not in the text, so we don't include it. We translate the entire text inside <text>. No extra commentary, no labels. Just the translation. The text: "Use this skill for security scanning: check transaction safety, is this transaction safe, pre-execution check, security scan, token risk scanning, honeypot detection, DApp/URL phishing detection, message signature safety, malicious transaction detection, approval safety checks, token approval management. Triggers: 'is this token safe', 'check token security', 'honeypot check', 'scan this tx', 'scan this swap tx', 'tx risk check', 'is this URL a scam', 'check if this dapp is safe', 'phishing..." We need to translate naturally into Japanese. Keep technical terms like "honeypot", "DApp", "URL", "tx" (transaction), "swap", "phishing
okx-task-watch
okx
We need to translate the text inside <text> from English to Japanese. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. The name "okx-task-watch" is not in the text, so we don't include it. We must not add labels or extra commentary. The text contains a mix of Japanese and English phrases. The target language is Japanese, so we should translate the English parts into Japanese, but keep technical terms like "okx-a2a", "user watch", "user outdated-list", "decision_request", etc. Also preserve "OKX A2A" as is. The text already has some Japanese: "监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听" - these are Chinese? Actually, the source text includes Chinese characters. The instruction says "Translate only the text inside <text>." and target language is Japanese. So we need to convert the Chinese parts to Japanese? But
developmentapiproductivity