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 Account and Asset Manager

This is an L2 composite skill that orchestrates 58 deduplicated MCP tool calls (54 read + 4 write) across 7 L1 skills. It provides a unified entry point for account and asset overview, margin and liquidation risk assessment, SimpleEarn and staking earnings snapshots, affiliate commission queries, and unified-account write operations (borrowing, collateral, leverage settings). This skill is intended for users aged 18 or above with full civil capacity.

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 alpha account balances
• gate-cli cex alpha market currencies
• gate-cli cex alpha market tickers
• gate-cli cex alpha market tokens
• gate-cli cex earn staking assets
• gate-cli cex earn staking awards
• gate-cli cex earn staking find
• gate-cli cex earn uni currency
• gate-cli cex earn uni interest
• gate-cli cex earn dual balance
• gate-cli cex earn dual orders
• cex_earn_list_structured_orders
• gate-cli cex earn uni currencies
• gate-cli cex earn uni rate
• gate-cli cex earn uni lends
• gate-cli cex earn staking orders
• gate-cli cex futures account get
• gate-cli cex futures market candlesticks
• gate-cli cex futures market contract
• gate-cli cex futures market funding-rate
• gate-cli cex futures market orderbook
• gate-cli cex futures market premium
• gate-cli cex futures market tickers
• gate-cli cex futures market trades
• gate-cli cex futures market liquidations
• gate-cli cex futures position list
• gate-cli cex margin account list
• gate-cli cex options account get
• gate-cli cex rebate broker commissions
• gate-cli cex rebate broker transactions
• gate-cli cex rebate partner commissions
• gate-cli cex rebate partner sub-list
• gate-cli cex rebate partner transactions
• gate-cli cex rebate user-info
• gate-cli cex rebate sub-relation
• gate-cli cex spot account get
• gate-cli cex spot market candlesticks
• gate-cli cex spot market orderbook
• gate-cli cex spot market tickers
• gate-cli cex spot market trades
• gate-cli cex spot account book
• gate-cli cex tradfi account assets
• gate-cli cex unified account get
• gate-cli cex unified query borrowable
• gate-cli cex unified query estimate-rate
• gate-cli cex unified mode get
• gate-cli cex unified query transferable
• gate-cli cex unified config leverage-get
• gate-cli cex unified config discount-tiers
• gate-cli cex unified account currencies
• gate-cli cex unified loan interest
• gate-cli cex unified loan records
• gate-cli cex wallet balance total

Execution Operations (Write)

• gate-cli cex unified loan create
• gate-cli cex unified config collateral
• gate-cli cex unified mode set
• gate-cli cex unified config leverage-set

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: Alpha:Read, Earn:Read, Fx:Read, Margin:Read, Options:Read, Rebate:Read, Spot:Read, Tradfi:Read, Unified:Write, Wallet: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 module routing in this skill.

• SKILL.md keeps orchestration/routing logic across account domains.
• references/gate-cli.md is the authoritative gate-cli execution contract for module aggregation, partial degradation strategy, and unified mutation safeguards.

Sub-Modules

Note: TradFi tools (from gate-exchange-tradfi, 10 read tools) are all read-only and used for asset inventory queries. They are included in the deduplicated 58-tool count but not listed as a separate L1 module in the sub-module table above.

Routing Rules

Design Principle

User queries often span multiple dimensions (e.g. "check my earn interest and will I get liquidated" covers S3 and S2). Instead of forcing single-intent classification, this skill uses signal overlay: each of 5 signal dimensions is independently detected from the query, and the activated dimensions contribute their respective tool sets. The final tool set is the union of all activated signals, deduplicated before execution.

Signal Dimension Definitions

Routing Flow

Input: User Query
Output: activated_signals[] + params{action_type, accounts[]}

1. Parameter Extraction
 Extract accounts[] (account types mentioned, 0-N)
 Extract action_type (borrow / transfer / add margin / setting / none)

2. Signal Detection (each dimension independent, non-exclusive, multi-select)
 S1 <- contains asset/balance/account/inventory expressions
 S2 <- contains liquidation/margin/position/risk expressions
 S3 <- contains earn/staking position/interest/rewards expressions
 S4 <- contains rebate/affiliate/commission/partner expressions
 S5 <- contains borrow/transfer/add-margin/setting expressions AND execution intent

3. Fallback Rules (if no signal explicitly activated)
 Vague account intent (e.g. "check my account") -> default S1 (asset overview)
 Account + risk keywords (e.g. "is it safe") -> default S1 + S2

4. Execution Mode
 S5 not activated -> read-only mode (query and summarise)
 S5 activated -> read+write mode (query -> Action Draft -> confirm -> execute)

5. Tool Set Assembly
 Tool Set = Union(all activated signal tool subsets)
 Deduplicate same tool + same parameters
 Independent tools run in parallel; S5 write operations run serially after reads

External Routing (Out of Scope)

Routing Example Table

L1/L2 Coexistence Strategy

Some user queries can be satisfied by a single L1 skill's tools (e.g. "how much do I have" only needs a few assets tools). This L2 provides a more comprehensive aggregated report through cross-L1 orchestration.

• Recommended strategy: All "account/asset/risk" requests enter this L2 as a unified entry point. If the sub-intent only needs a single L1's tool set, call that subset only and output normally (short-circuit optimisation).
• Principle: Unified entry ensures consistent user experience for all account/asset/risk queries; internally call 1-N tools as needed without forcing full orchestration.

Mixed Intent Handling

When a user query contains both account/risk intent and other L2 intents (e.g. "check my account, then buy BTC"):

1. Split into two segments: account/risk part is handled by this skill and output conclusions
2. Trading/research part routes to the corresponding L2 (trading copilot / market research), each executes independently
3. Example: "Check my account, then buy some BTC" -> this skill completes asset overview -> prompts "trading part has been routed to trading copilot"

Edge Case Handling

Execution

Read-Only Scenarios (S1-S4, no S5)

1. Activate signal dimensions from user query
2. Assemble deduplicated tool set from all activated dimensions
3. Execute all tools in parallel (no serial dependencies)
4. LLM aggregates multi-source results, annotates data timestamp and source
5. Output structured report per activated dimension

Write Scenarios (S5 activated)

1. Phase 1 (Parallel Read): Execute S1/S2 tools to get current account state
2. LLM evaluates feasibility and generates Action Draft (follow G. Write operation grading: medium-risk = risk note + irreversibility for mode switch; high-risk borrow/repay = amount + currency + rate)
3. Present Action Draft to user with key parameters and risk notes
4. Wait for explicit user confirmation (Y/N)
5. Phase 2 (Execute): Submit write tool call only after confirmation
6. Output execution result

Tool Deduplication Rules

• Same tool + same parameters within one request: execute once, reuse result for multiple aggregation steps
• Example: gate-cli cex unified account get needed by both S1 and S2 only executes once

gate-cli command index

Full Deduplicated Tool Inventory (58 tools: 54 read + 4 write)

Assets Domain (11 tools, all read)

Unified Account Domain (14 tools, 10 read + 4 write)

SimpleEarn Domain (5 tools, all read)

Staking Domain (4 tools, all read)

Market Analysis Domain (12 tools, all read)

Futures Positions (1 tool, read)

Affiliate Domain (7 tools, all read)

Alpha Domain (4 tools, all read)

Domain Knowledge

Key Value Propositions

• Single-query visibility into "where is my money, earn/affiliate snapshots, will I get liquidated" without multi-page navigation (does not produce asset weekly reports, total PnL ledger, or idle fund allocation plans)
• 58 tool calls orchestrated by scenario with parallel/serial awareness; conclusions and data sources are traceable
• Write operations (borrow/settings) require mandatory confirmation; zero risk of accidental execution; read operations are fully parallelised for fast response
• All tools require API Key authentication; data is limited to the authenticated user's own view

Target Users

• Active traders with open positions who need a quick asset overview
• Users concerned about asset security and risk control (margin, liquidation)
• Users who periodically review earn/staking yields and affiliate commission summaries
• Advanced users who utilise unified-account borrowing, leverage, and collateral features

Key Constraints

• This skill covers main account only; sub-account management is out of scope.
• Margin ratio and liquidation price calculations are reference values; always note "subject to the exchange's actual liquidation rules."
• Asset data has snapshot latency; always annotate the data timestamp in output.
• Borrowing incurs interest; users must assess their own repayment capacity.
• Asset data is limited to the user's own view and must not be leaked to other contexts.
• When a query returns no meaningful business data (empty list, no records), do not list or emphasise cex_* tool names in user-facing output; use natural language like "no records found" instead.

Capability Boundaries (What This Skill Does NOT Do)

• Does NOT execute trades (spot/futures open/close) — route to trading copilot
• Does NOT perform coin research, market analysis, or news — route to market research
• Does NOT recommend earn products or handle subscriptions — route to smart earn
• Does NOT manage sub-accounts
• Does NOT produce asset weekly reports or cross-period asset analysis (API limitation)
• Does NOT produce a total PnL ledger across all business lines (inconsistent data sources)
• Does NOT provide idle fund allocation advice or product comparison — route to smart earn

Unified account estimated borrow rate (gate-cli cex unified query estimate-rate)

• Semantics (Gate API): The tool returns estimated borrow interest rates for the current hour, per currency, as string decimals (e.g. "0.000002"). This matches the public API contract: hourly estimate, not a fixed annual quote.
• User-facing output: Always state that the value is a hourly estimated rate (or equivalent). Do not present the raw number as annualized APR/APY unless you perform an explicit conversion and label it clearly as a reference only (e.g. simple scaling: hourly × 24 × 365 — actual accrual follows platform rules).
• Distinction: SimpleEarn tools such as gate-cli cex earn uni rate expose product APY-style figures; they are a different product line from unified-account borrow estimates. Do not mix units in one sentence without naming each source.

Common Misconceptions

Affiliate / rebate data (S4)

• gate-cli cex rebate user-info may return an empty object. You can still build a meaningful S4 report from gate-cli cex rebate partner commissions (and other S4 read tools such as partner sub list and transaction history). Empty user_info does not mean there is no commission data.
• Source of truth for commission flows: gate-cli cex rebate partner commissions returns historical commission rows. commissionAsset is commonly USDT or POINT; rows may also carry a source dimension such as FUTURES, SPOT, TradFi, or ALPHA (names as returned by the API).
• No fabricated lifetime rebate totals: When user_info does not expose a ready-made cumulative rebate figure, do not invent a single "total rebate" number. To state aggregate USDT and POINT from history alone, you must page through the full history (use the API's offset/limit parameters, e.g. limit 100 per request), repeat until no more rows, then sum commissionAmount grouped by commissionAsset. If the session has not completed all pages, state that explicitly and do not guess totals.
• Official totals: Direct users to the Gate App or Web partner or rebate center for authoritative cumulative figures if they need a single official number without full pagination in the session.
• Optional follow-up: If the user asks, you may offer to continue pagination for rebate only and report USDT total and POINT total from commission history. Do not add those rebate totals to SimpleEarn, staking, or other yield sections (no cross-section "total income" mixing).

Reference Documents

• gate-runtime-rules.md — Exchange runtime rules (precision, price limits), referenced before executing borrow operations

Note: Unified account specifications (margin ratio calculation, borrowing rules, mode switching constraints) are embedded in the Domain Knowledge and Safety Rules sections of this SKILL.md. For detailed unified-account rules, refer to the gate-exchange-unified L1 skill.

Safety Rules

G. Write Operation Confirmation Mechanism and Safety Rules

Category: Strong confirmation · Action Draft — All unified-account mutations below use an Action Draft plus an explicit user confirmation in the immediately preceding turn. There is no silent execution.

Write operation grading (by risk level)

Implementation notes

• gate-cli cex unified query estimate-rate: Treat returned rates as hourly estimates when quoting to the user or filling Action Drafts (see Domain Knowledge: Unified account estimated borrow rate).
• Medium vs High: Medium-risk tools still use an Action Draft; the difference is emphasis — medium-risk settings require a concise risk tip (and irreversibility when switching mode). High-risk lending requires the financial fields (amount, currency, rate) to be explicit in the draft before confirmation.
• One tool per confirmation batch if parameters differ; do not bundle unrelated writes under one generic “OK”.

User Confirmation Requirement

All write operations require explicit user confirmation before execution. The confirmation flow is:

1. Action Draft: Present operation type, target, parameters, estimated impact, and risk note (see grading table above for medium vs high content)
2. Wait for Confirmation: User must reply with explicit approval (Y / Confirm)
3. Execute: Submit write tool call only after approval
4. Single-use: Confirmation is consumed after one use; parameter changes require re-confirmation
5. Per-step: Multi-step write operations require confirmation for each step separately

Write Operation Classification (summary)

No-Confirmation Guard

Without explicit user confirmation, no write operation is executed. Only read and query operations are allowed.

Stale Confirmation Handling

If parameters change after confirmation (different currency, amount, or operation type), the previous confirmation is invalidated and a new Action Draft must be presented.

Hard Blocking Rules

• NEVER call mutation tools without explicit confirmation from the immediately previous user turn
• NEVER guess parameters; if amount, currency, or direction is missing, ask the user
• NEVER fabricate data; if a tool call fails, degrade gracefully and note "data temporarily unavailable"
• Liquidation warnings are reference values only; always state "subject to the exchange's actual rules"

Error Handling

Risk Disclaimers

• Digital asset trading involves significant risk and may result in partial or total loss of your investment.
• Leveraged trading (futures, margin, options, delivery contracts) may result in losses exceeding your initial margin. Small market movements can cause total margin loss.
• The above is for informational purposes only and does not constitute investment, financial, tax, or legal advice.
• AI-assisted outputs are for general information only and do not constitute any representation, warranty, or guarantee by Gate.
• Users must comply with the laws and regulations of their jurisdiction. Gate services may not be available in restricted regions.

Report Template

Read-Only Report

## Account and Asset Risk Report

| Dimension | Status |
|-----------|--------|
| Data Timestamp | {timestamp} |
| Activated Signals | {S1/S2/S3/S4} |

### S1 Asset Overview (if activated)
{asset_panorama_table}

### S2 Risk and Margin (if activated)
{margin_and_position_risk_table}
Note: Liquidation prices and margin ratios are reference values. Subject to the exchange's actual liquidation rules.

### S3 Earn Snapshot (if activated)
{simpleearn_and_staking_summary}

### S4 Affiliate Report (if activated)
{rebate_and_commission_summary}
Note: If `gate-cli cex rebate user-info` is empty, rely on `gate-cli cex rebate partner commissions` (and other S4 tools). Do not fabricate lifetime USDT/POINT totals unless all history pages were fetched and summed by `commissionAsset`. Point to App/Web partner center for official cumulative figures when appropriate.

Write Operation Report

Medium-risk settings (set_unified_mode, set_user_leverage_currency_setting, set_unified_collateral):

## Action Draft (medium-risk · strong confirmation)

| Item | Value |
|------|-------|
| Operation | {set collateral / set leverage / switch unified mode} |
| Target | {currency / mode / leverage value} |
| Amount or config | {as applicable} |
| Risk warning | {e.g. impact on margin; if mode switch: **this change is irreversible**} |

Reply **Y** to confirm or **N** to cancel.

High-risk lending (create_unified_loan — borrow or repay):

## Action Draft (high-risk · strong confirmation)

| Item | Value |
|------|-------|
| Operation | {borrow / repay} |
| Currency | {e.g. USDT} |
| Amount | {numeric amount} |
| Interest rate | {hourly estimated rate from `gate-cli cex unified query estimate-rate` / API; state **hourly** — not APR unless explicitly converted and labeled reference-only} |
| Risk warning | {e.g. interest accrual, repayment obligation} |

Reply **Y** to confirm or **N** to cancel.

Cross-Skill Workflows

Workflow A: Check Risk Then Add Margin

1. This skill evaluates position risk (S2) and available spot balance (S1)
2. If margin is insufficient, generate add-margin Action Draft (S5)
3. After confirmation, execute collateral setting

Workflow B: Check Borrowable Then Borrow

1. This skill queries borrowable limit and estimated rate (S1 inquiry subset)
2. If user confirms borrow intent, activate S5 and generate borrow Action Draft
3. After confirmation, execute borrow; if user wants to trade, route to trading copilot