okx-guide

Name: okx-guide
Author: okx

315stars61forks

How to install okx-guide?

okx/onchainos-skills/okx-guide

$npx -y skills add okx/onchainos-skills --skill okx-guide

Installs into the current project.

Summary

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 — '

Files · 1

View on GitHub

SKILL.md

1	# Onchain OS — Guide Hub (Onboarding · OKX.AI · Support)
2
3	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).
4
5	## Pre-flight Checks
6
7	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.
8
9	- 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.)
10	- Support (§3 → `references/ai-support.md`): conversation-layer only (no CLI) — no preflight.
11
12	## Intent Routing
13
14	Match the user's intent to a row, then read the Reference file(s) before responding and follow them exactly.
15
16	\| User Intent \| Reference \|
17	\|---\|---\|
18	\| 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) \|
19	\| 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) \|
20	\| 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) \|
21
22	## Disambiguation
23
24	MUST: When an opener could match more than one row, prefer the more specific intent:
25
26	- 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").
27	- Generic Onchain OS onboarding, or a blank "now what / where do I start / I'm new" with no product named → how-to-play.md.
28	- Intent to reach a human / complaint / feedback / bug / FAQ / help docs → ai-support.md.

People who liked this also viewed

6 picks

Type

okx-guide

315stars61forks

View on GitHub

How to install okx-guide?

okx/onchainos-skills/okx-guide

$npx -y skills add okx/onchainos-skills --skill okx-guide

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Onchain OS — Guide Hub (Onboarding · OKX.AI · Support)
2
3	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).
4
5	## Pre-flight Checks
6
7	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.
8
9	- 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.)
10	- Support (§3 → `references/ai-support.md`): conversation-layer only (no CLI) — no preflight.
11
12	## Intent Routing
13
14	Match the user's intent to a row, then read the Reference file(s) before responding and follow them exactly.
15
16	\| User Intent \| Reference \|
17	\|---\|---\|
18	\| 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) \|
19	\| 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) \|
20	\| 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) \|
21
22	## Disambiguation
23
24	MUST: When an opener could match more than one row, prefer the more specific intent:
25
26	- 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").
27	- Generic Onchain OS onboarding, or a blank "now what / where do I start / I'm new" with no product named → how-to-play.md.
28	- Intent to reach a human / complaint / feedback / bug / FAQ / help docs → ai-support.md.

People who liked this also viewed

6 picks

Type