Skill: gate-exchange/gate-exchange-vip-fee (version 1.0.2)

--- name: gate-exchange-vipfee version: "2026.3.23-1" updated: "2026-03-23" description: "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'." --- # Gate VIP & Fee Query 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 [gate-runtime-rules.md](https://github.com/gate/gate-skills/blob/master/skills/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 Server | Status | |------------|--------| | Gate (main) | ✅ Required | ### MCP Tools Used **Query Operations (Read-only)** - cex_account_get_account_detail - cex_wallet_get_wallet_fee ### Authentication - API Key Required: Yes (see skill doc/runtime MCP deployment) - Permissions: Account:Read, Wallet:Read - 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` ## MCP Mode **Read and strictly follow** [`references/mcp.md`](./references/mcp.md), then execute this skill's VIP/fee query workflow. - `SKILL.md` keeps intent routing and rendering rules. - `references/mcp.md` is the authoritative MCP execution layer for account/fee data retrieval and safe output behavior. ## Quick Start Below are the most common prompts to get started quickly: 1. **Query VIP tier** > What is my VIP level? 2. **Query trading fees** > Show me the spot and futures trading fees. 3. **Query VIP tier and fees together** > Check my VIP level and trading fees. ## Domain Knowledge ### Tool Mapping by Domain | Group | Tool Calls | |-------|------------| | Account / VIP tier | `cex_account_get_account_detail` | | Trading fee rates | `cex_wallet_get_wallet_fee` | ### Key Concepts - **VIP Tier**: Gate assigns VIP levels (VIP 0 – VIP 16) based on trading volume and asset holdings. Higher VIP tiers unlock lower fee rates. - **Spot Fee**: The maker/taker fee rate applied to spot trading pairs. - **Futures Fee**: The maker/taker fee rate applied to futures/contract trading, differentiated by settlement currency (BTC, USDT, USD). - 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. ### API Behavior Notes - **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. - **`settle` parameter scope**: The `settle` parameter only affects futures fee fields (`futuresMakerFee` / `futuresTakerFee`). Spot fees (`makerFee` / `takerFee`) remain unchanged regardless of `settle`. - **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. ## Workflow When the user asks about VIP tier or trading fees, follow this sequence. ### Step 1: Identify Query Type Classify the request into one of these categories: 1. **VIP tier query** — user wants to know their current VIP level 2. **Fee rate query** — user wants to know spot and/or futures trading fee rates 3. **Combined query** — user wants both VIP tier and fee information Key data to extract: - `query_type`: "vip", "fee", or "combined" - `currency_pair` (optional): specific trading pair for fee lookup - `settle` (optional): futures settlement currency (BTC / USDT / USD) ### Step 2: Query VIP Tier (if needed) If `query_type` is "vip" or "combined": Call `cex_account_get_account_detail` with: - No parameters required Key data to extract: - `vip_level`: the user's current VIP tier (e.g., VIP 0, VIP 1, etc.) ### Step 3: Query Trading Fee Rates (if needed) If `query_type` is "fee" or "combined": Call `cex_wallet_get_wallet_fee` with: - `currency_pair` (optional): specify trading pair context (note: fee rates are account-level and do not vary by pair) - `settle` (optional): futures settlement currency — affects futures fee fields only Key data to extract: - `maker_fee_rate`: spot maker fee rate - `taker_fee_rate`: spot taker fee rate - `futures_maker_fee_rate`: futures maker fee rate - `futures_taker_fee_rate`: futures taker fee rate ### Step 4: Return Result Format 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: - If user asked about **spot fees only** → show only `makerFee` / `takerFee` - If user asked about **futures/contract fees only** → show only `futuresMakerFee` / `futuresTakerFee` - If user asked about **trading fees** (general) → show both spot and futures - If user asked about **VIP only** → show only VIP level, no fee data - 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." Key data to extract: - VIP level (if queried) - Spot maker/taker fee rates (if queried) - Futures maker/taker fee rates (if queried) ## Judgment Logic Summary | Condition | Action | |-----------|--------| | User asks about VIP tier/level only | Call `cex_account_get_account_detail`, return VIP level | | User asks about trading fees only | Call `cex_wallet_get_wallet_fee`, return spot and futures fee rates | | User asks about both VIP and fees | Call both tools, return combined result | | User specifies a trading pair | Pass `currency_pair` parameter to `cex_wallet_get_wallet_fee` | | User specifies futures settlement currency | Pass `settle` parameter to `cex_wallet_get_wallet_fee` | | User asks about spot fees only | Call `cex_wallet_get_wallet_fee`, return only spot fee portion | | User asks about futures/contract fees only | Call `cex_wallet_get_wallet_fee` with `settle` parameter, return only futures fee portion | | 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 | | API returns error or empty data | Inform user of the issue and suggest checking account authentication | ## Report Template ```markdown ## Query Result {vip_section} {fee_section} ``` **VIP Section** (when VIP is queried): ```markdown ### VIP Tier | Item | Value | |------|-------| | VIP Level | {vip_level} | ``` **Fee Section** (when fees are queried): ```markdown ### Trading Fee Rates | Category | Maker Fee | Taker Fee | |----------|-----------|-----------| | Spot | {spot_maker_fee} | {spot_taker_fee} | | Futures | {futures_maker_fee} | {futures_taker_fee} | ``` **Combined example output**: ```markdown ## Query Result ### VIP Tier | Item | Value | |------|-------| | VIP Level | VIP 1 | ### Trading Fee Rates | Category | Maker Fee | Taker Fee | |----------|-----------|-----------| | Spot | 0.1% | 0.1% | | Futures (USDT) | 0.015% | 0.05% | ``` ## Error Handling | Error Type | Typical Cause | Handling Strategy | |------------|---------------|-------------------| | Authentication failure | API key invalid or expired | Inform user to check MCP configuration and API key validity | | Empty response | Account data not available | Inform user the query returned no data and suggest retrying | | Network error | MCP connection issue | Suggest user check MCP server connectivity | ## Safety Rules - This Skill is read-only and does not perform any trading or account modification operations. - No user confirmation is required since all operations are queries only. - Never expose raw API keys or sensitive authentication details in responses.

path: CHANGELOG.md
content: # Changelog

## [2026.3.11-2] - 2026-03-11

### Added
- `API Behavior Notes` section in Domain Knowledge: account-level pricing, settle parameter scope, invalid currency_pair handling

### Changed
- Step 3: clarified `currency_pair` parameter description (fee rates are account-level, not pair-specific)

## [2026.3.11-1] - 2026-03-11

### Added
- Initial version with VIP tier query via `cex_account_get_account_detail`
- Trading fee rate query (spot and futures) via `cex_wallet_get_wallet_fee`
- Support for combined VIP + fee queries
- Standard architecture with complete Workflow, Judgment Logic Summary, and Report Template


path: README.md
content: # Gate VIP & Fee Query Skill

## Overview

`gate-exchange-vipfee` is a read-only query Skill that helps users quickly check their Gate VIP tier and trading fee rates (spot and futures). It leverages Gate MCP tools to retrieve account profile and fee rate data, presenting results in a clean, structured format.

### Core Capabilities

| Capability | Description | MCP Tool |
|------------|-------------|----------|
| VIP Tier Query | Query the user's current VIP level | `cex_account_get_account_detail` |
| Trading Fee Query | Query spot and futures maker/taker fee rates | `cex_wallet_get_wallet_fee` |
| Combined Query | Return both VIP tier and fee rates in one response | Both tools |

## Architecture

This Skill uses the **Standard Architecture** (single-function, all logic in one SKILL.md).

```
gate-exchange-vipfee/
├── SKILL.md                    # AI Agent runtime instructions
├── README.md                   # Human-readable documentation
├── CHANGELOG.md                # Version changelog
└── references/
    └── scenarios.md            # Usage scenarios and prompt examples
```

### Workflow Summary

```
User Request
    ↓
Step 1: Identify query type (VIP / Fee / Combined)
    ↓
Step 2: Query VIP tier via cex_account_get_account_detail (if needed)
    ↓
Step 3: Query fee rates via cex_wallet_get_wallet_fee (if needed)
    ↓
Step 4: Format and return result
```

## Usage

Trigger this Skill with prompts such as:

- "What is my VIP level?"
- "Check my trading fees"
- "Show me the spot and futures fees"
- "What is my VIP level and fee rate?"

## MCP Tools

| Tool | Purpose | Auth Required |
|------|---------|---------------|
| `cex_account_get_account_detail` | Get account profile including VIP tier | Yes |
| `cex_wallet_get_wallet_fee` | Get spot and futures trading fee rates | Yes |

## Authentication

This skill does **not** handle credentials directly. Authentication is managed by the Gate MCP platform layer — the MCP server holds the user's API key and injects it into API calls automatically. No environment variables or secrets are required by the skill itself. Users should configure their Gate API key in the MCP server settings (see [Gate MCP](https://github.com/gateio/gate-mcp) for setup instructions).

## Source

- **Repository**: [github.com/gate/gate-skills](https://github.com/gate/gate-skills)
- **Publisher**: [Gate.com](https://www.gate.com)


path: references/mcp.md
content: ---
name: gate-exchange-vipfee-mcp
version: "2026.3.30-1"
updated: "2026-03-30"
description: "MCP execution specification for VIP tier and trading fee queries on Gate Exchange."
---

# Gate VIP Fee MCP Specification

## 1. Scope and Trigger Boundaries

In scope:
- Query user VIP level/account detail
- Query spot/futures fee rates

Out of scope:
- Any order placement or account mutation

## 2. MCP Detection and Fallback

Detection:
1. Verify Gate MCP exposes `cex_account_get_account_detail` and `cex_wallet_get_wallet_fee`.
2. Probe with account detail query.

Fallback:
- If MCP unavailable/auth invalid, return setup/auth guidance.

## 3. Authentication

- API key required for user-specific fee data.

## 4. MCP Resources

No mandatory MCP resources.

## 5. Tool Calling Specification

| Tool | Purpose | Common errors |
|---|---|---|
| `cex_account_get_account_detail` | fetch VIP/account profile context | auth denied |
| `cex_wallet_get_wallet_fee` | fetch spot/futures fee rates | market/pair filter mismatch |

## 6. Execution SOP (Non-Skippable)

1. Determine query type (VIP level, fee rates, combined).
2. Call minimal required read tools.
3. Normalize fee rendering (maker/taker, spot/futures context).
4. Return structured summary.

## 7. Output Templates

```markdown
## VIP & Fee Summary
- VIP Level: {vip_level}
- Spot Fee: maker {spot_maker}, taker {spot_taker}
- Futures Fee: maker {fx_maker}, taker {fx_taker}
- Notes: {conditions_or_scope}
```

## 8. Safety and Degradation Rules

1. Keep values as returned by API; no fabricated discounts.
2. Distinguish spot and futures fee contexts clearly.
3. If unavailable for a market/pair, mark as unavailable instead of defaulting.
4. This skill is read-only.
5. Preserve timestamp/context when fee values are queried for specific pairs.


path: references/scenarios.md
content: # Scenarios

## Scenario 1: Query VIP Tier

**Context**: User wants to check their current Gate VIP level.

**Prompt Examples**:
- "What is my VIP level?"
- "Check my VIP tier"
- "Show me my current VIP level"
- "Which VIP tier am I on?"

**Expected Behavior**:
1. Identify query type as "vip"
2. Call `cex_account_get_account_detail` to retrieve account profile
3. Extract VIP level from the response
4. Return VIP tier in the Report Template format

## Scenario 2: Query Trading Fee Rates

**Context**: User wants to know their current spot and futures trading fee rates.

**Prompt Examples**:
- "What are my trading fees?"
- "Check my fee rates"
- "Show me the spot and futures fees"
- "What are my maker and taker fees?"

**Expected Behavior**:
1. Identify query type as "fee"
2. Call `cex_wallet_get_wallet_fee` to retrieve fee rate data
3. Extract spot maker/taker fee and futures maker/taker fee
4. Return fee rates in the Report Template format with spot and futures categories

## Scenario 3: Query Both VIP Tier and Fee Rates

**Context**: User wants to know both their VIP level and trading fee rates in a single query.

**Prompt Examples**:
- "Check my VIP level and trading fees"
- "What is my VIP tier and fee rate?"
- "Show me my VIP level and trading fees"
- "Show my account tier and fee info"

**Expected Behavior**:
1. Identify query type as "combined"
2. Call `cex_account_get_account_detail` to retrieve VIP tier
3. Call `cex_wallet_get_wallet_fee` to retrieve fee rates
4. Return combined result with both VIP tier and fee rate sections

## Scenario 4: Query Fee for Specific Trading Pair

**Context**: User wants to check the fee rate for a specific trading pair.

**Prompt Examples**:
- "What is the fee for BTC_USDT?"
- "Check the fee rate for ETH_USDT"
- "Show me the trading fee for BTC_USDT"

**Expected Behavior**:
1. Identify query type as "fee" with `currency_pair` parameter
2. Call `cex_wallet_get_wallet_fee` with `currency_pair` set to the specified pair
3. Extract fee rates for the specified pair
4. Return fee rates in the Report Template format

## Scenario 5: Query Futures Fee by Settlement Currency

**Context**: User specifically asks about futures/contract fee rates for a particular settlement currency.

**Prompt Examples**:
- "What are my USDT-settled futures fees?"
- "Check the BTC-settled contract fees"
- "Show me the futures fees for USDT settlement"

**Expected Behavior**:
1. Identify query type as "fee" with `settle` parameter
2. Call `cex_wallet_get_wallet_fee` with `settle` set to the specified currency (BTC / USDT / USD)
3. Extract futures maker/taker fee rates
4. Return futures fee rates in the Report Template format


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)