Resolving gate-cli (binary path)
Resolve gate-cli in order: (1) command -v gate-cli and gate-cli --version succeeds; (2) ${HOME}/.local/bin/gate-cli if executable; (3) ${HOME}/.openclaw/skills/bin/gate-cli if executable. Canonical rules: exchange-runtime-rules.md §4 (or gate-runtime-rules.md §4).
KYC Portal Skill
General Rules
⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.
Do NOT select or call any tool until all rules are read. These rules have the highest priority.
→ Read gate-runtime-rules.md
- Only use the
gate-cli commands explicitly listed in this skill. Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.
Skill Dependencies
Authentication
- Interactive file setup: when
GATE_API_KEY and GATE_API_SECRET are not both set on the host, run gate-cli config init to complete the wizard for API key, secret, profiles, and defaults (see gate-cli).
- Env / flags:
gate-cli config init is not required when credentials are already supplied — e.g. both GATE_API_KEY and GATE_API_SECRET set on the host, or --api-key / --api-secret where supported — never ask the user to paste secrets into chat.
- API Key Required: Conditional. Providing the KYC portal link does not require API key; if runtime supports user-state queries, login/auth may be required for those queries.
Installation Check
- Required:
gate-cli (run sh ./setup.sh from this skill directory if missing; optional GATE_CLI_SETUP_MODE=release).
- Add
$HOME/.openclaw/skills/bin to PATH if you invoke gate-cli by name (or the directory where setup.sh installs it).
- Credentials: When
GATE_API_KEY and GATE_API_SECRET are both set (non-empty) for the host, do not require gate-cli config init for gate-cli-backed auth. When both are unset or empty and authenticated state queries are needed, remind the operator to run gate-cli config init or to configure GATE_API_KEY / GATE_API_SECRET in the matching skill from the skill library (never ask the user to paste secrets into chat).
- Sanity check: Confirm the CLI works (e.g.
gate-cli --version) before relying on authenticated KYC state queries.
Execution mode
Read and strictly follow references/gate-cli.md, then execute this skill's KYC portal guidance workflow.
SKILL.md keeps routing, trigger phrases, and product semantics.references/gate-cli.md is the authoritative gate-cli execution contract, including detection, fallback, and safety boundaries.
Workflow
When the user asks about KYC or identity verification:
- Provide the KYC portal URL: https://www.gate.com/myaccount/profile/kyc_home
- Tell them to log in (if needed), open the link, and follow the on-screen steps on the portal.
If they ask about KYC status or want to submit documents in-chat, say verification is done only on the portal and direct them to the link (or to Gate support for status).
Judgment Logic Summary
| Condition |
Action |
| User wants to do KYC, find verification page, or asks why verification / why can't withdraw |
Give KYC portal URL and brief steps (log in, open link, complete on portal). |
| User asks for KYC status or tries to submit docs in-chat |
Redirect to portal or Gate support; do not perform verification. |
Report Template
You can complete identity verification (KYC) on the official KYC portal:
**KYC portal**: https://www.gate.com/myaccount/profile/kyc_home
Log in to your Gate account, open the link above, and follow the on-screen steps. Verification is done entirely on the portal.
1---2name: gate-exchange-kyc3description: Gate KYC portal routing skill. Use when the user asks to verify identity, complete KYC, or fix withdrawal blocks. Triggers on 'complete KYC', 'verify identity', 'why can't I withdraw'.4---56### Resolving `gate-cli` (binary path)78Resolve **`gate-cli`** in order: **(1)** **`command -v gate-cli`** and **`gate-cli --version`** succeeds; **(2)** **`${HOME}/.local/bin/gate-cli`** if executable; **(3)** **`${HOME}/.openclaw/skills/bin/gate-cli`** if executable. Canonical rules: [`exchange-runtime-rules.md`](https://github.com/gate/gate-skills/blob/master/skills/exchange-runtime-rules.md) §4 (or [`gate-runtime-rules.md`](https://github.com/gate/gate-skills/blob/master/skills/gate-runtime-rules.md) §4).91011# KYC Portal Skill1213## General Rules1415⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.16Do NOT select or call any tool until all rules are read. These rules have the highest priority.17→ Read [gate-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/gate-runtime-rules.md)18- **Only use the `gate-cli` commands explicitly listed in this skill.** Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.1920## Skill Dependencies212223### Authentication24- **Interactive file setup:** when **`GATE_API_KEY`** and **`GATE_API_SECRET`** are **not** both set on the host, run **`gate-cli config init`** to complete the wizard for API key, secret, profiles, and defaults (see [gate-cli](https://github.com/gate/gate-cli)).25- **Env / flags:** **`gate-cli config init`** is **not** required when credentials are already supplied — e.g. **both** **`GATE_API_KEY`** and **`GATE_API_SECRET`** set on the host, or **`--api-key`** / **`--api-secret`** where supported — never ask the user to paste secrets into chat.26- API Key Required: Conditional. Providing the KYC portal link does not require API key; if runtime supports user-state queries, login/auth may be required for those queries.2728### Installation Check29- **Required:** `gate-cli` (run `sh ./setup.sh` from this skill directory if missing; optional `GATE_CLI_SETUP_MODE=release`).30- Add `$HOME/.openclaw/skills/bin` to **`PATH`** if you invoke `gate-cli` by name (or the directory where [`setup.sh`](./setup.sh) installs it).31- **Credentials:** When **`GATE_API_KEY`** and **`GATE_API_SECRET`** are both set (non-empty) for the host, **do not** require **`gate-cli config init`** for `gate-cli`-backed auth. When **both** are unset or empty and authenticated state queries are needed, **remind** the operator to run **`gate-cli config init`** **or** to configure **`GATE_API_KEY`** / **`GATE_API_SECRET`** in the **matching skill** from the skill library (never ask the user to paste secrets into chat).32- **Sanity check:** Confirm the CLI works (e.g. **`gate-cli --version`**) before relying on authenticated KYC state queries.3334## Execution mode3536**Read and strictly follow** [`references/gate-cli.md`](./references/gate-cli.md), then execute this skill's KYC portal guidance workflow.3738- `SKILL.md` keeps routing, trigger phrases, and product semantics.39- `references/gate-cli.md` is the authoritative `gate-cli` execution contract, including detection, fallback, and safety boundaries.4041## Workflow4243When the user asks about KYC or identity verification:44451. Provide the KYC portal URL: https://www.gate.com/myaccount/profile/kyc_home462. Tell them to log in (if needed), open the link, and follow the on-screen steps on the portal.4748If they ask about KYC status or want to submit documents in-chat, say verification is done only on the portal and direct them to the link (or to Gate support for status).49## Judgment Logic Summary5051| Condition | Action |52|-----------|--------|53| User wants to do KYC, find verification page, or asks why verification / why can't withdraw | Give KYC portal URL and brief steps (log in, open link, complete on portal). |54| User asks for KYC status or tries to submit docs in-chat | Redirect to portal or Gate support; do not perform verification. |5556## Report Template5758```markdown59You can complete identity verification (KYC) on the official KYC portal:6061**KYC portal**: https://www.gate.com/myaccount/profile/kyc_home6263Log in to your Gate account, open the link above, and follow the on-screen steps. Verification is done entirely on the portal.64```
gate