| name | gate-exchange-flashswap-assistant |
| description | L2 flash swap orchestration: fc preview and create (1:1, 1:N, N:1), spot balance checks, min/max gates, optional dust-to-GT, order history. Use this skill whenever the user wants flash swap, instant convert, consolidate alts to one coin, split one asset into several via flash, diagnose below-minimum flash size, or convert wallet dust to GT. Trigger phrases include "flash swap", "flash convert", "swap to USDT", "consolidate to USDT", "dust to GT", "small balance to GT", or "flash swap history". |
| user-invocable | true |
| disable-model-invocation | false |
| metadata | {"openclaw":{"emoji":"💱","os":["darwin","linux"],"primaryEnv":"GATE_API_KEY","requires":{"bins":"[Truncated]","env":"[Truncated]"},"install":["[Truncated]","[Truncated]","[Truncated]","[Truncated]"]}} |
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-flashswap-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 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 flash-swap ordergate-cli cex flash-swap pairsgate-cli cex flash-swap ordersgate-cli cex flash-swap preview-many-to-onegate-cli cex flash-swap preview-one-to-manygate-cli cex flash-swap preview-v1gate-cli cex spot account getgate-cli cex wallet balance smallgate-cli cex wallet balance small-history
Execution Operations (Write)
gate-cli cex flash-swap create-many-to-onegate-cli cex flash-swap create-one-to-manygate-cli cex flash-swap create-v1gate-cli cex wallet balance convert-small
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.
- API Key Required: Yes (authenticated Gate Exchange MCP)
- Permissions: Flash convert write (
gate-cli cex flash-swap preview / create or preview-v1 / create-v1 / multi-currency variants; MCP cex_fc_* when using Exchange MCP), spot account read, wallet small-balance read and convert as required by the gateway (configure keys with least privilege)
- Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage
Installation Check
- Required: Gate (main);
gate-cli when using CLI-backed flows (install via setup.sh from this skill when applicable).
- Install (MCP / IDE): 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. 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 mutating flash-swap or small-balance calls, confirm the runtime works (e.g.
gate-cli --version or a read-only check appropriate to this skill).
Domain Knowledge
What this skill covers
- Flash swap (fc): Instant convert using preview then create. Three modes: one-to-one, one-to-many (one sell asset to multiple buy assets), many-to-one (multiple sell assets to one buy asset, consolidation).
- On-path balance checks: Use
gate-cli cex spot account get for the sell-side (and USDT side for one-to-many) only for this flow. Do not pull full portfolio views here.
- Two different “small balance” paths (must explain to the user):
- Flash swap: Subject to per-pair
sell_min_amount / sell_max_amount from gate-cli cex flash-swap pairs. If below minimum, do not call fc preview to fake a quote.
- Wallet dust → GT:
gate-cli cex wallet balance small / gate-cli cex wallet balance convert-small converts platform-classified dust to GT (not USDT). Rules differ from flash minima; never silently substitute this when the user asked for USDT flash swap.
Core concepts
- quote_id: From preview; required for create. Validity comes from
valid_timestamp in the response — never assume a fixed TTL.
- sell_amount / buy_amount: Use one per leg as required by the API; one-to-many can use per-target
sell_amount or buy_amount; many-to-one uses per-source sell_amount.
- Order status:
status=1 success, status=2 failure — verify after each create.
- Precision: Show tiny receive amounts with clear precision; optional rough fiat hint only when clearly justified.
Explicitly out of scope for tools in this skill
- Do not call
gate-cli cex spot market tickers, gate-cli cex spot market orderbook, or gate-cli cex wallet balance total from this skill. Market depth, “is it a good time”, and full asset audits belong to other skills (see Judgment Logic Summary).
Regulatory and risk notices
- Digital asset trading involves significant risk and may result in partial or total loss of your investment.
- This skill is intended for users aged 18 or above with full civil capacity. Users must comply with applicable laws in their jurisdiction.
- AI-assisted outputs and tool results are for general information only and do not constitute investment, financial, tax, or legal advice, or any representation or warranty by Gate.
- Prompts and trading-related inputs are processed to call the Gate API via MCP; do not collect unnecessary personal data.
Atomic Tool Call Chains (mandatory)
Execution rule: Map the user request to scenario #1–#21 below when possible. Follow the listed tool order. Do not skip gates (balance, sell_min_amount, preview before create).
Notation
[P1] Parallel: Invoke the listed tools in the same wave (any order among them is acceptable unless a later step depends on their output).→: Serial — complete the previous step before starting the next.[P0] Plan: No MCP call — parse amounts, split ratios, or restrict the coin set (e.g. user-supplied list only).[Confirm]: Present Action Draft; wait for explicit Y before any write tool in that branch.(W): Write tool — only after Confirm unless the scenario explicitly ends at preview-only.
Routing reminders (from spec)
- One-to-many rows #4, #5, #11: If the user uses only spot buy / market buy language with no flash swap / convert / swap anchor, route
gate-exchange-trading instead of fc tools.
- #8, #20: Preview-only until the user opts in to create.
- #21: Never mix dust→GT silently into a “swap to USDT” story without explaining the different product path.
Base scenarios (#1–#8)
| # | User intent (paraphrase) | Mode | Signal | Atomic chain |
|---|
| 1 | Swap a fixed amount (e.g. 1 BTC) to USDT | 1→1 | S1 | [P1] gate-cli cex flash-swap pairs(sell asset) · gate-cli cex spot account get(sell asset) → Check available ≥ sell amount and sell amount ≥ sell_min_amount → gate-cli cex flash-swap preview-v1(sell_asset, sell_amount, buy_asset) → Show rate, estimated receive, validity → Action Draft → [Confirm] → (W) gate-cli cex flash-swap create-v1(quote_id, matching amounts) → Verify status → Report result |
| 2 | Swap full available balance of one asset to USDT (e.g. take-profit SOL) | 1→1 | S1 | [P1] gate-cli cex spot account get(asset) · gate-cli cex flash-swap pairs(asset) → Set sell_amount = available; check ≥ sell_min_amount → gate-cli cex flash-swap preview-v1 → Action Draft → [Confirm] → (W) gate-cli cex flash-swap create-v1 → Verify status |
| 3 | After deposit, swap asset A to USDT | 1→1 | S1 | [P1] gate-cli cex spot account get(A) · gate-cli cex flash-swap pairs(A) → Confirm balance and min/max → gate-cli cex flash-swap preview-v1(A→USDT) → Action Draft → [Confirm] → (W) gate-cli cex flash-swap create-v1 → Verify status |
| 4 | One source (e.g. 3000 USDT) flash into multiple targets with set spend per target (e.g. 1000 USDT each to BTC, ETH, SOL) |
Extended scenarios (#9–#13)
| # | User intent (paraphrase) | Signal | Atomic chain |
|---|
| 9 | Whether a coin (e.g. APT) supports flash swap / pair limits | S4 | [P1] gate-cli cex flash-swap pairs(currency) → If empty: not supported; suggest spot trading skill → If rows: show pairs and min/max |
| 10 | Did the latest flash swap succeed | S4 | [P1] gate-cli cex flash-swap orders(limit=1) → Take newest order_id → gate-cli cex flash-swap order(order_id) → Report status (1 success / 2 fail), fills |
| 11 | USDT flash into target buy amounts (e.g. 0.1 BTC and 1 ETH) | S2 | [P0] Build params with buy_amount per leg (not sell_amount) → [P1] gate-cli cex spot account get(USDT) · gate-cli cex flash-swap pairs(each target) → gate-cli cex flash-swap preview-one-to-many → Check total USDT consumed vs available (e.g. total_consume_amount or equivalent field) → Action Draft per leg → [Confirm] → (W) gate-cli cex flash-swap create-one-to-many → Verify each status |
| 12 | One-to-one non-USDT leg (e.g. 2 ETH → BTC) | S1 | [P1] gate-cli cex spot account get(ETH) · gate-cli cex flash-swap pairs(ETH) → Check ≥ amount and min/max → gate-cli cex flash-swap preview-v1(sell ETH, buy BTC, …) → Action Draft (state single-hop flash, not “via USDT”) → [Confirm] → (W) gate-cli cex flash-swap create-v1 → Verify status |
|
Dust, small size, and split scenarios (#14–#21)
| # | User intent (paraphrase) | Signal | Atomic chain |
|---|
| 14 | “Too small” / may be below flash min (e.g. PEPE) | S5 | [P1] gate-cli cex flash-swap pairs(asset) · gate-cli cex spot account get(asset) → If available < sell_min_amount: do not call gate-cli cex flash-swap preview (or any preview variant); show balance / min / gap → gate-cli cex wallet balance small → If asset in dust list: explain S7 dust→GT path; else suggest accumulate or spot sell (trading copilot) → If available ≥ min: continue scenario #1-style S1 chain |
| 15 | Small total one-to-many (e.g. 30 USDT split across DOGE and SHIB) | S2 | [P0] Confirm per-leg USDT split with user if unclear → [P1] gate-cli cex spot account get(USDT) · gate-cli cex flash-swap pairs(each target) → Ensure each leg ≥ sell_min_amount; if not, ask to adjust → gate-cli cex flash-swap preview-one-to-many → Highlight failed legs; Action Draft → [Confirm] → (W) gate-cli cex flash-swap create-one-to-many(confirmed params) |
| 16 | Single-asset amount exceeds sell_max_amount (must split batches) | S6 | [P1] gate-cli cex spot account get(asset) · gate-cli cex flash-swap pairs(asset) → Read sell_max_amount; plan batches each ≤ max → For batch k: gate-cli cex flash-swap preview-v1 → Action Draft → [Confirm] → (W) gate-cli cex flash-swap create-v1 → Verify status → Re-query gate-cli cex spot account get before batch k+1 New preview (new ) for next batch |
Workflow
Step 1: Route intent and select signal S1–S7
First, try to match Atomic Tool Call Chains scenario #1–#21 and execute that chain as written (parallel vs serial, preview gates, confirm before writes).
If no row fits, fall back: classify the request. If it belongs to out of scope (see Judgment Logic Summary), stop and name the appropriate skill without calling fc or wallet convert tools.
If in scope but not tabulated, assign one or more signals: S1 one-to-one flash, S2 one-to-many flash, S3 many-to-one consolidation, S4 query or history, S5 below-minimum or dust diagnosis, S6 split over sell_max_amount, S7 dust to GT.
Key data to extract:
signal: S1 | S2 | S3 | S4 | S5 | S6 | S7 (combinations allowed, e.g. S5 then S1)sell_assets, buy_asset, amounts, and whether the user asked for preview onlyuser_confirmed_flash_language: user used flash swap / convert / swap narrative vs pure spot buy wording (see routing table)
Step 2: Parallel gateway reads (flash paths S1–S3, S5, S6)
Call gate-cli cex flash-swap pairs with:
currency (or equivalent filter per MCP): each sell asset (and targets as needed)
Call gate-cli cex spot account get with:
- Parameters needed to read available balance for each relevant currency (sell side and USDT for one-to-many)
Key data to extract:
sell_min_amount, sell_max_amount per pairavailable balances- Whether each leg passes min gate before preview
S5 rule: If available < sell_min_amount for a flash leg, do not call gate-cli cex flash-swap preview (or any preview variant) for that leg. Present a clear table (balance vs min gap) and optionally call gate-cli cex wallet balance small to see if S7 applies.
S6 rule: If amount > sell_max_amount, plan sequential batches; each batch needs its own preview, Action Draft, Y, create, and post-create balance refresh before the next preview. Cap planned batches at a reasonable maximum (for example 20) or stop if the user cancels — do not loop without bound.
Step 3: Preview (choose one preview tool by mode)
One-to-one (S1) — Call gate-cli cex flash-swap preview-v1 with sell_asset, buy_asset, and either sell_amount or buy_amount.
One-to-many (S2) — Call gate-cli cex flash-swap preview-one-to-many with params array (per leg amounts). Highlight per-leg preview errors.
Many-to-one (S3) — After filtering legs below min or zero balance, call gate-cli cex flash-swap preview-many-to-one with params for remaining legs. Present will execute vs skipped summary.
Key data to extract:
quote_id per successful leg- Rates, receive amounts,
valid_timestamp
- Any per-leg errors for user-visible highlighting
Step 4: Action Draft and explicit confirmation (all writes)
Present an Action Draft listing sell/buy assets, amounts, effective rate or receive estimate, quote validity, and multi-leg status. For S7, the draft must state that the operation is dust to GT via gate-cli cex wallet balance convert-small, not USDT flash swap.
Wait for explicit Y to execute or N to cancel. Without Y, call no write tool.
Key data to extract:
user_confirmation: Y | N- Whether parameters still match the last preview (if not, re-preview)
Step 5: Execute flash swap creates (after Y, one create family per request)
Use exactly one of:
Call gate-cli cex flash-swap create-v1 with body fields including quote_id and matching sell/buy amounts from preview.
Call gate-cli cex flash-swap create-one-to-many with params including each leg quote_id and amounts — exclude failed preview legs.
Call gate-cli cex flash-swap create-many-to-one with params including each leg quote_id and amounts — exclude failed preview legs.
Key data to extract:
- Per-order
status and IDs
- Errors returned by the API
Step 6: Verify order outcome
For each created order, read status. If needed, Call gate-cli cex flash-swap order with the order id to confirm details.
Key data to extract:
- Success vs failure per leg
- Final received amounts where provided
Step 7: Query and history paths (S4)
Call gate-cli cex flash-swap orders with appropriate limit / filters for history or “latest order”.
Call gate-cli cex flash-swap order with order_id when the user needs detail on a specific id or you took the latest id from list.
For supported-pair or min/max questions, use gate-cli cex flash-swap pairs and gate-cli cex spot account get as needed.
For dust history, Call gate-cli cex wallet balance small-history with optional filters per MCP.
Key data to extract:
- Human-readable table: time, sides, amounts, status
Step 8: Dust to GT path (S7)
Call gate-cli cex wallet balance small (no substitute for “list all account dust” beyond this tool’s contract).
Present the convertible list. Action Draft must specify currencies or is_all exactly as the user confirmed.
After Y, Call gate-cli cex wallet balance convert-small with the confirmed parameters.
Key data to extract:
- Conversion result or error; optional follow-up with
gate-cli cex wallet balance small-history
Judgment Logic Summary
Signal definitions
| Signal | Meaning | Primary tools |
|---|
| S1 | One-to-one flash | gate-cli cex flash-swap pairs, gate-cli cex spot account get, gate-cli cex flash-swap preview-v1, gate-cli cex flash-swap create-v1 |
| S2 | One-to-many flash (user anchors flash/convert/swap, not pure spot buy) | gate-cli cex flash-swap preview-one-to-many, gate-cli cex flash-swap create-one-to-many |
| S3 | Many-to-one consolidation | gate-cli cex flash-swap preview-many-to-one, gate-cli cex flash-swap create-many-to-one |
| S4 | Queries: history, support, min check, order status | gate-cli cex flash-swap orders, gate-cli cex flash-swap order, gate-cli cex flash-swap pairs, gate-cli cex wallet balance small-history |
| S5 | Below flash minimum / fragile balance | Reads only until min met; optional gate-cli cex wallet balance small → offer S7 |
| S6 | Amount over sell_max_amount | Same create family as S1/S2/S3 but sequential batches with fresh preview and confirmation per batch |
| S7 | Dust to GT | gate-cli cex wallet balance small, gate-cli cex wallet balance convert-small |
Out of scope routing (do not use this skill’s tool list)
| User intent | Route to |
|---|
| Research, “why”, slippage, depth, liquidity, charts | gate-info-research or gate-exchange-trading (no tickers/order book from here) |
| Spot buy/sell narrative (market/limit, “buy some”, “DCA”, “bid”) without flash/convert anchor | gate-exchange-trading |
| Futures / margin trading | gate-exchange-trading or domain futures/margin skills |
| Transfers between accounts (spot ↔ futures, subaccounts) | gate-exchange-transfer |
| Full portfolio, margin risk, liquidation context | gate-exchange-assets-manager or gate-exchange-assets |
| Earn / staking | gate-exchange-simpleearn or relevant earn skill |
| On-chain DEX swap | DEX skills (e.g. gate-dex-trade) |
Mode detection
- One-to-one: One sell asset and one buy asset; no multi-asset split wording.
- One-to-many: One sell asset, multiple buy assets; user must anchor flash swap / convert, not only “buy multiple”.
- Many-to-one: Multiple sell assets into one buy asset, or words like “consolidate”, “convert all to USDT”.
- If unclear: ask whether the user wants one source → many targets or many sources → one target.
Report Template
Flash swap Action Draft (before any fc create)
- Mode (one-to-one / one-to-many / many-to-one)
- Each leg: sell asset and amount → buy asset and expected receive (from preview)
- Quote validity: reference
valid_timestamp (do not invent seconds)
- Risk line: instant execution; final result from API
- Ask: Reply Y to execute or N to cancel
S5 diagnostic (no preview)
- Asset, available balance,
sell_min_amount, shortfall
- Next options: accumulate, spot trade via trading copilot, or check dust list for GT path (S7)
Dust to GT Action Draft
- Explicit: operation is small balance convert to GT, not USDT flash
- Coins or
is_all exactly as user confirmed
- Y / N
After execution
- Per-leg status and amounts
- Reminder: digital asset transactions are generally irreversible; flash fills are immediate
Safety Rules
Confirmation
- No
gate-cli cex flash-swap create (or create-v1 / multi-currency create variants) and no gate-cli cex wallet balance convert-small without prior Action Draft and explicit Y.
- Never use an expired or stale
quote_id; if the user delayed, re-preview.
- Never call fc preview solely to mask a below-minimum balance.
Proportionality
- Pass only minimum parameters to MCP tools. Do not send unrelated conversation content as tool input.
Error Handling
| Situation | Action |
|---|
gate-cli cex flash-swap pairs fails | State limits unknown; warn before preview; avoid guessing min/max |
| Preview returns error | Do not create; show message; suggest adjusting size or spot path |
| Create returns failure | Do not auto-retry; suggest fresh preview |
gate-cli cex spot account get fails | Warn balance unknown; do not invent balances |
gate-cli cex wallet balance small fails | Do not call convert; explain dust list unavailable |
gate-cli cex wallet balance convert-small fails | Show error; no silent retry |
| User says N after draft | Stop; no writes |
Reference
- Normative tool order for mapped stories: Atomic Tool Call Chains (scenarios #1–#21) above
- Human-readable scenarios and prompt examples:
references/scenarios.md
- Shared disambiguation: read
gate-skills-disambiguation.md from your skills root when present
