Gate Exchange Welfare Center
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 ./references/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)
- - cexwelfaregetbeginnertasklist
- cexwelfaregetuser_identity
Authentication
- - Credentials Source: Local Gate MCP deployment (
GATE_API_KEY, GATE_API_SECRET) - API Key Required: Yes
- Permissions: Welfare:Read
- Never ask the user to paste secrets into chat; rely on the configured MCP session only.
- API Key Provisioning Reference: https://www.gate.com/myaccount/profile/api-key/manage (create or rotate keys outside the chat when the local MCP setup requires them).
Installation Check
- - Required: Gate (main)
- Install: Use the local Gate MCP installation flow for the current host IDE before continuing.
- Continue only after the Gate MCP session is configured with the credentials listed above; do not switch to browser auth or ask the user to paste secrets into chat.
MCP Mode
Read and strictly follow references/mcp.md, then execute this skill's welfare workflow.
- -
SKILL.md keeps user-type routing, task-display semantics, and policy constraints. - INLINECODE5 is the authoritative MCP execution layer for identity gate, task query sequence, and fallback handling.
Overview
Welfare center new user task entry Skill (version 2026.3.18-6, with MCP tools integration). When users ask about benefits/rewards/tasks, first determine if they are new users. Show all new user onboarding task details for new users, guide existing users to official website or App.
Trigger Scenarios: Execute this Skill when users mention welfare benefits, new user rewards, task claiming, reward claiming and other related keywords.
Domain Knowledge
New User Definition
- - New User (code=0): Newly registered users who have not completed any trading activities, deposits, or other engagement tasks
- Existing User (code=1001): Users with trading history, completed tasks, or established account activity
User Status Categories
- - Normal Users: Can participate in all new user activities and claim rewards
- Risk Control Users (code=1002): Temporarily restricted from participating in activities due to security concerns
- Sub-accounts (code=1003): Cannot participate; must use main account
- Agent Users (code=1004): Excluded from new user welfare programs
- Market Makers (code=1005): Professional traders excluded from new user benefits
- Enterprise Users (code=1006): Corporate accounts excluded from individual user benefits
- Not Logged In (code=1008): Must authenticate before accessing welfare information
Task Types
- - Registration Tasks (type=10): Basic onboarding activities like app download, account setup
- Guidance Tasks (type=11): Progressive engagement tasks like KYC verification, first deposit, first trade
Reward Mechanisms
- - USDT Trial Vouchers: Practice trading credits for new users
- Bonus USDT: Real trading capital rewards
- Points: Loyalty program credits for redemption
- Task Completion: Sequential unlock of advanced features and higher rewards
Welfare Ecosystem
- - Centralized Hub: All welfare activities accessible via https://www.gate.com/rewards_hub
- Mobile Integration: Full feature parity in Gate mobile app
- Cross-platform Sync: Task progress and rewards synchronized across web and mobile
Routing Rules
| User Intent | Keywords / Patterns | Routing |
|---|
| Query welfare / rewards / tasks (general) | "what welfare", "how to claim rewards", "what tasks can I do", "welfare", "rewards" | Execute this Skill → Determine user type first |
| Query new user benefits / rewards |
"new user benefits", "how to claim new user rewards", "new user tasks", "new user benefits", "newbie rewards" | Execute this Skill → Determine user type first |
| Spot trading | "buy BTC", "sell ETH" | Route to
gate-exchange-spot |
| Asset query | "how much USDT do I have", "check balance" | Route to
gate-exchange-assets |
| Deposit | "how to deposit", "how to fund account" | Route to deposit related Skill |
Execution Workflow
Step 1: Determine User Identity
Call MCP tool to query whether the current user is a new user.
| Step | MCP Tool | Parameters | Data Retrieved |
|---|
| 1 | INLINECODE8 (User identity determination interface) | Automatically get current user identity | Returns code=0 (qualifies as new user) or error codes (1001=existing user, 1002=risk control, 1003=sub-account, 1004=agent, 1005=market maker, 1006=enterprise, 1008=not logged in) |
Enter corresponding branch based on returned result:
Case 1: Existing User Guidance
Trigger Condition: Step 1 determines user as existing user (cex_welfare_get_user_identity returns code=1001).
No additional MCP tool calls needed, directly output guidance text.
Output Template:
CODEBLOCK0
Case 2: New User Task List
Trigger Condition: Step 1 determines user as new user (cex_welfare_get_user_identity returns code=0).
Step 2: Get All New User Onboarding Tasks
| Step | MCP Tool | Parameters | Data Retrieved |
|---|
| 2 | INLINECODE11 (Query beginner guidance task list) | Automatically get current user tasks | Get beginner guidance task list, including registration tasks (type=10) and guidance tasks (type=11), each task contains reward information, completion status and task description |
Step 3: Generate Task List Response
Important Note: Must use real task data obtained from MCP interface in Step 2, absolutely cannot fabricate or use template example data!
Based on the real task data returned from Step 2, output to users in the following format:
- 1. Iterate through all tasks: For each task in the
data.tasks array returned by INLINECODE13 - Extract real fields: Use the task's real fields such as
task_name, task_desc, reward_num, reward_unit, INLINECODE18 - Status display:
status=1 shows "Pending", status=2 shows "Completed" - Format output: Strictly follow template format, but content must be real MCP data
Data mapping rules:
- - Task title: Use
task_name field - Task description: Use
task_desc field - Reward amount: Use
reward_num field - Reward unit: Use
reward_unit field - Completion status: Use
status field (1=Pending, 2=Completed)
Response Templates
Case 1 — Existing User Guidance
CODEBLOCK1
Case 2 — New User Task List
CODEBLOCK2
Example Output:
CODEBLOCK3
Exception Handling
| Exception Type | Handling Method |
|---|
| Existing user (code=1001) | Execute existing user guidance: Prompt to visit https://www.gate.com/rewards_hub |
| Risk control user (code=1002) |
Prompt: "Your account is temporarily unable to participate in new user activities, please contact customer service for details" |
| Sub-account (code=1003) | Prompt: "Sub-accounts cannot participate in new user activities, please log in with main account" |
| Agent user (code=1004) | Prompt: "Agent users cannot participate in new user activities" |
| Market maker (code=1005) | Prompt: "Market maker users cannot participate in new user activities" |
| Enterprise user (code=1006) | Prompt: "Enterprise users cannot participate in new user activities" |
| Not logged in (code=1008) | Prompt: "Please log in to your Gate account first before querying welfare tasks" |
| Unable to determine user type (interface timeout/exception) | Prompt: "Welfare information is temporarily unavailable, please try again later, or visit https://www.gate.com/rewards_hub directly" |
| New user task list is empty | Prompt: "No new user tasks available at the moment, please check later, or visit https://www.gate.com/rewards_hub for more benefits" |
| Interface returns other errors | Generic fallback: "Service is temporarily unavailable, please try again later" |
Cross-Skill Integration
| User Follow-up Intent | Routing Target |
|---|
| User wants to complete "First Deposit" task | Route to deposit / funding Skill |
| User wants to complete "First Trade" task |
Route to
gate-exchange-spot |
| User wants to complete "Identity Verification" task | Show guidance text: Go to Gate web or open Gate App to complete KYC |
| User asks about asset balance | Route to
gate-exchange-assets |
Safety Rules
- 1. Read-only queries: This Skill only queries task information, does not execute task claiming, reward distribution or other write operations.
- Identity verification prerequisite: Must complete user type determination first, must not show new user task list to existing users.
- Real data only: Strictly prohibit fabricating task information! Must use real data returned by MCP interface, must not use fake reward information from example templates (such as "10 points", "5 USDT trial voucher", etc.).
- Data integrity: All displayed task names, descriptions, reward amounts, reward units must come from real return values of
cex_welfare_get_beginner_task_list interface. - Disclaimer: Task information is subject to final display on Gate official website, data returned by this Skill is for reference only.
- Required prompt text: When displaying task rewards, must include the required prompt text as specified: "Non-agent, non-institutional users and users with normal account status can complete tasks and claim rewards. Specific tasks and rewards are subject to final display on Gate official website/App", must not be omitted.
Gate 福利中心
通用规则
⚠️ 注意——在继续操作前,您必须阅读并严格遵守共享运行时规则。
在阅读完所有规则之前,请勿选择或调用任何工具。这些规则具有最高优先级。
→ 请阅读 ./references/gate-runtime-rules.md
- - 仅调用本技能中明确列出的 MCP 工具。 即使 MCP 服务器中存在未在此处记录的工具,也不得调用。
MCP 依赖项
必需的 MCP 服务器
使用的 MCP 工具
查询操作(只读)
- - cexwelfaregetbeginnertasklist
- cexwelfaregetuser_identity
身份验证
- - 凭证来源:本地 Gate MCP 部署(GATEAPIKEY、GATEAPISECRET)
- 需要 API 密钥:是
- 权限:福利:读取
- 切勿要求用户在聊天中粘贴密钥;仅依赖已配置的 MCP 会话。
- API 密钥配置参考:https://www.gate.com/myaccount/profile/api-key/manage(当本地 MCP 设置需要时,在聊天之外创建或轮换密钥)。
安装检查
- - 必需:Gate(主)
- 安装:在继续之前,使用当前主机 IDE 的本地 Gate MCP 安装流程。
- 仅在 Gate MCP 会话配置了上述凭证后继续;请勿切换到浏览器身份验证或要求用户在聊天中粘贴密钥。
MCP 模式
阅读并严格遵守 references/mcp.md,然后执行本技能的福利工作流程。
- - SKILL.md 保留用户类型路由、任务显示语义和策略约束。
- references/mcp.md 是身份网关、任务查询序列和回退处理的权威 MCP 执行层。
概述
福利中心新用户任务入口技能(版本 2026.3.18-6,集成 MCP 工具)。当用户询问福利/奖励/任务时,首先判断其是否为新用户。向新用户显示所有新用户引导任务详情,引导现有用户前往官网或 App。
触发场景:当用户提及福利、新用户奖励、任务领取、奖励领取等相关关键词时,执行本技能。
领域知识
新用户定义
- - 新用户(code=0):新注册且未完成任何交易活动、充值或其他参与任务的用户
- 现有用户(code=1001):有交易历史、已完成任务或账户活动已建立的用户
用户状态分类
- - 正常用户:可参与所有新用户活动并领取奖励
- 风控用户(code=1002):因安全原因暂时限制参与活动
- 子账户(code=1003):无法参与;必须使用主账户
- 代理用户(code=1004):被排除在新用户福利计划之外
- 做市商(code=1005):专业交易者,被排除在新用户福利之外
- 企业用户(code=1006):企业账户,被排除在个人用户福利之外
- 未登录(code=1008):必须先进行身份验证才能访问福利信息
任务类型
- - 注册任务(type=10):基础引导活动,如 App 下载、账户设置
- 引导任务(type=11):渐进式参与任务,如 KYC 验证、首次充值、首次交易
奖励机制
- - USDT 体验券:新用户练习交易额度
- USDT 奖励金:真实交易资金奖励
- 积分:忠诚度计划积分,可用于兑换
- 任务完成:按顺序解锁高级功能和更高奖励
福利生态系统
- - 集中枢纽:所有福利活动均可通过 https://www.gate.com/rewards_hub 访问
- 移动端集成:Gate 移动 App 功能完全一致
- 跨平台同步:任务进度和奖励在网页端和移动端同步
路由规则
| 用户意图 | 关键词/模式 | 路由 |
|---|
| 查询福利/奖励/任务(通用) | 有什么福利、如何领取奖励、我可以做什么任务、福利、奖励 | 执行本技能 → 首先判断用户类型 |
| 查询新用户福利/奖励 |
新用户福利、如何领取新用户奖励、新用户任务、新手福利、新手奖励 | 执行本技能 → 首先判断用户类型 |
| 现货交易 | 购买 BTC、卖出 ETH | 路由至 gate-exchange-spot |
| 资产查询 | 我有多少 USDT、查看余额 | 路由至 gate-exchange-assets |
| 充值 | 如何充值、如何入金 | 路由至充值相关技能 |
执行工作流程
步骤 1:判断用户身份
调用 MCP 工具查询当前用户是否为新用户。
| 步骤 | MCP 工具 | 参数 | 获取的数据 |
|---|
| 1 | cexwelfaregetuseridentity(用户身份判断接口) | 自动获取当前用户身份 | 返回 code=0(符合新用户条件)或错误码(1001=现有用户、1002=风控、1003=子账户、1004=代理、1005=做市商、1006=企业、1008=未登录) |
根据返回结果进入对应分支:
案例 1:现有用户引导
触发条件:步骤 1 判断用户为现有用户(cexwelfaregetuseridentity 返回 code=1001)。
无需额外调用 MCP 工具,直接输出引导文本。
输出模板:
请访问 Gate 网页端 https://www.gate.com/rewards_hub 或打开 Gate App 查看福利任务和奖励。
案例 2:新用户任务列表
触发条件:步骤 1 判断用户为新用户(cexwelfaregetuseridentity 返回 code=0)。
步骤 2:获取所有新用户引导任务
| 步骤 | MCP 工具 | 参数 | 获取的数据 |
|---|
| 2 | cexwelfaregetbeginnertask_list(查询新手引导任务列表) | 自动获取当前用户任务 | 获取新手引导任务列表,包括注册任务(type=10)和引导任务(type=11),每个任务包含奖励信息、完成状态和任务描述 |
步骤 3:生成任务列表响应
重要提示:必须使用步骤 2 中从 MCP 接口获取的真实任务数据,绝对不得编造或使用模板示例数据!
基于步骤 2 返回的真实任务数据,按以下格式输出给用户:
- 1. 遍历所有任务:针对 cexwelfaregetbeginnertasklist 返回的 data.tasks 数组中的每个任务
- 提取真实字段:使用任务的真实字段,如 taskname、taskdesc、rewardnum、reward_unit、status
- 状态显示:status=1 显示待完成,status=2 显示已完成
- 格式化输出:严格遵循模板格式,但内容必须为真实 MCP 数据
数据映射规则:
- - 任务标题:使用 taskname 字段
- 任务描述:使用 taskdesc 字段
- 奖励数量:使用 rewardnum 字段
- 奖励单位:使用 rewardunit 字段
- 完成状态:使用 status 字段(1=待完成,2=已完成)
响应模板
案例 1 — 现有用户引导
请访问 Gate 网页端 https://www.gate.com/rewards_hub 或打开 Gate App 查看福利任务和奖励。
案例 2 — 新用户任务列表
🎁 您专属的新用户任务如下,完成任务即可领取对应奖励:
{遍历 task_list 中的每个任务:}
📌 {task_name}
{task_desc}
💰 奖励:{rewardnum} {rewardunit}
状态:{根据 status 字段显示:1=待完成,2=已完成}
⚠️ 非代理、非机构用户且账户状态正常的用户可完成任务并领取奖励。具体任务及奖励以 Gate 官网/App 最终展示为准。
示例