Gate Exchange Subaccount

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 call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they exist in the MCP server.

MCP Dependencies

Required MCP Servers

MCP Tools Used

Query Operations (Read-only)

• cex_sa_get_sa
• cex_sa_list_sas
• cex_sa_lock_sa
• cex_sa_unlock_sa

Execution Operations (Write)

• cex_sa_create_sa

Authentication

• API Key Required: Yes (see skill doc/runtime MCP deployment)
• Permissions: Sa:Write
• Get API Key: https://www.gate.io/myaccount/profile/api-key/manage

Installation Check

• Required: Gate (main)
• Install: Run installer skill for your IDE
  • Cursor: gate-mcp-cursor-installer
  • Codex: gate-mcp-codex-installer
  • Claude: gate-mcp-claude-installer
  • OpenClaw: gate-mcp-openclaw-installer

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 cex_sa_get_sa 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 cex_sa_list_sas 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 cex_sa_list_sas 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 cex_sa_create_sa 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 cex_sa_get_sa 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 cex_sa_lock_sa 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 cex_sa_get_sa 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 cex_sa_unlock_sa 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 (cex_sa_create_sa, cex_sa_lock_sa, cex_sa_unlock_sa): 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.