gate-exchange-kyc
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-clicommands 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_KEYandGATE_API_SECRETare not both set on the host, rungate-cli config initto complete the wizard for API key, secret, profiles, and defaults (see gate-cli). - Env / flags:
gate-cli config initis not required when credentials are already supplied — e.g. bothGATE_API_KEYandGATE_API_SECRETset on the host, or--api-key/--api-secretwhere 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(runsh ./setup.shfrom this skill directory if missing; optionalGATE_CLI_SETUP_MODE=release). - Add
$HOME/.openclaw/skills/bintoPATHif you invokegate-cliby name (or the directory wheresetup.shinstalls it). - Credentials: When
GATE_API_KEYandGATE_API_SECRETare both set (non-empty) for the host, do not requiregate-cli config initforgate-cli-backed auth. When both are unset or empty and authenticated state queries are needed, remind the operator to rungate-cli config initor to configureGATE_API_KEY/GATE_API_SECRETin 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.mdkeeps routing, trigger phrases, and product semantics.references/gate-cli.mdis the authoritativegate-cliexecution 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.