gate-exchange-activitycenter

Resolving gate-cli (binary path)

Resolve gate-cli in order: (1) command -v gate-cli and gate-cli --version succeeds; (2) ${HOME}/.local/bin/gate-cli if executable; (3) ${HOME}/.openclaw/skills/bin/gate-cli if executable. Canonical rules: exchange-runtime-rules.md §4 (or gate-runtime-rules.md §4).

gate-exchange-activitycenter

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

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 use the gate-cli commands explicitly listed in this skill. Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.

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.

Skill Dependencies

gate-cli commands used

Query Operations (Read-only)

• gate-cli cex activity get-entry
• gate-cli cex activity list
• gate-cli cex activity types

Authentication

• Interactive file setup: when GATE_API_KEY and GATE_API_SECRET are not both set on the host, run gate-cli config init to complete the wizard for API key, secret, profiles, and defaults (see gate-cli).
• Env / flags: gate-cli config init is not required when credentials are already supplied — e.g. both GATE_API_KEY and GATE_API_SECRET set on the host, or --api-key / --api-secret where supported — never ask the user to paste secrets into chat.
• API Key Required: Yes
• Permissions: Activity:Read
• Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

Installation Check

• Required: gate-cli (run sh ./setup.sh from this skill directory if missing; optional GATE_CLI_SETUP_MODE=release).
• Add $HOME/.openclaw/skills/bin to PATH if you invoke gate-cli by name (or the directory where setup.sh installs it).
• Credentials: When GATE_API_KEY and GATE_API_SECRET are both set (non-empty) for the host, do not require gate-cli config init — that is equivalent valid config for gate-cli. When both are unset or empty, remind the operator to run gate-cli config init or to configure GATE_API_KEY / GATE_API_SECRET in the matching skill from the skill library (never ask the user to paste secrets into chat).
• Sanity check: Do not proceed with authenticated calls until the CLI behaves as expected (e.g. gate-cli --version or a read-only gate-cli cex ... command from this skill); confirm credentials resolve before mutating operations.

Execution mode

Read and strictly follow references/gate-cli.md, then execute this skill's activity-center workflow.

• SKILL.md keeps routing and recommendation logic.
• references/gate-cli.md is the authoritative gate-cli execution contract for entry/list/type queries, filter handling, and degraded output behavior.

Routing Rules

gate-cli command index

API Parameter Constraints

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

Scenario 1: Activity Recommendation

1.1 Hot Recommendation (No Type Specified)

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

API Call:

`gate-cli cex activity list`?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

1.2 Type-Based Recommendation

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

API Call Sequence:

1. gate-cli cex activity types → Get type list, match user's type name (case-insensitive)
2. 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

1.3 Scenario-Based Recommendation

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

`gate-cli cex activity list`?recommend_type=scenario&keywords=GT&page_size=3

1.4 Search by Name

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

API Call:

`gate-cli cex activity list`?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.

Scenario 2: My Activities

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

API Call:

`gate-cli cex activity get-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

Decision Logic

URL Processing Rules

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

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})

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:

Response Format Example:

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.

Response Templates

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

Template Compliance Rules

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

Activity Recommendation (Has Results)

Required Response Structure:

{Intro Text from table above}

| Activity Title | Activity Type | Activity Link |
|----------------|---------------|---------------|

Follow-up Prompts by Scenario:

My Activities Template (Scenario 2)

Required Response Structure:

No Results Template

Required Response Structure:

Error Handling

Safety Rules

1. No investment advice: Activity rewards are platform benefits, not investment guidance
2. No data fabrication: Only show data returned by backend
3. Compliance check: Do not show activities unavailable in user's region
4. No internal exposure: Never mention technical details to users, including:

• API names (e.g., gate-cli cex activity list)
• 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"

Data Integrity Rules

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

1. Never Guess Data

• ❌ 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

2. Self-Verification Mechanism

Before displaying any processed data, perform self-check:

3. Proactive Validation (Not Reactive Correction)

• ✅ 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

If data validation fails:

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

Cross-Skill Routing

Additional References

For detailed scenarios and examples, see references/scenarios.md