Gate Dex Trade

Auto-Update (Session Start Only)

On session start (not during interactions), check for updates once:

1. Read this file's frontmatter version and updated fields.
2. Fetch remote SKILL.md from https://raw.githubusercontent.com/gateio/web3_wallet_skill/master/skills/gate-dex-trade/SKILL.md.
3. Compare: update if remote version > local version, or same version but remote updated date is newer.
4. On update: fetch and overwrite all skill files (SKILL.md, README.md, CHANGELOG.md, install.sh, references/mcp.md, references/openapi.md).
5. On failure: silently continue — never block user interactions.
6. Skip if: already checked this session, or skill was installed < 24h ago.

Routing Flow

User triggers trading intent
  ↓
Step 1: Has user explicitly specified a mode?
  ├─ Explicitly mentions "OpenAPI" / "AK/SK" / "API Key" → OpenAPI mode
  ├─ Otherwise → MCP only (Step 2)
  └─ Not specified → Step 2
  ↓
Step 2: Is this a cross-chain swap?
  ├─ Cross-chain → Must use MCP mode (OpenAPI doesn't support cross-chain), proceed to Step 3
  └─ Same-chain / uncertain → Step 3
  ↓
Step 3: Gate Wallet MCP Server Discovery & Detection
  a) Scan configured MCP Server list for Servers providing both `dex_tx_quote` and `dex_tx_swap` tools
  b) If found → Record server identifier, verify with:
     CallMcpTool(server="<identifier>", toolName="dex_chain_config", arguments={chain: "ETH"})
     ├─ Success → MCP mode
     └─ Failed → Step 4
  c) No matching Server → Step 4
  ↓
Step 4: MCP unavailable → setup guide only (`references/setup.md`), no OpenAPI fallback

Mode Dispatch

MCP Mode

Read and strictly follow references/mcp.md, execute according to its complete workflow.

Includes: connection detection, authentication (mcp_token), MCP Resource/tool calls (dex_tx_quote / dex_tx_swap / dex_tx_swap_detail), token address resolution, native_in/native_out rules, three-step confirmation gateway (SOP), quote templates, risk warnings, cross-Skill collaboration, security rules.

OpenAPI Mode (Progressive Loading)

Default off in this workspace — explicit OpenAPI request only.

Limitation: OpenAPI mode only supports same-chain Swap, does not support cross-chain exchanges.

Load files progressively — only load what the current step needs:

1. Always load first: references/openapi/_shared.md — env detection, credentials, API call method (via helper script)
2. Then load based on swap stage:

3. On error: references/openapi/errors.md

Legacy monolithic file preserved at references/openapi.md for backward compatibility.

MCP Server Setup Guide

When MCP detection fails and a setup guide is needed, read and display references/setup.md. Show only the configuration for the user's current platform when identifiable. Display at most once per session.

Supported Chains

Actual supported chains are determined by runtime API/Resource returns:

• MCP Mode: swap://supported_chains Resource
• OpenAPI Mode: trade.swap.chain interface

For uncommon chains: MCP calls dex_chain_config, OpenAPI calls trade.swap.chain.

Cross-Skill Collaboration

Security Rules

1. Mode selection transparency: Clearly inform users of the current mode and reasons
2. Authentication isolation: MCP uses mcp_token, OpenAPI uses AK/SK — never mix
3. Three-step confirmation gateway: Trading pair confirmation → quote display → signature authorization — cannot be skipped
4. Balance pre-check: Mandatory verification of asset and Gas token sufficiency before trading
5. Risk warnings: Forced warning for exchange value difference > 5%, high slippage (> 5%) MEV attack warnings
6. No OpenAPI fallback when MCP fails (this project)
7. No repeated guidance: MCP setup guide displayed at most once per session