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 LaunchPool Suite

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)

• gate-cli cex launch pledge-records
• gate-cli cex launch projects
• gate-cli cex launch reward-records

Execution Operations (Write)

• gate-cli cex launch pledge
• gate-cli cex launch redeem

Authentication

• Interactive file setup: when GATEAPIKEY and GATEAPISECRET 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 GATEAPIKEY and GATEAPISECRET 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-cli (run sh ./setup.sh from this skill directory if missing; optional GATECLISETUP_MODE=release).
• Add $HOME/.openclaw/skills/bin to PATH if you invoke gate-cli by name (or the directory where [setup.sh](./setup.sh) installs it).
• Credentials: When GATEAPIKEY and GATEAPISECRET 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 GATEAPIKEY / GATEAPISECRET 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](./references/gate-cli.md), then execute this skill's LaunchPool workflow.

• SKILL.md keeps routing and product semantics.
• references/gate-cli.md is the authoritative gate-cli execution contract for project/record queries, stake-redeem confirmation gates, and result verification.

Module overview

Domain Knowledge

LaunchPool concepts

Timestamp formatting

The createtimest and rewardtimest fields in pledge/reward records are pre-formatted strings from the API (e.g. "2026-03-16 09:32:22"). Display them as-is in the data row and put (UTC) in the table header instead of appending to each value.

Project time fields (starttimest, endtimest) are internal data — do NOT display them to the user.

Reward records time params: The reward records API requires starttime/endtime as integer unix timestamps, which are error-prone to calculate. Follow the Timestamp strategy in references/records.md (Strategy 1: skip time params for recent queries; Strategy 2: use anchor table for historical ranges). Do NOT attempt to mentally compute unix timestamps without the anchor table.

Number formatting

Routing rules

Execution

1. Intent and parameters

• Determine module (Projects / Stake / Redeem / Pledge Records / Reward Records).
• Stake intent: If the user wants to stake tokens, route to references/stake-redeem.md Stake section. Requires project identification + amount + user confirmation.
• Redeem intent: If the user wants to redeem, route to references/stake-redeem.md Redeem section. Requires project identification + amount + user confirmation.
• Extract parameters: coin, pid, rid, amount, status, sorttype, limitrule, page, starttime, endtime.
• Missing: if user says "LaunchPool" without specifying intent, ask which operation or show projects by default.

2. Tool selection

• Stake: First call gate-cli cex launch projects to identify the target project pid and reward pool rid, then show preview, wait for confirmation, then call gate-cli cex launch pledge.
• Redeem: Show preview of the redemption, wait for confirmation, then call gate-cli cex launch redeem.

3. Format response

• Use the Response Template and field names from the reference file for the chosen module.
• Projects: show name, projectstate, totalamount, days, and per reward pool: coin, rateyear, alreadybuytotalamount, personalmaxamount/personalminamount, transactionconfig. Do NOT display starttimest/end_timest, pid, or rid.
• Stake/Redeem: show order preview first, then confirmation result. Stake returns flow_id; Redeem returns success boolean.
• Pledge Records: show createtimest, rewardcoin, coin, amount, type (1=Stake, 2=Redeem). Note: API does not return project name.
• Reward Records: show rewardtimest, coin (reward coin), validmortgageamount, amountbase, amount_ext. Note: API does not return project name.

Report template

After each operation, output a short standardized result consistent with the reference (e.g. project list table, stake confirmation, redeem confirmation, pledge record list, reward record list). Use the exact response fields from the API (see references) so the user sees correct field names and values.

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.

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

• Product name: LaunchPool
• Currency symbols from API: USDT, GT, BTC, DOGE, etc.
• Project names from API name field (e.g. "DOGE", "USDT-rudy")
• Technical IDs and their values: pid, rid, flow_id (internal use only, do NOT display to user)
• Timestamp format including the (UTC) suffix
• API error labels: INVALIDPARAMVALUE, INSUFFICIENTBALANCE, INVALIDCREDENTIALS, PROJECTNOTFOUND
• Numeric values, percentages, and the unit USD in trading volume 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

• Stake and Redeem are write operations. Before calling gate-cli cex launch pledge or gate-cli cex launch redeem, MUST show an order preview and wait for explicit user confirmation.
• Preview format: project name, staking coin, amount, estimated APR (for stake), staking period.
• 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, LaunchPool is not available in your region." Do NOT retry.