{"skill":{"slug":"gate-exchange-vip-fee","displayName":"Gate VIP & Fee Query Skill","summary":"Gate VIP tier and trading fee query skill. Use when the user asks about their fee rates or VIP level. Triggers on 'VIP level', 'trading fee', 'fee rate', 'sp...","description":"---\nname: gate-exchange-vipfee\nversion: \"2026.3.23-1\"\nupdated: \"2026-03-23\"\ndescription: \"Gate VIP tier and trading fee query skill. Use when the user asks about their fee rates or VIP level. Triggers on 'VIP level', 'trading fee', 'fee rate', 'spot fee', 'futures fee'.\"\n---\n\n# Gate VIP & Fee Query Assistant\n\n## General Rules\n\n⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.\nDo NOT select or call any tool until all rules are read. These rules have the highest priority.\n→ Read [gate-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/gate-runtime-rules.md)\n- **Only call MCP tools explicitly listed in this skill.** Tools not documented here must NOT be called, even if they\n  exist in the MCP server.\n\n---\n\n## MCP Dependencies\n\n### Required MCP Servers\n| MCP Server | Status |\n|------------|--------|\n| Gate (main) | ✅ Required |\n\n### MCP Tools Used\n\n**Query Operations (Read-only)**\n\n- cex_account_get_account_detail\n- cex_wallet_get_wallet_fee\n\n### Authentication\n- API Key Required: Yes (see skill doc/runtime MCP deployment)\n- Permissions: Account:Read, Wallet:Read\n- Get API Key: https://www.gate.io/myaccount/profile/api-key/manage\n\n### Installation Check\n- Required: Gate (main)\n- Install: Run installer skill for your IDE\n  - Cursor: `gate-mcp-cursor-installer`\n  - Codex: `gate-mcp-codex-installer`\n  - Claude: `gate-mcp-claude-installer`\n  - OpenClaw: `gate-mcp-openclaw-installer`\n\n## MCP Mode\n\n**Read and strictly follow** [`references/mcp.md`](./references/mcp.md), then execute this skill's VIP/fee query workflow.\n\n- `SKILL.md` keeps intent routing and rendering rules.\n- `references/mcp.md` is the authoritative MCP execution layer for account/fee data retrieval and safe output behavior.\n\n## Quick Start\n\nBelow are the most common prompts to get started quickly:\n\n1. **Query VIP tier**\n   > What is my VIP level?\n\n2. **Query trading fees**\n   > Show me the spot and futures trading fees.\n\n3. **Query VIP tier and fees together**\n   > Check my VIP level and trading fees.\n\n## Domain Knowledge\n\n### Tool Mapping by Domain\n\n| Group | Tool Calls |\n|-------|------------|\n| Account / VIP tier | `cex_account_get_account_detail` |\n| Trading fee rates | `cex_wallet_get_wallet_fee` |\n\n### Key Concepts\n\n- **VIP Tier**: Gate assigns VIP levels (VIP 0 – VIP 16) based on trading volume and asset holdings. Higher VIP tiers unlock lower fee rates.\n- **Spot Fee**: The maker/taker fee rate applied to spot trading pairs.\n- **Futures Fee**: The maker/taker fee rate applied to futures/contract trading, differentiated by settlement currency (BTC, USDT, USD).\n- The `cex_wallet_get_wallet_fee` tool returns fee rates for both spot and futures in a single response. Use the `settle` parameter to query futures-specific fees.\n\n### API Behavior Notes\n\n- **Account-level pricing**: Gate fee rates are determined by the user's VIP tier. The `currency_pair` parameter does not change the returned fee values — all trading pairs share the same account-level rate.\n- **`settle` parameter scope**: The `settle` parameter only affects futures fee fields (`futuresMakerFee` / `futuresTakerFee`). Spot fees (`makerFee` / `takerFee`) remain unchanged regardless of `settle`.\n- **Invalid `currency_pair` handling**: The API does not return an error for non-existent trading pairs. It silently returns the default account-level fees. Do not treat a successful response as confirmation that the trading pair exists.\n\n## Workflow\n\nWhen the user asks about VIP tier or trading fees, follow this sequence.\n\n### Step 1: Identify Query Type\n\nClassify the request into one of these categories:\n\n1. **VIP tier query** — user wants to know their current VIP level\n2. **Fee rate query** — user wants to know spot and/or futures trading fee rates\n3. **Combined query** — user wants both VIP tier and fee information\n\nKey data to extract:\n- `query_type`: \"vip\", \"fee\", or \"combined\"\n- `currency_pair` (optional): specific trading pair for fee lookup\n- `settle` (optional): futures settlement currency (BTC / USDT / USD)\n\n### Step 2: Query VIP Tier (if needed)\n\nIf `query_type` is \"vip\" or \"combined\":\n\nCall `cex_account_get_account_detail` with:\n- No parameters required\n\nKey data to extract:\n- `vip_level`: the user's current VIP tier (e.g., VIP 0, VIP 1, etc.)\n\n### Step 3: Query Trading Fee Rates (if needed)\n\nIf `query_type` is \"fee\" or \"combined\":\n\nCall `cex_wallet_get_wallet_fee` with:\n- `currency_pair` (optional): specify trading pair context (note: fee rates are account-level and do not vary by pair)\n- `settle` (optional): futures settlement currency — affects futures fee fields only\n\nKey data to extract:\n- `maker_fee_rate`: spot maker fee rate\n- `taker_fee_rate`: spot taker fee rate\n- `futures_maker_fee_rate`: futures maker fee rate\n- `futures_taker_fee_rate`: futures taker fee rate\n\n### Step 4: Return Result\n\nFormat the response according to the Report Template. The API (`cex_wallet_get_wallet_fee`) always returns the full fee structure (spot + futures + delivery). Filter the output based on the user's original intent:\n\n- If user asked about **spot fees only** → show only `makerFee` / `takerFee`\n- If user asked about **futures/contract fees only** → show only `futuresMakerFee` / `futuresTakerFee`\n- If user asked about **trading fees** (general) → show both spot and futures\n- If user asked about **VIP only** → show only VIP level, no fee data\n- If user specified a `currency_pair` → append a note in the response: \"Note: The API returns account-level fee rates. The fee shown applies to all trading pairs; if the pair you specified does not exist, the result still reflects your default account fee rate.\"\n\nKey data to extract:\n- VIP level (if queried)\n- Spot maker/taker fee rates (if queried)\n- Futures maker/taker fee rates (if queried)\n\n## Judgment Logic Summary\n\n| Condition | Action |\n|-----------|--------|\n| User asks about VIP tier/level only | Call `cex_account_get_account_detail`, return VIP level |\n| User asks about trading fees only | Call `cex_wallet_get_wallet_fee`, return spot and futures fee rates |\n| User asks about both VIP and fees | Call both tools, return combined result |\n| User specifies a trading pair | Pass `currency_pair` parameter to `cex_wallet_get_wallet_fee` |\n| User specifies futures settlement currency | Pass `settle` parameter to `cex_wallet_get_wallet_fee` |\n| User asks about spot fees only | Call `cex_wallet_get_wallet_fee`, return only spot fee portion |\n| User asks about futures/contract fees only | Call `cex_wallet_get_wallet_fee` with `settle` parameter, return only futures fee portion |\n| User specifies a `currency_pair` | Append a disclaimer that the API does not validate trading pairs; the returned fee is the account-level default and the pair may not exist |\n| API returns error or empty data | Inform user of the issue and suggest checking account authentication |\n\n## Report Template\n\n```markdown\n## Query Result\n\n{vip_section}\n\n{fee_section}\n```\n\n**VIP Section** (when VIP is queried):\n\n```markdown\n### VIP Tier\n\n| Item | Value |\n|------|-------|\n| VIP Level | {vip_level} |\n```\n\n**Fee Section** (when fees are queried):\n\n```markdown\n### Trading Fee Rates\n\n| Category | Maker Fee | Taker Fee |\n|----------|-----------|-----------|\n| Spot | {spot_maker_fee} | {spot_taker_fee} |\n| Futures | {futures_maker_fee} | {futures_taker_fee} |\n```\n\n**Combined example output**:\n\n```markdown\n## Query Result\n\n### VIP Tier\n\n| Item | Value |\n|------|-------|\n| VIP Level | VIP 1 |\n\n### Trading Fee Rates\n\n| Category | Maker Fee | Taker Fee |\n|----------|-----------|-----------|\n| Spot | 0.1% | 0.1% |\n| Futures (USDT) | 0.015% | 0.05% |\n```\n\n## Error Handling\n\n| Error Type | Typical Cause | Handling Strategy |\n|------------|---------------|-------------------|\n| Authentication failure | API key invalid or expired | Inform user to check MCP configuration and API key validity |\n| Empty response | Account data not available | Inform user the query returned no data and suggest retrying |\n| Network error | MCP connection issue | Suggest user check MCP server connectivity |\n\n## Safety Rules\n\n- This Skill is read-only and does not perform any trading or account modification operations.\n- No user confirmation is required since all operations are queries only.\n- Never expose raw API keys or sensitive authentication details in responses.\n","tags":{"latest":"1.0.2"},"stats":{"comments":0,"downloads":624,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":3},"createdAt":1773490944206,"updatedAt":1778491905918},"latestVersion":{"version":"1.0.2","createdAt":1775115427896,"changelog":"- Introduced `references/mcp.md` as the authoritative guide for MCP execution and safe data retrieval.\n- Updated `SKILL.md` to streamline routing, reporting, and intent logic; details for data access have been moved to `references/mcp.md`.\n- Clarified workflow: follow shared MCP rules and the new reference document before any account or fee queries.\n- No changes to MCP server/tools or output format—behavior remains backward compatible.\n- Minor adjustments to the description and quick start for better clarity.","license":"MIT-0"},"metadata":null,"owner":{"handle":"gate-exchange","userId":"s172g4d1dcv6ccs6desbb2xw1583qza9","displayName":"Gate","image":"https://avatars.githubusercontent.com/u/33109813?v=4"},"moderation":{"isSuspicious":false,"isMalwareBlocked":false,"verdict":"clean","reasonCodes":["review.llm_review"],"summary":"Review: review.llm_review","engineVersion":"v2.4.24","updatedAt":1780090247714}}