Gate Exchange Assets Assistant

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 ./references/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_dc_list_dc_accounts
• cex_earn_list_dual_balance
• cex_earn_list_dual_orders
• cex_earn_list_structured_orders
• cex_fx_get_fx_accounts
• cex_margin_list_margin_accounts
• cex_options_list_options_account
• cex_spot_get_spot_accounts
• cex_spot_list_spot_account_book
• cex_tradfi_query_user_assets
• cex_unified_get_unified_accounts
• cex_wallet_get_total_balance

Authentication

• Credentials Source: Local Gate MCP deployment (GATE_API_KEY, GATE_API_SECRET)
• API Key Required: Yes
• Permissions: Delivery:Read, Earn:Read, Fx:Read, Margin:Read, Options:Read, Spot:Read, Tradfi:Read, Unified:Read, Wallet:Read
• Never ask the user to paste secrets into chat; rely on the configured MCP session only.
• API Key Provisioning Reference: https://www.gate.com/myaccount/profile/api-key/manage (create or rotate keys outside the chat when the local MCP setup requires them).

Installation Check

• Required: Gate (main)
• Install: Use the local Gate MCP installation flow for the current host IDE before continuing.
• Continue only after the Gate MCP session is configured with the credentials listed above; do not switch to browser auth or ask the user to paste secrets into chat.

MCP Mode

Read and strictly follow references/mcp.md, then execute this skill's assets-query workflow.

• SKILL.md keeps intent routing and rendering rules.
• references/mcp.md is the authoritative MCP execution layer for multi-account data collection, normalization, and degraded output handling.

Domain Knowledge

MCP Tool Mapping (Gate gate-mcp)

Account Name Mapping (details key → Display)

Key Rules

• Read-only. No trading, transfer, or order placement.
• TradFi / payment: USDx and payment assets are NOT included in CEX total; display separately.
• Unified account: When margin_mode is classic/cross_margin/portfolio, spot may be merged into "trading account". Do NOT use internal terms like "advanced mode", "S1/S2".
• Pair format: Futures use no-slash (BTCUSDT); spot/margin use slash (BTC/USDT).
• Precision: Fiat valuation 2 decimals; dust (\x3C$0.01) show as \x3C$0.01; finance yesterday PnL up to 8 decimals.

Case Routing Map

I. Total & Overview (Case 1)

II. Specific Currency (Case 2)

III. Specific Account + Currency (Case 3)

IV. Sub-Account Queries (Case 4–15)

V. Account Book (Legacy 5–7)

Special Scenario Handling

Output Templates

Case 1 – Total Balance:

Your total CEX asset valuation ≈ ${total.amount} USDT
🕒 Updated: {time} (UTC+8)
💰 Account distribution: details keys (spot/futures/delivery etc.) amount, show only amount > 0

Case 2 – Specific Currency:

You hold {total_qty} {COIN} (≈ ${total_val} USDT)
🕒 Updated: {time} (UTC+8)
💰 Asset distribution: {account}: {qty} {COIN}, ≈ ${val} ({pct}%)

Case 15 – TradFi:

Your TradFi account details:
Net value: {net_value} USDx | Balance: {balance} USDx | Unrealised PnL: {unrealised_pnl} USDx
Margin: {margin} USDx | Available margin: {available_margin} USDx | Margin ratio: {ratio}% (max 999+%)
⚠ TradFi account in USDx, 1:1 with USDT, not in CEX total valuation.

Acceptance Test Queries (Validation)

Cross-Skill Workflows

• Before trading: User asks "Can I buy 100U BTC?" → This skill: cex_spot_get_spot_accounts currency=USDT → Route to gate-exchange-spot if sufficient.
• After transfer: Route to this skill for updated balance when user asks.
• Transfer card: When futures/options = 0, recommend [Transfer] and trigger transfer skill.

Safety Rules

• Read-only only. Never call create_order, cancel_order, create_transfer, or any write operation.
• If user intent includes trading, transfer, or order placement → route to appropriate skill.
• Always clarify currency and scope (spot vs all wallets) when ambiguous.

For detailed scenario templates and edge cases, see references/scenarios.md.