gate-exchange-activitycenter

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gate-exchange-activitycenter

Gate交易所活动中心

Activity center aggregates platform campaigns (trading competitions, airdrops, newcomer activities, referral activities, etc.), supporting activity recommendations and my activities entry.

活动中心聚合了平台各类活动（交易竞赛、空投、新人活动、邀请活动等），支持活动推荐和我的活动入口。

General Rules

通用规则

Read and follow the shared runtime rules before proceeding: → exchange-runtime-rules.md

Trigger Scenarios: User mentions "recommend activities", "what activities", "airdrop activities", "trading competition", "VIP activities", "my activities", etc.

⚠️ MANDATORY RESPONSE FORMAT: When this skill is triggered, AI responses MUST strictly follow the Response Templates defined in this document. Free-form responses are FORBIDDEN.

在开始前请阅读并遵循共享的运行时规则： → exchange-runtime-rules.md

触发场景：用户提及"推荐活动"、"有什么活动"、"空投活动"、"交易竞赛"、"VIP活动"、"我的活动"等。

⚠️ 强制响应格式：当该Skill被触发时，AI回复必须严格遵循本文档定义的响应模板。禁止自由格式回复。

Routing Rules

路由规则

User Intent	Keywords/Pattern	Action
Hot Recommendation	"recommend activities" "what activities" "recent activities"	Scenario 1.1 Hot Recommendation
Type-Based Recommendation	"airdrop activities" "trading competition" "VIP activities" "earn activities"	Scenario 1.2 Type-Based
Scenario-Based Recommendation	"I have GT" "futures activities" "spot activities"	Scenario 1.3 Scenario-Based
Search by Name	"{activity name}" "position airdrop"	Scenario 1.4 Search by Name
My Activities	"what activities I joined" "my activities" "enrolled activities"	Scenario 2 My Activities
Welfare Center/Newcomer Tasks	"claim rewards" "check-in" "newcomer tasks"	❌ NOT applicable to this skill

用户意图	关键词/模式	操作
热门推荐	"recommend activities" "what activities" "recent activities"	场景1.1 热门推荐
按类型推荐	"airdrop activities" "trading competition" "VIP activities" "earn activities"	场景1.2 按类型推荐
按场景推荐	"I have GT" "futures activities" "spot activities"	场景1.3 按场景推荐
按名称搜索	"{activity name}" "position airdrop"	场景1.4 按名称搜索
我的活动	"what activities I joined" "my activities" "enrolled activities"	场景2 我的活动
福利中心/新人任务	"claim rewards" "check-in" "newcomer tasks"	❌ 不适用于本Skill

MCP Tools

MCP工具

MCP Tool	Purpose	action_type
`cex_activity_list_activity_types`	Get activity type list (id, name) for type filtering	query
`cex_activity_list_activities`	Query activities by hot/type/scenario/keywords	info-card
`cex_activity_get_my_activity_entry`	Get "My Activities" entry card	info-card

MCP工具	用途	action_type
`cex_activity_list_activity_types`	获取活动类型列表（id、名称）用于类型筛选	query
`cex_activity_list_activities`	按热门/类型/场景/关键词查询活动	info-card
`cex_activity_get_my_activity_entry`	获取"我的活动"入口卡片	info-card

API Parameter Constraints

API参数约束

Parameter	Constraint	Description
`page_size`	MUST be ≤ 3	⚠️ HARD LIMIT: Each request MUST NOT exceed 3 activities. Always set `page_size=3` or less.
`page`	Integer	Page number, default 1.
`recommend_type`	`hot` / `type` / `scenario`	Query mode: hot (popular), type (by type_ids), scenario (by keywords)
`type_ids`	String	Activity type IDs, comma-separated. Used with `recommend_type=type`
`keywords`	String	Search keywords for activity name. Used with `recommend_type=scenario`

⚠️ CRITICAL: The
page_size
parameter is strictly limited to a maximum of 3. Any value greater than 3 is FORBIDDEN.

参数	约束	说明
`page_size`	必须 ≤3	⚠️ 硬性限制：每个请求不得超过3个活动。始终设置 `page_size=3` 或更小。
`page`	整数	页码，默认1。
`recommend_type`	`hot` / `type` / `scenario`	查询模式：hot（热门）、type（按type_ids）、scenario（按关键词）
`type_ids`	字符串	活动类型ID，逗号分隔。与 `recommend_type=type` 配合使用
`keywords`	字符串	活动名称搜索关键词。与 `recommend_type=scenario` 配合使用

⚠️ 重要提示：
page_size
参数严格限制最大值为3。任何大于3的值均被禁止。

Scenario 1: Activity Recommendation

场景1：活动推荐

1.1 Hot Recommendation (No Type Specified)

1.1 热门推荐（未指定类型）

Trigger: "recommend activities" "what activities" "recent activities"

API Call:

cex_activity_list_activities?recommend_type=hot&sort_by=default&page=1&page_size=3

Rules:

✅ Do NOT ask for type clarification, call API directly
✅ Fixed
```
page_size=3
```
(maximum allowed), no pagination

触发语："recommend activities" "what activities" "recent activities"

API调用：

cex_activity_list_activities?recommend_type=hot&sort_by=default&page=1&page_size=3

规则：

✅ 无需询问类型，直接调用API
✅ 固定
```
page_size=3
```
（允许的最大值），不支持分页

1.2 Type-Based Recommendation

1.2 按类型推荐

Trigger: "airdrop activities" "trading competition" "VIP activities" "earn activities"

API Call Sequence:

```
cex_activity_list_activity_types
```
→ Get type list, match user's type name (case-insensitive)

cex_activity_list_activities?recommend_type=type&type_ids=matched_id1,matched_id2&sort_by=time&page_size=3

Keyword Extraction Examples:

"what airdrop activities are there" → Extract: airdrop
"VIP activities" → Extract: VIP
"I'm a VIP, any exclusive activities" → Extract: VIP
"any low-risk activities" → Extract: earn

触发语："airdrop activities" "trading competition" "VIP activities" "earn activities"

API调用顺序：

```
cex_activity_list_activity_types
```
→ 获取类型列表，匹配用户提及的类型名称（不区分大小写）

cex_activity_list_activities?recommend_type=type&type_ids=matched_id1,matched_id2&sort_by=time&page_size=3

关键词提取示例：

"what airdrop activities are there" → 提取：airdrop
"VIP activities" → 提取：VIP
"I'm a VIP, any exclusive activities" → 提取：VIP
"any low-risk activities" → 提取：earn

1.3 Scenario-Based Recommendation

1.3 按场景推荐

Trigger: "I have GT, what activities can I join" "futures activities"

API Call:

If mappable to type: Use
```
recommend_type=type
```
with
```
type_ids
```
If scenario/asset: Use
```
recommend_type=scenario
```
with
```
keywords
```

cex_activity_list_activities?recommend_type=scenario&keywords=GT&page_size=3

触发语："I have GT, what activities can I join" "futures activities"

API调用：

若可映射到类型：使用
```
recommend_type=type
```
并传入
```
type_ids
```
若为资产/场景：使用
```
recommend_type=scenario
```
并传入
```
keywords
```

cex_activity_list_activities?recommend_type=scenario&keywords=GT&page_size=3

1.4 Search by Name

1.4 按名称搜索

Trigger: "help me find position airdrop" "where is VIP exclusive activity" "find test activity"

API Call:

cex_activity_list_activities?recommend_type=scenario&keywords=test_activity&page=1&page_size=3

Parameter Notes:

Use
```
recommend_type=scenario
```
with
```
keywords
```
for name search
```
keywords
```
is the activity name or partial name to search
⚠️ Language Conversion: If user input contains non-English text, translate keywords to English before passing to the
```
keywords
```
parameter

Response Template (when results found):

Based on your keywords, I found some possible activities. If you didn't find the activity you're looking for, you can provide a more complete activity name, or click more activities to explore more hot activities.

触发语："help me find position airdrop" "where is VIP exclusive activity" "find test activity"

API调用：

cex_activity_list_activities?recommend_type=scenario&keywords=test_activity&page=1&page_size=3

参数说明：

使用
```
recommend_type=scenario
```
并传入
```
keywords
```
进行名称搜索
```
keywords
```
为活动名称或部分名称
⚠️ 语言转换：若用户输入包含非英文文本，需先将关键词翻译为英文再传入
```
keywords
```
参数

响应模板（找到结果时）：

根据您的关键词，我找到了一些可能的活动。如果未找到您想要的活动，可以提供更完整的活动名称，或点击更多活动查看更多热门活动。

Scenario 2: My Activities

场景2：我的活动

Trigger: "what activities I joined" "my activities" "enrolled activities"

API Call:

cex_activity_get_my_activity_entry

Rules:

✅ Only show entry card, guide user to click and jump
✅ Apply URL Processing Rules (see above) to the
```
url
```
field
❌ Do NOT filter activity list in this API

触发语："what activities I joined" "my activities" "enrolled activities"

API调用：

cex_activity_get_my_activity_entry

规则：

✅ 仅展示入口卡片，引导用户点击跳转
✅ 对
```
url
```
字段应用URL处理规则（见上文）
❌ 不得在此API中筛选活动列表

Decision Logic

决策逻辑

Condition	Action
User asks for hot/recommended activities	Call `cex_activity_list_activities` with `recommend_type=hot` directly
User specifies activity type	First call `cex_activity_list_activity_types` , then `cex_activity_list_activities` with `recommend_type=type&type_ids=xxx`
User mentions asset/scenario (GT, futures)	Use `recommend_type=scenario` with `keywords`
User searches by activity name	Use `recommend_type=scenario` with `keywords={activity_name}`
User asks "my activities"	Call `cex_activity_get_my_activity_entry`
Activity list returns empty	Use "No Results" template, do NOT use "filtered for you..."

条件	操作
用户询问热门/推荐活动	直接调用 `cex_activity_list_activities` 并设置 `recommend_type=hot`
用户指定活动类型	先调用 `cex_activity_list_activity_types` ，再调用 `cex_activity_list_activities` 并设置 `recommend_type=type&type_ids=xxx`
用户提及资产/场景（GT、期货）	使用 `recommend_type=scenario` 并传入 `keywords`
用户按活动名称搜索	使用 `recommend_type=scenario` 并传入 `keywords={activity_name}`
用户询问"我的活动"	调用 `cex_activity_get_my_activity_entry`
活动列表返回空	使用"无结果"模板，不得使用"为您筛选了..."表述

URL Processing Rules

URL处理规则

All activity URLs returned by API must be processed before displaying to users:

URL Pattern	Processing	Example
Relative path (starts with `/` )	Prepend `https://www.gate.com`	`/competition/xxx` → `https://www.gate.com/competition/xxx`
Already has host (starts with `http://` or `https://` )	Keep as-is, no modification	`https://www.gate.com/campaigns/xxx` → `https://www.gate.com/campaigns/xxx`

Why relative paths? API returns relative paths for flexibility:

Multi-language support: Frontend can dynamically add language prefix (
```
/zh/
```
,
```
/en/
```
,
```
/ja/
```
)
Multi-environment deployment: Different domains for test/staging/production
Client flexibility: Web, App, H5 can handle links differently

Display Format: Always use clickable Markdown link:

[{activity_title}]({processed_url})

API返回的所有活动URL在展示给用户前必须进行处理：

URL模式	处理方式	示例
相对路径（以 `/` 开头）	前缀添加 `https://www.gate.com`	`/competition/xxx` → `https://www.gate.com/competition/xxx`
已包含主机（以 `http://` 或 `https://` 开头）	保持原样，不修改	`https://www.gate.com/campaigns/xxx` → `https://www.gate.com/campaigns/xxx`

为什么使用相对路径？ API返回相对路径以保证灵活性：

多语言支持：前端可动态添加语言前缀（
```
/zh/
```
、
```
/en/
```
、
```
/ja/
```
）
多环境部署：测试/预发布/生产环境使用不同域名
客户端灵活性：Web、App、H5可对链接进行不同处理

展示格式：始终使用可点击的Markdown链接：

[{activity_title}]({processed_url})

Activity Response Field Specification

活动响应字段规范

For all activity recommendation scenarios (1.1, 1.2, 1.3, 1.4), the response MUST only include the following fields:

API Field	Display Label	Processing Rule
`master_one_line`	Activity Title	Display as-is
`url`	Activity Link	Apply URL Processing Rules (prepend `https://www.gate.com` for relative paths)
`type_name`	Activity Type	Display the `type_name` value directly (NOT `type_id` )

Response Format Example:

Activity Title	Activity Type	Activity Link
Traditional Assets Limited Edition Event	Traditional Assets	View Details

Rules:

✅ Only display the 3 fields listed above
✅ Use
```
type_name
```
for activity type (NOT
```
type_id
```
)
✅ Process URLs according to URL Processing Rules
❌ Do NOT display other fields like
```
id
```
,
```
type_id
```
,
```
hot
```
,
```
img
```
,
```
competition_name
```
,
```
start_at
```
,
```
end_at
```
, etc.

对于所有活动推荐场景（1.1、1.2、1.3、1.4），响应必须仅包含以下字段：

API字段	显示标签	处理规则
`master_one_line`	活动标题	原样展示
`url`	活动链接	应用URL处理规则（相对路径前缀添加 `https://www.gate.com` ）
`type_name`	活动类型	直接展示 `type_name` 值（不得使用 `type_id` ）

响应格式示例：

活动标题	活动类型	活动链接
Traditional Assets Limited Edition Event	Traditional Assets	查看详情

规则：

✅ 仅展示上述3个字段
✅ 使用
```
type_name
```
作为活动类型（不得使用
```
type_id
```
）
✅ 按照URL处理规则处理链接
❌ 不得展示其他字段，如
```
id
```
、
```
type_id
```
、
```
hot
```
、
```
img
```
、
```
competition_name
```
、
```
start_at
```
、
```
end_at
```
等

Response Templates

响应模板

⚠️ MANDATORY: AI responses MUST strictly follow these templates. Free-form or custom responses are FORBIDDEN.

⚠️ 强制要求：AI回复必须严格遵循以下模板。禁止自由格式或自定义回复。

Template Compliance Rules

模板合规规则

REQUIRED: Every response MUST use the exact template structure defined below
REQUIRED: Include the intro text + activity table + follow-up prompt
FORBIDDEN: Adding extra commentary, explanations, or custom formatting
FORBIDDEN: Omitting any part of the template structure

必填：每个回复必须使用以下定义的精确模板结构
必填：包含介绍文本 + 活动表格 + 后续提示
禁止：添加额外评论、解释或自定义格式
禁止：省略模板结构的任何部分

Activity Recommendation (Has Results)

活动推荐（有结果）

Scenario	Intro Text (MUST use exactly)
Hot (1.1)	Here are the current hot activities:
By Type (1.2)	Filtered [type] activities for you:
By Scenario (1.3)	Filtered activities related to [scenario/asset] for you:
By Name (1.4)	Based on your keywords, I found some possible activities:

Required Response Structure:

{Intro Text from table above}

| Activity Title | Activity Type | Activity Link |
|----------------|---------------|---------------|
| {master_one_line} | {type_name} | [View Details]({processed_url}) |
| ... | ... | ... |

{Follow-up Prompt - see below}

Follow-up Prompts by Scenario:

Scenario	Follow-up Prompt (MUST include)
Hot (1.1)	Click the link to view details or sign up. Need activities of a specific type?
By Type (1.2)	Click the link to view details and how to participate.
By Scenario (1.3)	Click the link to view participation requirements and rewards.
By Name (1.4)	If you didn't find what you're looking for, provide a more complete activity name.

场景	介绍文本（必须严格使用）
热门推荐（1.1）	以下是当前的热门活动：
按类型推荐（1.2）	为您筛选了[type]类活动：
按场景推荐（1.3）	为您筛选了与[场景/资产]相关的活动：
按名称搜索（1.4）	根据您的关键词，我找到了一些可能的活动：

必填响应结构：

{上述表格中的介绍文本}

| 活动标题 | 活动类型 | 活动链接 |
|----------------|---------------|---------------|
| {master_one_line} | {type_name} | [查看详情]({processed_url}) |
| ... | ... | ... |

{后续提示 - 见下文}

各场景后续提示：

场景	后续提示（必须包含）
热门推荐（1.1）	点击链接查看详情或报名。需要特定类型的活动吗？
按类型推荐（1.2）	点击链接查看详情及参与方式。
按场景推荐（1.3）	点击链接查看参与要求及奖励。
按名称搜索（1.4）	如果未找到您想要的活动，请提供更完整的活动名称。

My Activities Template (Scenario 2)

我的活动模板（场景2）

Required Response Structure:

Click [My Events]({processed_url}) to view your enrolled and ongoing activities.

In "My Events" you can:
- View activity progress
- Claim activity rewards
- Track activity status

必填响应结构：

点击[我的活动]({processed_url})查看您已报名及进行中的活动。

在"我的活动"中您可以：
- 查看活动进度
- 领取活动奖励
- 跟踪活动状态

No Results Template

无结果模板

Required Response Structure:

Currently no [type/keyword] activities are in progress. You can:
- Check the activity center regularly, new activities will be displayed as soon as they launch
- Tell me other activity types you're interested in (e.g., trading, earn, VIP exclusive), and I can filter for you

必填响应结构：

当前暂无[type/关键词]类活动进行中。您可以：
- 定期查看活动中心，新活动上线后会及时展示
- 告诉我您感兴趣的其他活动类型（如交易、赚币、VIP专属），我可为您筛选

Error Handling

错误处理

Error Type	Response Template
API timeout/failure	Unable to load activities at the moment, please try again later.
No matching activities	Use "No Results" template
401 Unauthorized	Session expired, please log in again to view activities.
400 Bad Request	Unable to process your request. Please try a different search term.
429 Rate Limited	Too many requests. Please wait a moment and try again.
500 Server Error	Service temporarily unavailable. Please try again later.
Network Error	Network connection issue. Please check your connection and try again.

错误类型	响应模板
API超时/失败	暂时无法加载活动，请稍后重试。
无匹配活动	使用"无结果"模板
401未授权	会话已过期，请重新登录以查看活动。
400请求错误	无法处理您的请求，请尝试其他搜索词。
429请求限制	请求过于频繁，请稍候再试。
500服务器错误	服务暂时不可用，请稍后重试。
网络错误	网络连接问题，请检查网络后重试。

Safety Rules

安全规则

No investment advice: Activity rewards are platform benefits, not investment guidance
No data fabrication: Only show data returned by backend
Compliance check: Do not show activities unavailable in user's region
No internal exposure: Never mention technical details to users, including:
- API names (e.g.,
```
cex_activity_list_activities
```
  )
- Parameter names (e.g.,
```
recommend_type
```
  ,
```
type_ids
```
  )
- Internal IDs (e.g.,
```
type_id=34
```
  ,
```
id=1499
```
  )
- Error codes or technical error messages
- Example of BAD response: "No Alpha type activities found (type_id=34)"
- Example of GOOD response: "Currently no Alpha activities are in progress"

不提供投资建议：活动奖励属于平台福利，并非投资指导
不编造数据：仅展示后端返回的数据
合规检查：不得展示用户所在地区不可用的活动
不暴露内部信息：绝不向用户提及技术细节，包括：
- API名称（如
```
cex_activity_list_activities
```
  ）
- 参数名称（如
```
recommend_type
```
  、
```
type_ids
```
  ）
- 内部ID（如
```
type_id=34
```
  、
```
id=1499
```
  ）
- 错误码或技术错误信息
- 错误回复示例："未找到Alpha类型活动（type_id=34）"
- 正确回复示例："当前暂无Alpha类型活动进行中"

Data Integrity Rules

数据完整性规则

⚠️ MANDATORY: These rules MUST be followed for ALL data processing and display.

⚠️ 强制要求：所有数据处理和展示必须遵循以下规则。

1. Never Guess Data

1. 绝不猜测数据

❌ FORBIDDEN: Guessing, estimating, or fabricating any data values
❌ FORBIDDEN: Making assumptions about timestamps, numbers, or any computed values
✅ REQUIRED: Only display data exactly as returned by API
✅ REQUIRED: If data is missing or unclear, state "Data unavailable" instead of guessing

❌ 禁止：猜测、估算或编造任何数据值
❌ 禁止：对时间戳、数字或任何计算值做出假设
✅ 要求：仅展示API返回的原始数据
✅ 要求：若数据缺失或不明确，显示"数据暂不可用"而非猜测

2. Self-Verification Mechanism

2. 自我验证机制

Before displaying any processed data, perform self-check:

Data Type	Verification Method
Timestamps	Verify conversion result is reasonable (year, month, day within expected range)
URLs	Verify URL format is valid after processing
Numbers	Verify numeric values match API response exactly
Type names	Verify `type_name` exists in API response, do NOT derive from `type_id`

在展示任何处理后的数据前，执行自我检查：

数据类型	验证方式
时间戳	验证转换结果合理（年、月、日在预期范围内）
URL	验证处理后的URL格式有效
数字	验证数值与API响应完全一致
类型名称	验证 `type_name` 存在于API响应中，不得从 `type_id` 推导

3. Proactive Validation (Not Reactive Correction)

3. 主动验证（而非被动修正）

✅ REQUIRED: Validate data BEFORE presenting to user
✅ REQUIRED: Double-check time-sensitive information (timestamps, dates)
❌ FORBIDDEN: Wait for user to point out errors
❌ FORBIDDEN: Display data first and correct later

✅ 要求：在展示给用户前验证数据
✅ 要求：仔细检查时间敏感信息（时间戳、日期）
❌ 禁止：等待用户指出错误
❌ 禁止：先展示数据再修正

4. Error Handling for Data Issues

4. 数据问题的错误处理

If data validation fails:

Do NOT display the problematic data
Show a safe fallback message: "Some data is temporarily unavailable"
Log the issue internally (do NOT expose to user)

若数据验证失败：

不展示有问题的数据
显示安全回退消息："部分数据暂不可用"
内部记录问题（不得向用户暴露）

Cross-Skill Routing

跨Skill路由

User Follow-up Intent	Route To
"I want to buy crypto"	Trading skill
"I want to stake"	Launchpool/Earn skill
"Welfare center" "check-in"	Welfare center skill (NOT this skill)

用户后续意图	路由至
"I want to buy crypto"	交易Skill
"I want to stake"	Launchpool/Earn Skill
"Welfare center" "check-in"	福利中心Skill（非本Skill）

Additional References

额外参考

For detailed scenarios and examples, see

references/scenarios.md

如需详细场景和示例，请查看

references/scenarios.md