Gate Exchange Subaccount

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).

Gate Exchange Sub-Account 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

gate-cli commands used

Query Operations (Read-only)

• gate-cli cex sub-account get
• gate-cli cex sub-account list
• gate-cli cex sub-account lock
• gate-cli cex sub-account unlock

Execution Operations (Write)

• gate-cli cex sub-account create

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.
• Permissions: Sa:Write
• Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

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 — that is equivalent valid config for gate-cli. When both are unset or empty, 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: Do not proceed with authenticated calls until the CLI behaves as expected (e.g. gate-cli --version or a read-only gate-cli cex ... command from this skill); confirm credentials resolve before mutating operations.

Execution mode

Read and strictly follow references/gate-cli.md, then execute this skill's sub-account workflow.

• SKILL.md keeps intent routing and permission boundaries.
• references/gate-cli.md is the authoritative gate-cli execution contract for create/lock/unlock confirmation gates and status verification.

Prerequisites

• MCP Dependency: Requires gate-mcp to be installed.
• Authentication: All sub-account operations require API key authentication with main-account privileges.
• Permission: The current user must be a main account holder to manage sub-accounts.

Available MCP Tools

Workflow

Step 1: Identify User Intent

Parse the user's message to determine which sub-account operation they need.

Key data to extract:

• intent: One of query_status, list_all, create, lock, unlock
• user_id: Sub-account UID (required for query_status, lock, unlock)
• login_name: Desired username (for create, may need to ask user)

Intent detection rules:

Step 2: Execute by Intent

Case A: Query Sub-Account Status (query_status)

Call gate-cli cex sub-account get with:

• user_id: The sub-account UID provided by the user

Key data to extract:

• login_name: Sub-account username
• remark: Sub-account remark/note
• state: Account state (normal / locked)
• type: Account type (normal / pool)
• create_time: Account creation timestamp

Present the sub-account details in a structured format.

Case B: List All Sub-Accounts (list_all)

Call gate-cli cex sub-account list with:

• type: "0" (normal sub-accounts only)

Key data to extract:

• For each sub-account: user_id, login_name, remark, state, create_time

Present results as a table with username, UID, remark (if any), and current status.

Case C: Create Sub-Account (create)

Pre-check: Call gate-cli cex sub-account list with type: "0" to get the current list of normal sub-accounts. Check if the user can still create more sub-accounts based on the returned count.

If creation is available:

1. Ask the user to provide a login name for the new sub-account
2. Optionally collect: email, remark
3. Confirm all details with the user before proceeding
4. Call gate-cli cex sub-account create with:

• login_name: User-provided login name (required)
• email: User-provided email (optional)
• remark: User-provided remark (optional)

5. Present the newly created sub-account details

Key data to extract:

• user_id: Newly created sub-account UID
• login_name: Confirmed username
• state: Should be "normal"

Important: Only normal sub-accounts can be created through this skill.

Case D: Lock Sub-Account (lock)

1. Validate that user_id is provided; if not, ask the user
2. Call gate-cli cex sub-account get with user_id to verify the sub-account exists and belongs to the main account
3. If the sub-account is already locked, inform the user and stop
4. Confirm with the user: "Are you sure you want to lock sub-account {user_id} ({login_name})? This will disable login and trading for this sub-account."
5. On confirmation, call gate-cli cex sub-account lock with:

• user_id: The sub-account UID

6. Report the result

Key data to extract:

• Lock operation success/failure status

Case E: Unlock Sub-Account (unlock)

1. Validate that user_id is provided; if not, ask the user
2. Call gate-cli cex sub-account get with user_id to verify the sub-account exists and is currently locked
3. If the sub-account is already unlocked/normal, inform the user and stop
4. Confirm with the user: "Are you sure you want to unlock sub-account {user_id} ({login_name})?"
5. On confirmation, call gate-cli cex sub-account unlock with:

• user_id: The sub-account UID

6. Report the result

Key data to extract:

• Unlock operation success/failure status

Step 3: Format and Respond

Present results using the Report Template below. Always include relevant context and next-step suggestions.

Judgment Logic Summary

Report Template

Query Status Response

Sub-Account Details
---
Username: {login_name}
UID: {user_id}
Status: {state}
Type: {type}
Remark: {remark or "N/A"}
Created: {create_time}

List All Sub-Accounts Response

Your Sub-Accounts
---
| # | Username | UID | Status | Remark |
|---|----------|-----|--------|--------|
| 1 | {login_name} | {user_id} | {state} | {remark or "-"} |
| 2 |... |... |... |... |

Total: {count} sub-account(s)

Create Sub-Account Response

Sub-Account Created Successfully
---
Username: {login_name}
UID: {user_id}
Status: Normal
Remark: {remark or "N/A"}

Note: Only normal sub-accounts can be created through this interface.

Lock/Unlock Response

Sub-Account {Action} Successfully
---
Username: {login_name}
UID: {user_id}
Previous Status: {previous_state}
Current Status: {new_state}

Domain Knowledge

• A main account on Gate can create multiple sub-accounts for asset isolation, strategy separation, or team management.
• Sub-accounts share the main account's KYC verification but have independent trading and wallet capabilities.
• Locking a sub-account disables both login and trading; the assets remain safe but inaccessible until unlocked.
• There are two types of sub-accounts: normal (type=0) and pool (type=1). This skill only supports creating normal sub-accounts.
• Sub-account creation requires a unique login name. Email and remark are optional.

Safety Rules

• Write operations (gate-cli cex sub-account create, gate-cli cex sub-account lock, gate-cli cex sub-account unlock): Always require explicit user confirmation before execution. Never auto-execute.
• UID validation: Before lock/unlock, always verify the sub-account exists and belongs to the current main account.
• State check: Before lock/unlock, check current state to avoid redundant operations.
• No sensitive data exposure: Never expose API keys, internal endpoint URLs, or raw error traces.
• Normal sub-accounts only: Creation is restricted to normal sub-accounts (type=0). Do not attempt to create pool sub-accounts.

Error Handling

Prompt Examples & Scenarios

See scenarios.md for full prompt examples and expected behaviors.