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 Unified Account Assistant

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.

Skill Dependencies

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.
• API Key Required: Yes
• Permissions: Unified:Read, Unified: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 unified-account routing.

• SKILL.md keeps scenario routing and confirmation policy.
• references/gate-cli.md is the authoritative gate-cli execution contract for limits checks, mutation drafts, and post-state verification.

Domain Knowledge

Tool Mapping by Domain

Capability Notes and API Coverage

• Batch borrowable and batch transferable endpoints may not be exposed as dedicated tools; for multi-currency requests, iterate single-currency queries and aggregate results.
• Loan repayment uses createunifiedloan with type=repay; full repayment uses repaid_all=true.
• Unified mode switching is high-impact and may fail if account risk constraints are not satisfied.
• Per-currency leverage settings should be validated against current account mode and platform limits.
• Collateral configuration changes can alter borrow power and liquidation risk.

Response Rendering Rules (Mandatory)

• Do not round API numeric strings for equity, borrowable, transferable, rates, or leverage values unless the user explicitly asks for formatted rounding.
• Do not trim, shorten, or normalize decimal strings. If API returns trailing zeros or long decimals, display the exact raw value string as returned.
• When API returns timestamps, show both raw timestamp and human-readable time (local timezone).
• For account-overview replies, always include account-level IMR/MMR using API fields:

- IMR: totalInitialMarginRate - MMR: totalMaintenanceMarginRate

• When per-currency risk fields are present in balances, include imr and mmr for each reported currency (preserve original API numeric strings).
• Unified mode display labels must use this mapping:

- classic -> 经典现货模式 - singlecurrency -> 单币种保证金模式 - multicurrency -> 跨币种保证金模式 - portfolio -> 组合保证金模式

• If unified account is not enabled/opened, place this warning at the top of the response: ⚠️ 当前账户未开通统一账户功能。

Risk-Sensitive Action Rules

Mutating unified actions are treated as high risk:

• createunifiedloan (borrow/repay)
• setunifiedmode
• setuserleveragecurrencysetting
• setunifiedcollateral

For each of the actions above, always require explicit user confirmation immediately before execution.

Workflow

When the user asks for any unified account operation, follow this sequence.

Step 1: Identify Task Type

Classify the request into one of these six categories:

1. Account overview and mode query
2. Borrowable/transferable limit query
3. Borrow/repay execution
4. Loan/interest history query
5. Leverage/collateral configuration
6. Mixed risk-and-funding actions (for example check limit, then borrow)

Step 2: Extract Parameters and Run Pre-checks

Extract key fields:

• currency or currency list
• operation type (borrow/repay, query vs mutation)
• amount and repaid_all intent
• target mode (classic / singlecurrency / multicurrency / portfolio)
• leverage value and collateral enable/disable lists

Pre-check order:

1. Required parameters completeness
2. Limit sufficiency (borrowable / transferable) for requested amount
3. Account mode and risk compatibility
4. User intent clarity for high-risk configuration changes

Step 3: Final User Confirmation Before Any Mutation (Mandatory)

Before every mutating call, provide an Action Draft first, then wait for explicit confirmation.

Required execution flow:

1. Send draft summary (no mutation call yet)
2. Wait for explicit user approval
3. Submit real mutation call only after approval
4. Treat confirmation as single-use
5. If parameters change, invalidate old confirmation and re-confirm

Required confirmation fields:

• operation type (borrow/repay/mode switch/leverage/collateral)
• target object (currency, mode, leverage, enable/disable lists)
• amount or config value
• key risk note

Recommended draft wording:

• Action Draft: borrow 100 USDT in unified account. Pre-check: max borrowable 250 USDT. Risk: interest accrues hourly. Reply "Confirm action" to proceed.

Hard blocking rules (non-bypassable):

• NEVER call mutation tools without explicit confirmation from the immediately previous user turn.
• If request scope changes (currency, amount, mode, leverage, collateral set), request fresh confirmation.
• For multi-step actions, require confirmation per mutation step.

Step 4: Call Tools by Scenario

Use only the minimal tool set required for the task:

• Account overview: getunifiedaccounts
• Mode query/switch: getunifiedmode / setunifiedmode
• Borrowable checks: getunifiedborrowable
• Transferable checks: getunifiedtransferable
• Borrow/repay: createunifiedloan
• Loan and interest records: listunifiedloanrecords, listunifiedloaninterest_records
• Currency support and rates: listunifiedcurrencies, getunifiedestimate_rate
• Leverage settings: getuserleveragecurrencysetting, setuserleveragecurrencysetting
• Collateral settings: setunifiedcollateral
• Risk tiers: listcurrencydiscount_tiers

Step 5: Return Actionable Result and Status

The response must include:

• Whether execution succeeded (or why it did not execute)
• Core numbers (amount, limit, rate, leverage, mode, key risk fields)
• For overview queries: explicitly include IMR/MMR (totalInitialMarginRate / totalMaintenanceMarginRate) and include per-currency imr/mmr when present
• For all money/rate outputs: preserve exact API string precision; do not trim or format decimals automatically
• For record queries: provide readable time alongside timestamps
• If condition not met, clearly explain gap and next option

Case Routing Map (1-18)

A. Account and Mode (1-3)

B. Borrow Limits and Borrowing (4-8)

C. Repayment and Records (9-12)

D. Transferability and Risk Config (13-18)

Judgment Logic Summary

Report Template

## Execution Result

| Item | Value |
|------|-----|
| Scenario | {case_name} |
| Scope | {currency_or_mode_scope} |
| Action | {action} |
| Status | {status} |
| Key Metrics | {key_metrics} |

{decision_text}

Example decision_text:

• ✅ Action completed successfully.
• 📝 Action draft ready. Reply "Confirm action" to proceed.
• ⏸️ Not executed: requested amount exceeds current limit.
• ❌ Not executed: required parameter is missing.

Error Handling

Cross-Skill Workflows

Workflow A: Unified Borrow Then Spot Buy

1. Use gate-exchange-unified to borrow quote currency (Case 6)
2. Use gate-exchange-spot to execute buy order with borrowed funds

Workflow B: Spot Sell Then Unified Repay

1. Use gate-exchange-spot to liquidate target asset into quote currency
2. Use gate-exchange-unified to repay outstanding loan (Case 9/10)

Safety Rules

• Before any mutation, restate target currency/mode/value and key risk.
• For borrowing, explicitly disclose that interest accrues and rates may vary.
• For mode or leverage changes, mention potential impact on margin and liquidation risk.
• For collateral changes, show both enable and disable sets before execution.
• Without explicit confirmation, stay in read-only mode.
• Do not reuse stale confirmations; re-confirm if any parameter changes.
• If constraints are not met, do not force execution; provide alternatives.