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 Spot Trading 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

This skill depends on the gate-cli binary and the documented subcommands below. Command strings align with gate-cli/cmd/cex/GATE_EXCHANGE_SKILLS_MCP_TO_GATE_CLI.md.

• Before any gate-cli invocation: ensure gate-cli is installed. Let GATE_CLI_BIN="${GATE_OPENCLAW_SKILLS_BIN:-$HOME/.openclaw/skills/bin}/gate-cli". If [ ! -x "$GATE_CLI_BIN" ] (and command -v gate-cli also fails if you rely on PATH), run setup.sh (e.g. sh ./setup.sh from this skill directory), then re-check. Do not continue with trading or account reads that require auth until gate-cli runs successfully (e.g. gate-cli --version).
• No MCP servers are required for this skill; execution is gate-cli only.

gate-cli commands used

Query Operations (Read-only)

• gate-cli cex spot market currency
• gate-cli cex spot market pair
• gate-cli cex spot account get
• gate-cli cex spot account batch-fee
• gate-cli cex spot market candlesticks
• gate-cli cex spot market orderbook
• gate-cli cex spot price-trigger get
• gate-cli cex spot market tickers
• gate-cli cex spot account book
• gate-cli cex spot order my-trades
• gate-cli cex spot order list
• gate-cli cex spot price-trigger list
• gate-cli cex wallet market trade-fee

Execution Operations (Write)

• gate-cli cex spot order batch-amend
• gate-cli cex spot order amend
• gate-cli cex spot order cancel
• gate-cli cex spot order batch-cancel
• gate-cli cex spot price-trigger cancel
• gate-cli cex spot price-trigger cancel-all
• gate-cli cex spot order batch-create
• gate-cli cex spot order buy / gate-cli cex spot order sell
• gate-cli cex spot price-trigger create

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: Spot:Write, Wallet:Read on the key used by gate-cli.
• Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

Installation Check

• Required: gate-cli (install via setup.sh when missing, per Skill Dependencies).
• GateClaw / OpenClaw: setup.sh installs to $HOME/.openclaw/skills/bin/gate-cli by default; add that directory to PATH if agents invoke gate-cli by name.
• 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 for the setup (e.g. gate-cli cex spot market tickers); confirm credentials resolve before trades.

Execution mode

Read and strictly follow references/gate-cli.md, then execute this skill's routing/case logic.

• SKILL.md remains the intent routing and scenario map.
• references/gate-cli.md is the authoritative execution contract for gate-cli usage, pre-checks, confirmation gates, and degraded handling.

Domain Knowledge

Tool Mapping by Domain

Key Trading Rules

• Use BASE_QUOTE format for trading pairs, for example BTC_USDT.
• Check quote-currency balance first before buy orders (for example USDT).
• Amount-based buys must satisfy min_quote_amount (commonly 10U).
• Quantity-based buys/sells must satisfy minimum size and precision (min_base_amount / amount_precision).
• Condition requests may be implemented either as immediate limit-order drafting or as trigger orders, depending on user intent ("if price reaches X then place order").
• Take-profit/stop-loss (TP/SL)-style requests are handled via spot price-trigger commands with explicit trigger and execution parameters.

Market Order Parameter Extraction Rules (Mandatory)

When calling gate-cli cex spot order buy / gate-cli cex spot order sell with type=market, fill amount by side:

Pre-check before execution:

• buy market order: verify quote-currency balance can cover amount (USDT).
• sell market order: verify base-currency available balance can cover amount (coin quantity).

Workflow

When the user asks for any spot trading operation, follow this sequence.

Step 1: Identify Task Type

Classify the request into one of these six categories:

1. Buy (market/limit/full-balance buy)
2. Sell (full-position sell/conditional sell)
3. Account query (total assets, balance checks, tradability checks)
4. Order management (list open orders, amend, cancel)
5. Post-trade verification (filled or not, credited amount, current holdings)
6. Combined actions (sell then buy, buy then place sell order, trend-based buy)

Step 2: Extract Parameters and Run Pre-checks

Extract key fields:

• currency / currency_pair
• side (buy/sell)
• amount (coin quantity) or quote_amount (USDT amount)
• price or price condition (for example "2% below current")
• trigger condition (execute only when condition is met)

When type=market, normalize parameters as:

• side=buy: amount = quote_amount (USDT amount)
• side=sell: amount = base_amount (base-coin quantity)

Pre-check order:

1. Trading pair/currency tradability status
2. Minimum order amount/size and precision
3. Available balance sufficiency
4. User condition satisfaction (for example "buy only below 60000")

Step 3: Final User Confirmation Before Any Order Placement (Mandatory)

Before every gate-cli cex spot order buy / gate-cli cex spot order sell, gate-cli cex spot order batch-create, or gate-cli cex spot price-trigger create, always provide an Order Draft first, then wait for explicit confirmation.

Required execution flow:

1. Send order draft (no trading call yet)
2. Wait for explicit user approval
3. Only after approval, submit the real order
4. Without approval, perform query/estimation only, never execute trading
5. Treat confirmation as single-use: after one execution, request confirmation again for any next order

Required confirmation fields:

• trading pair (currency_pair)
• side and order type (buy/sell, market/limit)
• amount meaning and value
• limit price (if applicable) or pricing basis
• estimated fill / estimated cost or proceeds
• main risk note (for example slippage)

Recommended draft wording:

• Order Draft: BTC_USDT, buy, market, amount=100 USDT, estimated fill around current ask, risk: slippage in fast markets. Reply "Confirm order" to place it.

Allowed confirmation responses (examples):

• Confirm order, Confirm, Proceed, Yes, place it

Hard blocking rules (non-bypassable):

• NEVER call gate-cli cex spot order buy / gate-cli cex spot order sell, gate-cli cex spot order batch-create, or gate-cli cex spot price-trigger create unless the user explicitly confirms in the immediately previous turn.
• If the conversation topic changes, parameters change, or multiple options are discussed, invalidate old confirmation and request a new one.
• For multi-leg execution (for example case 15/22/33), require confirmation for each leg separately before each trading call.

If user confirmation is missing, ambiguous, or negative:

• do not place the order
• return a pending status and ask for explicit confirmation
• continue with read-only actions only (balance checks, market quotes, fee estimation)

Step 4: Run commands by scenario

Use only the minimal gate-cli command set required for the task:

• Balance and available funds: gate-cli cex spot account get
• Rule validation: gate-cli cex spot market pair
• Live price and moves: gate-cli cex spot market tickers
• Order placement: gate-cli cex spot order buy / gate-cli cex spot order sell / gate-cli cex spot order batch-create
• Trigger-order placement/query/cancel: gate-cli cex spot price-trigger create / gate-cli cex spot price-trigger list / gate-cli cex spot price-trigger get / gate-cli cex spot price-trigger cancel / gate-cli cex spot price-trigger cancel-all
• Cancel/amend: gate-cli cex spot order cancel / gate-cli cex spot order batch-cancel / gate-cli cex spot order amend / gate-cli cex spot order batch-amend
• Open order query: gate-cli cex spot order list (use status=open)
• Fill verification: gate-cli cex spot order my-trades
• Account change history: gate-cli cex spot account book
• Batch fee query: gate-cli cex spot account batch-fee

Step 5: Return Actionable Result and Status

The response must include:

• Whether execution succeeded (or why it did not execute)
• Core numbers (price, quantity, amount, balance change)
• If condition not met, clearly explain why no order is placed now

Case Routing Map (1-36)

A. Buy and Account Queries (1-8)

B. Smart Monitoring and Trading (9-16)

C. Order Management and Amendment (17-25)

D. Advanced Spot Utilities (26-31)

E. Trigger Orders and TP/SL Automation (32-36)

Judgment Logic Summary

Report Template

## Execution Result

| Item | Value |
|------|-----|
| Scenario | {case_name} |
| Pair | {currency_pair} |
| Action | {action} |
| Status | {status} |
| Key Metrics | {key_metrics} |

{decision_text}

Example decision_text:

• ✅ Condition met. Your order has been placed.
• 📝 Order draft ready. Reply "Confirm order" to execute.
• ⏸️ No order placed yet: current price is 60200, above your target 60000.
• ❌ Not executed: minimum order amount is 10U, your input is 5U.

Error Handling

Cross-Skill Workflows

Workflow A: Buy Then Amend

1. Place order with gate-exchange-spot (Case 2/9/23)
2. If still unfilled, amend price (Case 17)

Workflow B: Cancel Then Rebuy

1. Cancel all open orders to release funds (Case 6)
2. Re-enter with updated strategy (Case 1/2/9)

Safety Rules

• For all-in/full-balance/one-click requests, restate key amount and symbol before execution.
• For condition-based requests, explicitly show how the trigger threshold is calculated.
• For TP/SL-style requests on spot, use the price-trigger workflow in this skill; do not imply unsupported CEX features—draft trigger legs and confirm before gate-cli cex spot price-trigger create.
• Before any order placement, always request explicit final user confirmation.
• Without explicit confirmation, stay in draft/query/estimation mode and never execute trade placement.
• Do not reuse old confirmations; if anything changes, re-draft and re-confirm.
• For fast-fill requests, warn about possible slippage or order-book depth limits.
• For chained actions (sell then buy), report step-by-step results clearly.
• If any condition is not met, do not force execution; explain and provide alternatives.