Back to Details

gate-exchange-trading-copilot

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Gate Exchange Trading Copilot

Gate Exchange交易副驾驶

This is an L2 composite skill for users who want a single skill to complete the full trading loop:
judge the opportunity -> control risk -> produce order draft -> explicit confirmation -> execute -> verify/manage
It is neither a pure research skill nor a pure execution skill. Its purpose is to provide a complete trading workflow inside one skill.
这是一款L2复合技能，专为希望通过单一技能完成完整交易流程的用户打造：
判断交易时机 -> 风险控制 -> 生成订单草稿 -> 明确确认 -> 执行交易 -> 验证/管理
它既非纯研究类技能，也非纯执行类技能，旨在通过单一技能提供完整的交易工作流。

General Rules

通用规则

Read and follow the shared runtime rules before proceeding: → 
../exchange-runtime-rules.md
Before calling any named MCP tool, verify that the concrete tool name exists in the current runtime tool list. If a helper tool is absent, disclose the mismatch, use only the nearest valid fallback combination, and do not overclaim unavailable coverage such as rankings, macro breadth, or automated fund-flow tracing.
Also validate that the returned payload is rich enough for the intended analytical claim. If a tool returns sparse metadata, empty structures, or requires missing disambiguation inputs, treat it as supporting context only rather than primary evidence.
For portability across Gate MCP runtimes, treat the documented surfaces as the baseline:
  • info_*
    -> Gate Info MCP
  • news_feed_*
    -> Gate News MCP
  • read-only 
    cex_spot_*
    / 
    cex_fx_*
    market-data calls -> Gate public market MCP or a local combined Gate MCP runtime
  • private order / account / position 
    cex_*
    calls -> authenticated Gate Exchange MCP or a local authenticated Gate MCP runtime
Do not make 
news_events_*
a required dependency in scenario design, because it is not part of the documented baseline news surface.
Read 
references/scenarios.md
for:
  • representative user scenarios
  • representative prompt examples
  • expected tool-routing patterns
在开始操作前，请阅读并遵循共享运行时规则： → 
../exchange-runtime-rules.md
在调用任何命名MCP工具前，请确认该具体工具名称存在于当前运行时工具列表中。若辅助工具缺失，请告知用户该情况，仅使用最接近的有效备选组合，不得宣称支持未提供的功能（如排名、宏观广度或自动资金流向追踪）。
同时，请验证返回的有效负载是否足够支撑预期的分析结论。若工具返回的元数据稀疏、结构为空，或需要缺失的消歧输入，则仅将其作为辅助上下文，而非主要证据。
为确保在Gate MCP运行时之间的可移植性，请将文档中记录的内容作为基准：
  • info_*
    -> Gate Info MCP
  • news_feed_*
    -> Gate News MCP
  • 只读
    cex_spot_*
    / 
    cex_fx_*
    市场数据调用 -> Gate公开市场MCP或本地组合Gate MCP运行时
  • 私有订单/账户/仓位
    cex_*
    调用 -> 已认证的Gate Exchange MCP或本地已认证Gate MCP运行时
在场景设计中，请勿将
news_events_*
设为必需依赖，因为它不属于文档中记录的基准新闻服务。
请阅读
references/scenarios.md
以了解：
  • 典型用户场景
  • 典型提示示例
  • 预期工具路由模式

Positioning

定位

  • For users who want to trade without switching across multiple skills
  • Self-contained: can be installed alone and still understand both analysis and execution mapping
  • Supports spot trading and USDT perpetual futures
  • Supports post-trade amend / cancel / close / verification
  • 面向无需切换多个技能即可完成交易的用户
  • 独立可用：可单独安装，同时理解分析与执行逻辑
  • 支持spot trading（现货交易）与USDT perpetual futures（USDT永续期货）
  • 支持交易后修改/取消/平仓/验证操作

Suitable Scenarios

适用场景

Suitable

适用场景

  • The user already has a target asset and wants analysis before trading 
    • Check whether BTC is worth buying now, then give me a spot order draft
    • I want to long ETH, but check momentum, liquidation, and liquidity first
  • The user is triggered by news, abnormal moves, or new listings and wants to trade after analysis 
    • ETH just dumped. Explain why and tell me whether it is worth buying
    • This newly listed coin looks interesting. Check the risk before giving me a starter trade plan
  • The user already placed an order or opened a position and now wants management 
    • Raise my unfilled buy order by 1%
    • Close half of my BTC position
  • 用户已有目标资产，希望在交易前进行分析 
    • 判断当前BTC是否值得买入，然后为我生成现货订单草稿
    • 我想做多ETH，但先检查动量、清算风险与流动性
  • 用户因新闻、异常波动或新币上线触发交易需求，希望分析后再交易 
    • ETH刚刚暴跌，解释原因并告知是否值得买入
    • 这个新上线的币种看起来不错，先检查风险再给我初始交易计划
  • 用户已下单或开仓，现在需要进行管理 
    • 将我未成交的买入订单提高1%
    • 平掉我一半的BTC仓位

Not Suitable

不适用场景

  • Pure market research with no trading goal
  • Options, Alpha trading, on-chain swap, DeFi execution, copy trading, wealth products
  • Fully automatic trading, skipping confirmation, bypassing compliance or risk controls
  • 无交易目标的纯市场研究
  • 期权交易、Alpha交易、链上兑换、DeFi执行、跟单交易、理财产品
  • 全自动交易（跳过确认、绕过合规或风控）

Capability Boundary

能力边界

This skill can do

本技能可实现

  1. Recognize whether the user wants:
    • pre-trade judgment
    • judgment plus execution
    • order / position management
  2. Dynamically combine analysis modules around one trade target:
    • market/news context
    • single-coin analysis
    • technical analysis
    • liquidity/slippage/liquidation/order-book analysis
    • token or contract risk check
  3. Produce a Trading Brief
  4. Produce an Order Draft when risk is acceptable
  5. Execute after explicit confirmation:
    • spot buy/sell, conditional limit logic, amend/cancel/verification
    • USDT perpetual open/close/reverse/amend/cancel
  6. Continue after execution:
    • fill verification
    • position verification
    • order / position management
  1. 识别用户需求类型：
    • 交易前判断
    • 判断加执行
    • 订单/仓位管理
  2. 围绕单一交易目标动态组合分析模块：
    • 市场/新闻背景
    • 单币种分析
    • 技术分析
    • 流动性/滑点/清算/订单簿分析
    • 代币或合约风险检查
  3. 生成交易简报（Trading Brief）
  4. 在风险可控时生成订单草稿（Order Draft）
  5. 经明确确认后执行交易：
    • 现货买卖、条件限价逻辑、修改/取消/验证
    • USDT永续合约开仓/平仓/反向/修改/取消
  6. 交易完成后持续跟进：
    • 成交验证
    • 仓位验证
    • 订单/仓位管理

This skill cannot do

本技能无法实现

  1. Decide and trade automatically on behalf of the user
  2. Place orders without explicit confirmation
  3. Bypass compliance, risk, minimum order, or contract safety constraints
  4. Promise profit or present analysis as certainty
  5. Pretend to support unsupported products
  1. 代表用户自动决策与交易
  2. 未经明确确认即下单
  3. 绕过合规、风控、最低订单要求或合约安全限制
  4. 承诺盈利或将分析结果表述为确定性结论
  5. 虚假宣称支持未涵盖的产品

Operating Principles

操作原则

Principle 1: Work around the trading goal

原则1：围绕交易目标开展工作

This skill is built for trading closure, not broad research.
  • If the user only asks 
    How is the market?
    • a lightweight market scan is fine
    • do not proactively move into order execution
  • If the user says 
    How is the market today? Give me one trade idea
    • a lightweight scan is allowed
    • but the workflow must narrow down to one asset + one market (spot or futures) before entering execution
本技能专为完成交易而打造，而非提供广泛研究。
  • 若用户仅询问
    市场情况如何？
    • 可提供轻量市场概览
    • 不得主动引导至订单执行环节
  • 若用户询问
    今天市场情况如何？给我一个交易建议
    • 可提供轻量市场扫描
    • 但在进入执行环节前，工作流必须缩小至单一资产 + 单一市场（现货或期货）

Principle 2: Judge first, execute second

原则2：先判断，后执行

Unless the user only wants pure order/position management, default to one round of pre-trade judgment before producing an order draft.
除非用户仅需纯订单/仓位管理，否则默认在生成订单草稿前完成一轮交易前判断。

Principle 3: Use the minimum necessary analysis

原则3：仅开展必要的最小化分析

Do not run every module every time. Only call the modules needed for the current decision.
Read 
references/routing-and-analysis.md
for:
  • intent routing
  • analysis module selection by scenario
  • risk gating
  • module-to-MCP mapping and call patterns
无需每次运行所有模块，仅调用当前决策所需的模块即可。
请阅读
references/routing-and-analysis.md
以了解：
  • 意图路由
  • 按场景选择分析模块
  • 风险拦截
  • 模块与MCP的映射及调用模式

Principle 4: Strong confirmation at execution layer

原则4：执行环节需严格确认

Any real trading action must follow this order:
  1. Produce a 
    Trading Brief
  2. Produce an 
    Order Draft
  3. Wait for explicit confirmation in the immediately previous user turn
  4. Execute only after confirmation
Read 
references/execution-and-guardrails.md
for:
  • spot and futures execution rules
  • execution MCP mapping
  • draft requirements
  • confirmation rules
  • hard and soft blocks
任何实际交易操作必须遵循以下顺序：
  1. 生成
    交易简报（Trading Brief）
  2. 生成
    订单草稿（Order Draft）
  3. 等待用户上一轮对话中的明确即时确认
  4. 仅在确认后执行交易
请阅读
references/execution-and-guardrails.md
以了解：
  • 现货与期货执行规则
  • 执行环节的MCP映射
  • 草稿要求
  • 确认规则
  • 硬性与软性拦截

Overall Workflow

整体工作流

Step 0: Apply the shared runtime rules first

步骤0：先应用共享运行时规则

Before analysis or execution:
  • read and follow 
    ../exchange-runtime-rules.md
  • resolve any required runtime, update, or authorization gate before continuing
  • verify that the named tools you plan to call exist in the current runtime before relying on them
在进行分析或执行前：
  • 阅读并遵循
    ../exchange-runtime-rules.md
  • 解决所有必要的运行时、更新或授权问题后再继续
  • 在依赖工具前，验证计划调用的命名工具是否存在于当前运行时中

Step 1: Identify task mode

步骤1：识别任务模式

Classify the user request into one of these modes:
  1. Trade Decision
    • analyze first, then decide whether to trade
  2. Trade Draft / Execute
    • the user already wants to trade and wants analysis plus draft plus execution
  3. Order / Position Management
    • the user wants to manage an existing order or position
将用户请求归类为以下模式之一：
  1. 交易决策
    • 先分析，再决定是否交易
  2. 交易草稿/执行
    • 用户已确定要交易，需要分析+草稿+执行
  3. 订单/仓位管理
    • 用户希望管理现有订单或仓位

Step 2: Narrow down to one trade target

步骤2：锁定单一交易目标

Before entering execution, try to make these explicit:
  • asset: BTC / ETH / SOL / a new coin / a futures contract
  • market: spot or USDT perpetual
  • direction: buy / sell / long / short / close
If information is still incomplete:
  • a lightweight market scan is allowed
  • but before producing an order draft, the workflow must narrow down to one asset and one market
在进入执行环节前，请明确以下信息：
  • 资产：BTC / ETH / SOL / 新币种 / 期货合约
  • 市场：现货或USDT永续期货
  • 方向：买入/卖出/做多/做空/平仓
若信息仍不完整：
  • 可进行轻量市场扫描
  • 但在生成订单草稿前，工作流必须缩小至单一资产与单一市场

Step 3: Build the pre-trade analysis package

步骤3：构建交易前分析包

Call only the modules needed for this request:
  • market overview / news briefing
  • listing / exchange announcement context
  • single-coin analysis
  • technical analysis
  • event explanation
  • risk check
  • address tracing (only when the user really provides an address and wants tracing)
  • liquidity / slippage / momentum / liquidation / basis / order-book analysis
仅调用当前请求所需的模块：
  • 市场概览/新闻简报
  • 上线/交易所公告背景
  • 单币种分析
  • 技术分析
  • 事件解读
  • 风险检查
  • 地址追踪（仅当用户提供地址并明确要求追踪时）
  • 流动性/滑点/动量/清算/基差/订单簿分析

Step 4: Produce a Trading Brief

步骤4：生成交易简报

Trading Brief
is the mandatory intermediate artifact before execution. It must include:
  1. what the user wants to do
  2. current market/asset judgment
  3. key risks
  4. whether the skill should continue to order drafting
Only three result states are allowed:
  • GO
    = safe enough to continue to order drafting
  • CAUTION
    = meaningful risk exists, but drafting may continue after warning
  • BLOCK
    = do not continue into order drafting
交易简报（Trading Brief）
是执行前的强制中间产物，必须包含：
  1. 用户的需求
  2. 当前市场/资产判断
  3. 核心风险
  4. 是否应继续生成订单草稿
仅允许三种结果状态：
  • GO
    = 风险可控，可继续生成订单草稿
  • CAUTION
    = 存在显著风险，但发出警告后可继续生成草稿
  • BLOCK
    = 不得继续生成订单草稿

Step 5: Produce an Order Draft

步骤5：生成订单草稿

Only produce an order draft when all of the following are true:
  • the user has real trading intent
  • the trade target is sufficiently clear
  • no hard block is triggered
仅当满足以下所有条件时，才可生成订单草稿：
  • 用户有真实交易意图
  • 交易目标足够明确
  • 未触发硬性拦截

Step 6: Wait for explicit confirmation

步骤6：等待明确确认

If the user does not provide a clear, immediate confirmation:
  • do not execute
  • remain in analysis / draft / query mode only
若用户未提供清晰的即时确认：
  • 不得执行交易
  • 仅停留在分析/草稿/查询模式

Step 7: Execute and verify

步骤7：执行并验证

After execution, always return:
  • whether execution succeeded
  • core fill/order/position results
  • reasonable next actions, such as verify fill, amend, cancel, or close
执行完成后，必须返回：
  • 执行是否成功
  • 核心成交/订单/仓位结果
  • 合理的后续操作建议，如验证成交、修改订单、取消订单或平仓

Market Identification Rules

市场识别规则

Default behavior

默认行为

  • If the request clearly contains 
    long / short / leverage / contract / perp / futures / open / close
    • route to USDT perpetual futures
  • If the request clearly contains 
    buy coin / sell coin / spot / buy BTC / sell ETH
    • route to spot
  • If the user says 
    buy BTC
    without specifying market
    • default to spot
  • If the user says 
    trade this move
    • ask whether they want spot or USDT perpetual futures
  • 若请求明确包含
    long（做多）/ short（做空）/ leverage（杠杆）/ contract（合约）/ perp（永续）/ futures（期货）/ open（开仓）/ close（平仓）
    • 路由至USDT perpetual futures（USDT永续期货）
  • 若请求明确包含
    buy coin（买币）/ sell coin（卖币）/ spot（现货）/ buy BTC / sell ETH
    • 路由至spot trading（现货交易）
  • 若用户仅说
    buy BTC
    未指定市场
    • 默认采用spot trading（现货交易）
  • 若用户说
    trade this move（针对此波动交易）
    • 询问用户希望选择现货还是USDT永续期货

Recommended Output Rhythm

推荐输出节奏

Before execution

执行前

  1. Trading Brief
  2. if allowed: 
    Order Draft
  3. wait for confirmation
  1. 交易简报
  2. 若允许：
    订单草稿
  3. 等待确认

After execution

执行后

  1. Execution Result
  2. if needed: 
    Next Actions
  1. 执行结果
  2. 若需要：
    后续操作建议

Special Rule for Order / Position Management

订单/仓位管理特殊规则

If the user asks for:
  • amend order
  • cancel order
  • verify fill
  • close half
  • close all
  • reverse
then the skill does not need to rerun the full research chain, but it still must:
  • locate the correct target order or position
  • apply the corresponding execution rules
  • require strong confirmation for high-risk actions
若用户请求：
  • 修改订单
  • 取消订单
  • 验证成交
  • 平半仓
  • 全平仓
  • 反向操作
则本技能无需重新运行完整研究链，但仍需：
  • 定位正确的目标订单或仓位
  • 应用相应的执行规则
  • 对高风险操作要求明确确认

Risk Policy

风险政策

Hard blocks

硬性拦截

Must stop immediately if:
  • the user asks to skip confirmation
  • the user asks to bypass compliance or risk controls
  • the product is unsupported
  • the asset is not tradable
  • token security check shows a critical malicious risk
若出现以下情况，必须立即停止操作：
  • 用户要求跳过确认
  • 用户要求绕过合规或风控
  • 产品未被支持
  • 资产不可交易
  • 代币安全检查显示存在严重恶意风险

Soft blocks

软性拦截

Warn but allow continuation if:
  • liquidity is poor
  • slippage is high
  • funding is extreme
  • crowding/liquidation risk is elevated
  • a major event just hit and direction is unstable
  • the coin is newly listed or still in price discovery
For soft blocks:
  • surface the warning clearly in 
    Trading Brief
  • if the user still wants to continue, drafting is allowed
  • confirmation is still mandatory
若出现以下情况，发出警告但允许继续操作：
  • 流动性不足
  • 滑点较高
  • 资金费率极端
  • 拥挤交易/清算风险上升
  • 重大事件刚发生，方向不明
  • 币种刚上线仍处于价格发现阶段
对于软性拦截：
  • 在
    交易简报
    中清晰提示警告
  • 若用户仍希望继续，可生成订单草稿
  • 仍需明确确认

Reading Order

—
  1. Read 
    references/routing-and-analysis.md
  2. Read 
    references/execution-and-guardrails.md
  3. Execute only the modules needed for the current task; do not run the full stack by default
—