Gate Alpha Assistant

This skill is the single entry for Gate Alpha operations. It supports seven modules: Token Discovery, Market Viewing, Trading (Buy), Trading (Sell), Account & Holdings, Account Book, and Order Management. User intent is routed to the matching workflow.

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_alpha_get_alpha_order
• cex_alpha_list_alpha_account_book
• cex_alpha_list_alpha_accounts
• cex_alpha_list_alpha_currencies
• cex_alpha_list_alpha_orders
• cex_alpha_list_alpha_tickers
• cex_alpha_list_alpha_tokens
• cex_alpha_quote_alpha_order

Execution Operations (Write)

• cex_alpha_place_alpha_order

Authentication

• API Key Required: Yes (see skill doc/runtime MCP deployment)
• Permissions: Alpha: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

MCP Mode

Read and strictly follow references/mcp.md, then execute module routing in this skill.

• SKILL.md keeps module dispatch and business boundaries.
• references/mcp.md is the authoritative MCP execution layer for quote->confirm->place order flow and post-order verification.

Module Overview

Routing Rules

MCP Tools

Domain Knowledge

Alpha Platform Overview

• Gate Alpha is a platform for early-stage token trading, supporting tokens across multiple blockchains.
• Tokens are identified by currency symbol (e.g., memeboxtrump) rather than standard ticker symbols.
• Trading status values: 1 = actively trading, 2 = suspended, 3 = delisted.

Supported Chains

solana, eth, bsc, base, world, sui, arbitrum, avalanche, polygon, linea, optimism, zksync, gatelayer

Note: Chain names may be returned in different cases depending on the endpoint (e.g., SOLANA vs solana). Normalize to lowercase when comparing.

Supported Launch Platforms

meteora_dbc, fourmeme, moonshot, pump, raydium_launchlab, letsbonk, gatefun, virtuals

Trading Mechanics

• Buy amount: USDT quantity (e.g., amount="5" means spend 5 USDT).
• Sell amount: Token quantity (e.g., amount="1000" means sell 1000 tokens).
• Quote validity: quote_id from cex_alpha_quote_alpha_order expires after 1 minute. Re-quote if expired.
• Gas modes: Input "speed" (default) or "custom" (with slippage). API returns gasMode as "1" (speed) or "2" (custom).
• Order statuses: 1 = Processing, 2 = Success, 3 = Failed, 4 = Cancelled, 5 = Transferring, 6 = Cancelling transfer. Terminal statuses: 2, 3, 4.

API Field Naming Conventions

All API endpoints use snake_case naming. Key fields by endpoint:

• /alpha/currencies: currency, name, chain, address, amount_precision, precision, status
• /alpha/tickers: currency, last, change, volume, market_cap
• /alpha/accounts: currency, available, locked, token_address, chain
• /alpha/account_book: id, time, currency, change, balance
• /alpha/orders (GET): order_id, tx_hash, side, usdt_amount, currency, currency_amount, status, gas_mode, chain, gas_fee, transaction_fee, create_time, failed_reason
• Empty query results may return [{}, {}] (array with empty objects) instead of []. Check for valid fields before processing.

Key Constraints

• All market data endpoints (currencies, tickers, tokens) are public and do not require authentication.
• Account, trading, and order endpoints require API Key authentication.
• Pagination: use page and limit parameters for large result sets.
• Rate limits: quote 10r/s, place order 5r/s, other endpoints 200r/10s.

Execution

1. Intent Classification

Classify the user request into one of seven modules: Token Discovery, Market Viewing, Trading (Buy), Trading (Sell), Account & Holdings, Account Book, or Order Management.

2. Route and Load

Load the corresponding reference document and follow its workflow.

3. Return Result

Return the result using the report template defined in each sub-module.

Error Handling

Safety Rules

• Order confirmation: NEVER place a buy or sell order without showing the quote details and receiving explicit user confirmation.
• Token validation: Always verify status=1 before initiating a trade. Abort if suspended or delisted.
• Balance verification: Before selling, always confirm available >= sell_amount. Report actual balance if insufficient.
• Quote freshness: Always check quote_id validity (1-minute window). Re-quote if the user delays confirmation.
• Never fabricate token data. If a query returns empty results, report it honestly.
• When displaying token addresses, show the full address to avoid confusion between similarly named tokens.
• Always verify trading status before suggesting a token is tradable.