Gate Exchange Candydrop

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 CandyDrop

Authoring language: This skill’s instructions and reference prose are written in English (Gate skill standard). End-user replies still follow Language adaptation (match the user’s locale).

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 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.

Skill Dependencies

gate-cli commands used

Query Operations (Read-only, Public)

• gate-cli cex launch candy-drop activities
• gate-cli cex launch candy-drop rules

Query Operations (Read-only, Auth Required)

• gate-cli cex launch candy-drop progress
• gate-cli cex launch candy-drop participations
• gate-cli cex launch candy-drop airdrops

Execution Operations (Write)

• gate-cli cex launch candy-drop register

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.
• Permissions: Launch:Write
• Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

Installation Check

• Required: Gate (main), Gate (trading); gate-cli when using CLI-backed flows (install via setup.sh from this skill when applicable).
• Install (MCP / IDE): Run installer skill for your environment — Cursor: gate-mcp-cursor-installer; Codex: gate-mcp-codex-installer; Claude: gate-mcp-claude-installer; OpenClaw: gate-mcp-openclaw-installer.
• 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: Before authenticated or mutating calls, confirm the runtime works (e.g. gate-cli --version or a read-only check appropriate to this skill); resolve credentials before registration or write operations.

Execution mode

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

• SKILL.md keeps routing and product semantics.
• references/gate-cli.md is the authoritative gate-cli execution contract for activity/rule queries, registration confirmation gates, progress/record queries, and result verification.

Module overview

Domain Knowledge

CandyDrop concepts

Timestamp formatting

• API returns time fields (e.g. start_time, end_time, register_time, airdrop_time) as pre-formatted UTC strings in the format YYYY-MM-DD HH:MM:SS(UTC).
• Tables / lists: Put (UTC) in the column header when the time is UTC. If the header already says (UTC) (ASCII or full-width punctuation variants), do not repeat it on every cell: strip a trailing (UTC) from the API value and show YYYY-MM-DD HH:MM:SS only (example: 2026-04-13 04:04:10, not 2026-04-13 04:04:10(UTC)). If the header does not mark UTC, keep the API string as-is so the zone is not lost.
• Other surfaces (e.g. inline sentences without a UTC-labeled header): you may keep the API form or use header + stripped cell style consistently within one reply.
• Query parameters start_time / end_time for records are integer unix timestamps (seconds). See Timestamp strategy in references/records.md for correct computation.

Number formatting

Dual-parameter resolution

Activity query interfaces support locating an activity by either activity_id or currency:

• currency (e.g. "USDT"): API auto-matches the nearest active activity for that token.
• activity_id: Precise numeric ID lookup.
• Priority: currency is preferred. If user provides both, use both. If only activity_id is given, use it directly. If neither is provided for rules/progress, ask the user for currency.

Routing rules

Execution

1. Intent and parameters

• Determine module (Activity List / Activity Rules / Register / Task Progress / Participation Records / Airdrop Records).
• Register intent: Route to references/register.md. Requires currency (required) and optionally activity_id. Must follow Preview-Confirm flow.
• Records intent: Route to references/records.md. Extract currency, status, start_time, end_time, page, limit.
• Extract parameters: currency, activity_id, status, rule_name, register_status, limit, offset, page, start_time, end_time.
• Missing: If user says "CandyDrop" without specifying intent, ask which operation or show activities by default — if showing the list, use concise output (title + table, no glossary; see references/activities.md).

2. Tool selection

• Register: Show registration preview, wait for confirmation, then call gate-cli cex launch candy-drop register.
• Records: Follow the Timestamp strategy in references/records.md for time parameter computation.

3. Format response

• Use the Response Template and field names from the reference file for the chosen module.
• Activity List: Optional one-line title + data table; for browse / “what activities are there” intents, no tutorial, field glossary, or pasting the task-type map — localize rule_name only inside cells. Fields: currency, total_rewards, start_time, end_time, rule_name, participants, user_max_rewards.
• Activity Rules: show currency, total_rewards, start_time, end_time, and per prize pool: prize_all, prize_limit, tasks.
• Register: show confirmation result (success).
• Task Progress: show currency, total_rewards, start_time, end_time, and per task: task_name, task_desc, value.
• Participation Records: show currency, status, register_time, id (time cells: strip trailing (UTC) when the table header already marks UTC — see Timestamp formatting above).
• Airdrop Records: show currency, airdrop_time, rewards with token unit ({rewards} {currency}) only — do not show flash-convert / USDT (convert_amount) (see references/records.md).

Report template

After each operation, output a short standardized result consistent with the reference (e.g. activity list, rules, registration confirmation, progress, records). Activity list answers stay minimal (see references/activities.md). Use the API field names and semantic values; where the reference requires localization (e.g. rule_name task types), render in the user’s language per references/activities.md without embedding the whole mapping as user-visible prose.

Language adaptation: Always respond in the same language as the user's input. The Response Templates in reference files define the structure and fields to display, not the literal output language. Translate all display labels to match the user's language.

Must localize (not tickers / not “keep English”):

• rule_name entries in the activity list (and anywhere shown as “task type”): use the Task types mapping table in references/activities.md — these strings describe product task categories (e.g. Futures, Simple Earn), not token symbols.

Do NOT translate (keep as-is regardless of language):

• Product name: CandyDrop
• Currency symbols from API: USDT, GT, BTC, DOGE, etc.
• Technical IDs and their values: id, activity_id (internal use, do NOT display unless relevant)
• Timestamp layout YYYY-MM-DD HH:MM:SS and the literal (UTC) token when it must remain visible (e.g. no UTC in header); do not drop timezone information in those cases
• API error labels: INVALID_PARAM_VALUE, SERVER_ERROR
• Numeric values, percentages, and the unit USD in thresholds

All other display labels should be translated to match the user's language.

Error Handling

API error labels

The API returns structured errors with a label field. Map them as follows:

Empty result handling

Safety rules

Confirmation required

• Register is a write operation. Before calling gate-cli cex launch candy-drop register, MUST show a registration preview and wait for explicit user confirmation.
• Preview format: activity currency, activity ID (if known).
• Ask user to reply "confirm" to proceed or "cancel" to abort.
• Only call the API after receiving explicit confirmation.

Compliance

• When the API returns a compliance or region restriction error, display a friendly message: "Due to compliance restrictions, CandyDrop is not available in your region." Do NOT retry.

Data integrity

• Preserve currency and activity_id exactly as the user provided.
• Do NOT fabricate activity data, reward amounts, or task progress.
• Only display data returned by actual API responses.