@coinbase/coinbase-cli 0.0.4 → 0.0.6

package/dist/version.txt

@@ -1 +1 @@
-0.0.4
+0.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coinbase/coinbase-cli",
-  "version": "0.0.4",
+  "version": "0.0.6",
   "description": "Coinbase for agents — CLI and MCP server for trading, wallets, payments, and onchain across the Coinbase platform",
   "type": "module",
   "bin": {

package/skills/coinbase-futures/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: coinbase-futures
+description: Places and manages CFM dated futures orders on Coinbase Advanced Trade — liquidation risk. Use when the user wants to open a dated futures position, or asks about liquidation risk. Uses the same `coinbase orders`/`coinbase portfolios` commands as spot (see `coinbase-trading`). These are real orders — losses can occur.
+requires: coinbase env configured with Trade permission (see `coinbase` skill)
+---
+
+# coinbase-futures
+
+CFM dated futures orders use the same `coinbase orders create` / `orders preview` commands as spot (see `coinbase-trading` for the shared market/limit/stop_limit mechanics and order-management commands). This skill covers what's different for CFM.
+
+**Portfolio scope**: CFM dated futures are documented as available only in the caller's default portfolio for now. Pass the default portfolio_uuid (equal to the user's UUID — see `coinbase-trading`) rather than a named sub-portfolio for any futures order.
+
+**Product IDs**: `<BASE>-<DDMMMYY>-CDE`, e.g. `BIT-28AUG26-CDE` (Bitcoin) or `BIP-20DEC30-CDE` (a separate Bitcoin-linked contract series — note the ticker root is `BIP`, not `BTC`). These roll to a new contract code every cycle — don't hardcode a date-coded ticker long-term; discover the live one with `coinbase products list product_type=FUTURE` and filter by the `-CDE` suffix.
+
+## Market orders: `base_size` only, and can fail after acceptance
+
+Futures market orders **must use `base_size`** (number of contracts) — `quote_size` is rejected with `"Futures market orders must be parameterized in base (number of contracts)"`. A market order can also be accepted (an `order_id` is returned) and then transition to `FAILED` asynchronously — not something the CLI can detect at submission time. For a reliable, immediate-fill order, prefer an IOC limit at/above the ask (buy) or at/below the bid (sell) instead of a plain market order:
+
+```sh
+coinbase orders create product_id=BIT-28AUG26-CDE side=BUY type=limit base_size=1 limit_price=65000 \
+  time_in_force=IOC
+```
+
+CFM's margin/leverage is fixed by the exchange per contract, not user-selectable per order — there's no `leverage`/`margin_type` param for orders.
+
+**Before placing an order, preview it and read back `predicted_liquidation_price`** — check current position risk from `portfolios get` alongside it, and confirm with the user if margin looks tight:
+
+```sh
+coinbase orders preview product_id=BIT-28AUG26-CDE side=BUY type=limit base_size=1 limit_price=65000
+```
+
+## Checking liquidation risk
+
+`coinbase portfolios get <portfolio_uuid>` includes `futures_positions` alongside spot.
+
+```sh
+coinbase portfolios get <portfolio_uuid> --jq '.futures_positions'
+```
+
+## Everything else
+
+Sizing (`quote_size`/`base_size`), order types, preview, edit, cancel, and fills work exactly as for spot — see `coinbase-trading`. `reduce_only` is not yet supported for CFM orders through this tool.

package/skills/coinbase-market-data/SKILL.md

@@ -48,4 +48,4 @@ coinbase products list --jq '.products[].product_id' --paginate
 ## Notes
 
 - For streaming/conditional reads ("tell me when BTC > 65k"), use `coinbase-watch` (`--until`), not polling loops.
-- Market data is read-only and does not place orders. To act on a price, hand off to `coinbase-trading`.
+- Market data is read-only and does not place orders. To act on a price, hand off to `coinbase-trading` (spot) or `coinbase-futures` (CFM dated futures).

package/skills/coinbase-portfolios/SKILL.md

@@ -25,6 +25,8 @@ coinbase portfolios edit <portfolio_uuid> name="Renamed"
 coinbase portfolios delete <portfolio_uuid>
 ```
 
+`portfolios get` includes `futures_positions` alongside spot for any portfolio holding CFM dated-futures positions — see `coinbase-futures` for placing futures orders and reading liquidation risk.
+
 ## The per-key scoping model
 
 Each CDP API key is scoped to ONE portfolio — the key can only trade within it. To operate across portfolios, register one env per portfolio using the `live-<portfolio>` convention:

package/skills/coinbase-trading/SKILL.md

@@ -8,6 +8,12 @@ requires: coinbase env configured with Trade permission (see `coinbase` skill)
 
 Place and manage spot orders. **These are REAL orders.** Confirm the full plan (product, side, size) with the user before placing.
 
+## Choosing the quote currency (USD vs USDC)
+
+The examples below use USD or USDC arbitrarily for illustration — always apply the rule below for real trades.
+
+Don't default to USD. If the user names a quote currency ("use my USDC"), use that pair. If they don't, check `coinbase balance` first and use whichever of USD/USDC they actually hold; if both, prefer USDC. If the pair you land on doesn't exist for that asset, say so instead of silently trying another one.
+
 ## Market orders
 
 Side determines which size field you use:
@@ -23,7 +29,7 @@ coinbase orders create product_id=BTC-USD side=BUY type=market quote_size=100
 # "Buy N USDC worth of <ASSET>" → BUY on <ASSET>-USDC with quote_size=N
 coinbase orders create product_id=BTC-USDC side=BUY type=market quote_size=1
 
-# Sell 0.5 ETH at market
+# Sell 0.5 ETH at market (USD used here for illustration only — apply the rule above)
 coinbase orders create product_id=ETH-USD side=SELL type=market base_size=0.5
 ```