@kaleidorg/mind 0.5.1 → 0.6.0

package/skills/channel-manager/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: channel-manager
+description: "Keep the Lightning node healthy: check node info, audit channels and liquidity, flush stuck RGB transfers, and (when allowed) buy inbound/asset channel capacity via the KaleidoSwap LSP. Triggers when the user asks about node health, channels, liquidity, or inbound capacity — and is the skill the scheduled 'heartbeat' loop runs."
+tools: rln_get_node_info, rln_list_channels, rln_get_balances, rln_list_assets, rln_refresh_transfers, kaleidoswap_lsp_get_info, kaleidoswap_lsp_estimate_fees, kaleidoswap_lsp_create_order, rln_pay_invoice
+triggers: node, channel, channels, liquidity, inbound, outbound, lsp, heartbeat, health, transfers, stuck
+metadata:
+  author: kaleidoswap
+  version: "0.1.0"
+---
+
+# Channel manager
+
+Keep the RGB Lightning node healthy and liquid. Read state every run; only buy
+capacity when the user allows it and it's actually needed.
+
+## Critical rules — these override everything else
+
+- **Diagnose before acting.** `rln_get_node_info` + `rln_list_channels` +
+  `rln_get_balances` first. Report what you see; don't guess.
+- **Respect `dry_run`.** When true, describe the action you *would* take (e.g.
+  "buy 1M sat inbound") but do NOT call `kaleidoswap_lsp_create_order` or
+  `rln_pay_invoice`.
+- **Buying capacity is a spend** — it routes through the host's risk gate. Never
+  propose one that breaches the BTC reserve, and always show the LSP fee
+  (`kaleidoswap_lsp_estimate_fees`) before recommending it.
+
+## Health checks (run in order)
+
+1. **Node up?** `rln_get_node_info` — pubkey, block height, synced.
+2. **Channels.** `rln_list_channels` — count, capacity, outbound vs inbound. Flag
+   any channel whose outbound is below the configured floor.
+3. **Stuck transfers.** `rln_refresh_transfers` to flush pending RGB transfers;
+   report anything still pending afterward.
+4. **Liquidity verdict.** If usable inbound (or an asset's inbound) is below the
+   threshold in the task parameters, that's the trigger to consider buying.
+
+## Buying capacity (only when needed + allowed)
+
+1. `kaleidoswap_lsp_get_info` — confirm the LSP is reachable + its limits.
+2. `kaleidoswap_lsp_estimate_fees` — show the fee for the size you'd buy.
+3. `kaleidoswap_lsp_create_order` (spend-gated) — create the order; it returns an
+   invoice/onchain address. Pay via `rln_pay_invoice` only after approval.
+
+## Scheduled (background) runs
+
+When run by the `heartbeat` loop, return STRICT JSON only:
+
+```
+{"task":"heartbeat","timestamp":"<ISO8601>","action":"ok|flush|buy_capacity|alert","dry_run":<bool>,"reason":"<why>","details":{"channels":<n>,"outbound_sat":<n>,"inbound_sat":<n>,"pending_transfers":<n>}}
+```
+
+Use `ok` when nothing needs doing, `alert` when a human should look.
+
+## Don'ts
+
+- Don't buy capacity that isn't needed, or when within the liquidity threshold.
+- Don't pay an LSP invoice when `dry_run` is true.
+- Don't invent channel ids, balances, or fees — read them from tools.
+- Don't breach the BTC reserve to open a channel.

package/skills/dca/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: dca
+description: "Dollar-cost-average a fixed budget into a target asset on a schedule. Reads the live quote and (when allowed) buys a small fixed slice via an atomic swap, respecting per-run allocation and risk limits. Triggers when the user mentions DCA, recurring buys, or averaging in — and is the skill a user-created DCA loop runs."
+tools: rln_get_balances, kaleidoswap_get_quote, kaleidoswap_atomic_init, kaleidoswap_atomic_execute, kaleidoswap_atomic_status, get_price
+triggers: dca, dollar cost average, recurring buy, average in, accumulate, stack
+metadata:
+  author: kaleidoswap
+  version: "0.1.0"
+---
+
+# Dollar-cost averaging
+
+Buy a fixed, small slice of a target asset each run. Boring on purpose: same
+size, every interval, regardless of price.
+
+## Critical rules — these override everything else
+
+- **Fixed slice only.** The per-run budget is the task's `allocation` — never
+  exceed it, never "catch up" by buying extra after a missed run.
+- **Respect `dry_run`.** When true, quote and report what you *would* buy; do NOT
+  execute.
+- **Respect risk + reserve.** A DCA buy is a spend; it passes through the host's
+  risk gate. Never breach the BTC reserve or the max single-spend limit.
+
+## Each run
+
+1. **Check funds.** `rln_get_balances` — is there enough BTC for one slice plus
+   the reserve? If not, return `action: "skip"` with the reason.
+2. **Quote.** `kaleidoswap_get_quote(BTC, <asset>, <slice>)`. Read the
+   `to_amount_display` / `fee_display` strings verbatim — no arithmetic.
+3. **Execute** (only when `dry_run` is false and within limits): the atomic swap
+   recipe drives `kaleidoswap_atomic_init` → `_execute`; then poll
+   `kaleidoswap_atomic_status`.
+
+## Scheduled (background) runs
+
+Return STRICT JSON only:
+
+```
+{"task":"<task id>","timestamp":"<ISO8601>","action":"buy|skip","dry_run":<bool>,"reason":"<why>","details":{"asset":"<asset>","slice":"<n>","received":"<display>","fee":"<display>"}}
+```
+
+## Don'ts
+
+- Don't vary the slice size or try to time the market — that's not DCA.
+- Don't buy when funds are below the reserve — `skip` instead.
+- Don't execute when `dry_run` is true.
+- Don't invent a quote — only the current `kaleidoswap_get_quote` result is real.

package/skills/kaleido-lsps/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: kaleido-lsps
 description: "Buy inbound Lightning channel capacity from a Lightning Service Provider (LSPS1). Quote a channel, estimate fees, place a channel order, and check order status. Triggers when the user wants inbound liquidity, says they can't receive a payment, needs a channel, asks about LSP fees, or wants to check the status of a channel order / LSP order."
-tools: lsp_get_info, lsp_get_network_info, lsp_estimate_fees, lsp_create_order, lsp_get_order, rln_get_node_info, rln_pay_invoice
+tools: kaleidoswap_lsp_get_info, kaleidoswap_lsp_estimate_fees, kaleidoswap_lsp_create_order, kaleidoswap_lsp_get_order, kaleidoswap_lsp_quote_asset_channel, kaleidoswap_lsp_create_asset_channel, lsp_get_info, lsp_estimate_fees, lsp_create_order, lsp_get_order, rln_get_node_info, rln_pay_invoice
 triggers: inbound, liquidity, channel order, lsp, lsps1, receive limit, can't receive, open channel, channel from, check status, order status, check the order, channel status, lsp status, check my channel
 metadata:
   author: kaleidoswap
@@ -21,11 +21,11 @@ talks to — the KaleidoSwap maker by default. Tool names are LSP-agnostic
 You have **no knowledge** of LSP capabilities, fees, channel sizes, or order
 status. Every number, capacity, fee, order id, or invoice in your reply MUST
 come from a tool result returned in the CURRENT turn. Never quote a fee from
-memory. Never claim an order completed without calling `lsp_get_order`.
+memory. Never claim an order completed without calling `kaleidoswap_lsp_get_order`.
 Never reuse a number from a previous turn.
 
 **Calling the tool IS the answer.** Don't write "the LSP info is fetched with
-`lsp_get_info`" — call it. Don't reveal tool names in your reply; describe
+`kaleidoswap_lsp_get_info`" — call it. Don't reveal tool names in your reply; describe
 what you're doing in plain language.
 
 If a tool needs a required argument the user didn't give (e.g. `client_pubkey`
@@ -40,7 +40,7 @@ The same conventions as trading apply:
 
 ## Tools and the flow
 
-### Step 1 — `lsp_get_info`
+### Step 1 — `kaleidoswap_lsp_get_info`
 No args. Returns the LSP's `OrderOptions` (min/max channel size, min/max
 expiry, etc.) and the `assets` list. **Call it once before estimating** so you
 can validate the user's request against the LSP's limits.
@@ -49,7 +49,7 @@ If the user wants 1M sats inbound but `max_initial_lsp_balance_sat` is 500k,
 say so plainly and offer the maximum — don't push through and let the maker
 reject it.
 
-### Step 2 — `lsp_estimate_fees` (read-only)
+### Step 2 — `kaleidoswap_lsp_estimate_fees` (read-only)
 Required args: `lsp_balance_sat`, `client_balance_sat`, `channel_expiry_blocks`.
 
 Defaults you can use silently if the user didn't specify:
@@ -60,10 +60,10 @@ Returns `{setup_fee, capacity_fee, duration_fee, total_fee}` — surface
 `total_fee` to the user and the breakdown when relevant.
 
 ### Step 3 — `rln_get_node_info`
-No args. Returns `{pubkey, ...}`. **Pubkey is required by `lsp_create_order` —
+No args. Returns `{pubkey, ...}`. **Pubkey is required by `kaleidoswap_lsp_create_order` —
 fetch it deterministically. Never invent a pubkey.**
 
-### Step 4 — `lsp_create_order` 🔒 spend
+### Step 4 — `kaleidoswap_lsp_create_order` 🔒 spend
 Required args: `client_pubkey` (from step 3), `lsp_balance_sat`. The maker
 also expects `client_balance_sat`, `required_channel_confirmations`,
 `funding_confirms_within_blocks`, `channel_expiry_blocks`, `announce_channel`
@@ -72,7 +72,7 @@ didn't specify, so just pass the values the user actually named.
 
 Returns:
 - `order_id`
-- `access_token` (save it — required for `lsp_get_order`)
+- `access_token` (save it — required for `kaleidoswap_lsp_get_order`)
 - `payment.bolt11.invoice` — Lightning invoice to pay
 - `payment.bolt11.order_total_sat` — the sats that need to flow
 - `payment.onchain.address` — optional on-chain fallback
@@ -82,11 +82,11 @@ Returns:
 Hand the `payment.bolt11.invoice` to `rln_pay_invoice`. This is a separate
 spend gate at the wallet contract; the user confirms paying the LSP.
 
-### Step 6 — `lsp_get_order` (poll)
+### Step 6 — `kaleidoswap_lsp_get_order` (poll)
 **Args: `order_id`, `access_token` (BOTH required — never omit either).**
 `order_state` progresses `CREATED → CHANNEL_OPENING → COMPLETED` (or `FAILED`).
 Poll until terminal. Always pass the exact order_id and access_token from the
-previous `lsp_create_order` result (or from the summary that listed them).
+previous `kaleidoswap_lsp_create_order` result (or from the summary that listed them).
 Report the outcome plainly with the new channel id from `channel.channel_id` if present.
 
 ## Don'ts
@@ -97,9 +97,9 @@ Report the outcome plainly with the new channel id from `channel.channel_id` if
 - Don't describe how a tool works — call it.
 - Don't pay a Lightning invoice without confirming the amount + LSP — the
   spend gate at `rln_pay_invoice` shows the user the destination.
-- Don't claim an order completed without polling `lsp_get_order` with BOTH
+- Don't claim an order completed without polling `kaleidoswap_lsp_get_order` with BOTH
   `order_id` and `access_token` and seeing `order_state: COMPLETED`.
-- Never call `lsp_get_order` with only the access_token or only the order_id.
+- Never call `kaleidoswap_lsp_get_order` with only the access_token or only the order_id.
   Always extract the exact values from the previous turn's summary (the one that
   said "order_id=... access_token=...") and pass them as separate arguments.
 - Don't ask the user for their node pubkey — fetch it from `rln_get_node_info`.

package/skills/kaleido-trading/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: kaleido-trading
 description: "Trade on KaleidoSwap — quote and execute swaps between BTC and RGB assets (USDT, XAUT). Get assets and pairs, pull an executable quote, place a market order, or track an atomic swap end-to-end. Triggers when the user wants a quote, to swap or trade assets, or to rebalance between BTC and stablecoins."
-tools: kaleidoswap_get_assets, kaleidoswap_get_pairs, kaleidoswap_get_quote, kaleidoswap_get_nodeinfo, kaleidoswap_place_order, kaleidoswap_get_order_status, kaleidoswap_get_order_history
+tools: kaleidoswap_get_assets, kaleidoswap_get_pairs, kaleidoswap_get_quote, kaleidoswap_place_order, kaleidoswap_get_order_status, kaleidoswap_atomic_init, kaleidoswap_atomic_execute, kaleidoswap_atomic_status, rln_get_node_info, rln_atomic_taker
 triggers: quote, swap, trade, rebalance, slippage, pair, pairs, usdt, xaut, kaleidoswap, rfq
 metadata:
   author: kaleidoswap

package/skills/liquidity-optimizer/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: liquidity-optimizer
+description: "Analyze and optimize the node's Lightning liquidity. Reads channels, balances and payment history, then explains the node's liquidity health and recommends concrete actions: buy inbound, open/close channels, rebalance BTC↔assets, or tune routing fees. Triggers when the user wants to rebalance, optimize liquidity, fix inbound/outbound balance, free up capital, lower fees, or asks 'how healthy is my node?' / 'where is my liquidity?'."
+tools: rln_list_channels, rln_get_balances, rln_get_node_info, rln_list_payments, kaleidoswap_lsp_get_info, kaleidoswap_lsp_estimate_fees, kaleidoswap_lsp_quote_asset_channel, rln_open_channel, rln_close_channel
+triggers: rebalance, rebalancing, optimize liquidity, liquidity, inbound, outbound, lopsided, depleted channel, free up capital, stuck funds, channel balance, routing fee, lower fees, fee optimization, node health, healthy node, where is my liquidity, capacity
+metadata:
+  author: kaleidoswap
+  version: "0.1.0"
+---
+
+# Liquidity optimizer
+
+Help the user keep their RGB Lightning node's liquidity healthy: balanced
+inbound/outbound, capital not stuck in dead channels, and fees set so the node
+can actually route and receive. You **analyze real channel state and recommend
+actions** — you never move funds without an explicit, confirmed instruction.
+
+## Critical rules — these override everything else
+
+You have **no knowledge** of the node's channels, balances, or capacity. Every
+number, channel id, ratio, or fee in your reply MUST come from a tool result
+returned in the CURRENT turn. Never quote a balance from memory or reuse a
+number from a previous turn — re-read it.
+
+**Calling the tool IS the analysis.** Don't say "I'd check your channels with
+`rln_list_channels`" — call it, then report what it returned in plain language.
+Don't reveal raw tool names in your reply.
+
+**Read freely, spend never (without confirmation).** `rln_list_channels`,
+`rln_get_balances`, `rln_get_node_info`, `rln_list_payments`,
+`kaleidoswap_lsp_get_info`, and `kaleidoswap_lsp_estimate_fees` are read-only —
+use them as much as you need. `rln_open_channel`, `rln_close_channel`, and
+buying a channel are **spends**: only call them when the user explicitly asked
+for that action this turn, and each goes through the wallet's confirmation gate.
+When you merely *recommend* an action, describe it — do not execute it.
+
+## How to assess liquidity
+
+### 1 — Read the state (always start here)
+- `rln_list_channels` → `channel_count`, `total_outbound_msat`,
+  `total_inbound_msat`, and per-channel `outbound_balance_msat`,
+  `inbound_balance_msat`, `is_usable`, capacity, peer, and any RGB asset
+  allocation. **Balances are in millisats (msat); divide by 1000 for sats.**
+- `rln_get_balances` → on-chain (vanilla/colored) + Lightning balance, to see
+  uncommitted capital that could open a channel.
+- `rln_get_node_info` → pubkey, peer/channel counts, sync state.
+- `rln_list_payments` (optional) → recent flow direction, to infer whether the
+  node mostly sends or receives.
+
+### 2 — Compute the picture (per channel and overall)
+For each channel, the **outbound ratio** = `outbound / (outbound + inbound)`:
+- **~0% (all inbound):** can receive but can't send — depleted outbound.
+- **~100% (all outbound):** can send but can't receive — no inbound liquidity.
+- **40–60%:** balanced and healthy.
+Then look at the totals: is the node short on **inbound** (can't receive) or
+short on **outbound** (can't send)? Flag channels that are `is_usable: false`
+(offline/pending peer) or that hold meaningful capital but never route.
+
+### 3 — Recommend, prioritized
+Lead with a one-line health verdict, then a short ordered action list. Match the
+remedy to the problem:
+- **Low inbound / "can't receive":** buy inbound from the LSP. Use
+  `kaleidoswap_lsp_get_info` for limits and `kaleidoswap_lsp_estimate_fees`
+  (or `kaleidoswap_lsp_quote_asset_channel` for an asset channel) to give a real
+  fee, then hand off to the channel-order flow. Don't invent the fee.
+- **Low outbound / "can't send":** open a channel to a well-connected peer with
+  spare on-chain BTC (`rln_open_channel`), or fund the wallet first.
+- **Lopsided but funded both ways:** rebalance instead of opening new channels —
+  for BTC↔asset imbalance, suggest a swap (the trading flow), since circular
+  rebalancing may not be available on this node.
+- **Dead/offline channels with stuck capital:** consider closing
+  (`rln_close_channel`) to reclaim funds, but only if the user confirms — note
+  on-chain fees and the ~hours for funds to settle.
+- **Fees:** if the node should route more, suggest lower routing fees; if it's
+  draining outbound cheaply, suggest raising them. If no fee-setting tool is
+  available this turn, give the recommendation and tell the user where to set it
+  rather than pretending you changed it.
+
+## Output style
+Concise and scannable. A verdict line, then "Top actions" as a short numbered
+list with the concrete number behind each (e.g. "Channel abc12… is 97% outbound
+— buy ~200k inbound, est. fee from the LSP"). No walls of JSON.
+
+## Don'ts
+- Don't invent channels, balances, ratios, capacities, or fees — read them.
+- Don't forget msat→sat conversion when reporting channel balances.
+- Don't open or close a channel, or buy liquidity, unless the user asked for
+  that action this turn — recommendations are not actions.
+- Don't claim you changed fees or rebalanced if no tool did it — say what the
+  user should do.
+- Don't reuse last turn's numbers — re-read before advising again.

package/skills/merchant-finder/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: merchant-finder
 description: "Find Bitcoin-accepting merchants near the user using live BTC Map data and the device's real location. Triggers when the user asks where to spend Bitcoin, buy pizza/food with sats or bitcoin, eat at restaurants/cafes paying with sats, for a shop, store, restaurant, cafe, bar, or ATM that accepts Bitcoin, or for merchants nearby or in a city like turin."
-tools: find_merchant_locations
+tools: find_merchant_locations, search_knowledge
 triggers: merchant, merchants, shop, shops, store, stores, restaurant, restaurants, cafe, cafes, bar, bars, atm, atms, accept, accepts, accepting, nearby, near me, around, place, places, spend, find, pizza, pizz, food, coffee, eat, dinner, lunch, buy, bitcoin map, btcmap
 metadata:
   author: kaleidoswap

package/skills/portfolio-manager/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: portfolio-manager
+description: "Keep a BTC / USDT / XAUT portfolio near its target allocation. Read live balances and prices, detect drift versus targets, and (when allowed) rebalance via an atomic swap on KaleidoSwap. Triggers when the user asks to rebalance, check allocation, review the portfolio, or optimize holdings — and is the skill the scheduled 'rebalance' loop runs."
+tools: rln_get_balances, rln_list_assets, kaleidoswap_get_pairs, kaleidoswap_get_quote, kaleidoswap_atomic_init, kaleidoswap_atomic_execute, kaleidoswap_atomic_status, get_price, get_market_data
+triggers: rebalance, allocation, portfolio, drift, optimize, target, weighting, holdings
+metadata:
+  author: kaleidoswap
+  version: "0.1.0"
+---
+
+# Portfolio manager
+
+Keep the holdings near their target weights across **BTC**, **USDT**, and
+**XAUT**. You fetch everything live — never assume a balance, price, or target.
+
+## Critical rules — these override everything else
+
+- **Read before you act.** Get balances (`rln_get_balances`) and prices
+  (`get_price`) every run. Never reuse a number from a previous turn.
+- **Respect `dry_run`.** When `dry_run` is true you describe the rebalance you
+  *would* make — you do NOT call `kaleidoswap_atomic_init`/`_execute`. This is
+  non-negotiable.
+- **Respect fund safety.** Never propose a swap that breaches the BTC reserve or
+  stop-loss floor passed in the task parameters. The host's risk gate is the
+  final word, but don't even suggest a breach.
+- **Below-minimum drift = do nothing.** If every asset is within the drift
+  threshold, say so and stop. Churn is a cost, not a feature.
+
+## How to think about a rebalance
+
+1. **Snapshot.** `rln_get_balances` → BTC sats + each RGB asset (raw units).
+2. **Value it.** Convert each holding to a common denomination using
+   `get_price`. Do NOT do arithmetic free-hand on raw RGB units — use the
+   display fields the tools return; only convert sats↔USD with the live BTC
+   price.
+3. **Compare to targets.** Targets come in the task parameters (e.g.
+   `BTC 70 / USDT 20 / XAUT 10`). Compute each asset's current weight and its
+   drift = current − target.
+4. **Decide.** If the largest drift exceeds the threshold, the over-weight asset
+   sells into the most under-weight asset. One swap per run — smallest trade
+   that brings the worst drift back inside the band.
+5. **Quote.** `kaleidoswap_get_quote(from, to, amount)` for that single leg.
+6. **Execute** (only when `dry_run` is false and the size is within limits): the
+   atomic swap recipe drives `kaleidoswap_atomic_init` → `_execute`; then poll
+   `kaleidoswap_atomic_status`.
+
+## Asset codes (canonical)
+
+`BTC` (satoshis), `USDT` (not `USD`), `XAUT` (not `XAU`/gold).
+
+## Scheduled (background) runs
+
+When run by the `rebalance` loop, after deciding, return STRICT JSON only:
+
+```
+{"task":"rebalance","timestamp":"<ISO8601>","action":"rebalance|noop","dry_run":<bool>,"reason":"<why>","details":{"from":"<asset>","to":"<asset>","amount":"<n>","drift":{}}}
+```
+
+`action` is `noop` when within band. Put the human explanation in `reason`.
+
+## Don'ts
+
+- Don't invent prices, quotes, or balances — call the tool.
+- Don't rebalance on noise — honor the drift threshold.
+- Don't place more than one swap per run.
+- Don't breach the reserve / stop-loss, ever.
+- Don't execute anything when `dry_run` is true.

package/skills/rgb-lightning-node/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: rgb-lightning-node
 description: "Drive the user's local RGB Lightning Node (RLN) — read its pubkey/status, whitelist a swap, or create Lightning/RGB receive invoices. Triggers when the user asks about the node, needs an invoice, or is mid-atomic-swap and the maker needs the node pubkey or a swapstring whitelisted."
-tools: rln_get_node_info, rln_whitelist_swap, rln_create_ln_invoice, rln_create_rgb_invoice
+tools: rln_get_node_info, rln_get_balances, rln_list_channels, rln_open_channel, rln_close_channel, rln_connect_peer, rln_get_channel_id, rln_atomic_taker, rln_list_payments, rln_create_ln_invoice, rln_create_rgb_invoice
 triggers: node, nodeinfo, pubkey, peer, channels, whitelist, taker, swapstring, invoice, receive, rgb invoice, ln invoice
 metadata:
   author: kaleidoswap
@@ -52,7 +52,7 @@ Call this when:
 the LSPS skill answers what's available to BUY (`lsp_get_info`); the current
 remote-balance breakdown isn't exposed by this skill's tools.
 
-### `rln_whitelist_swap` — { swapstring } — 🔒 confirm-gated
+### `rln_atomic_taker` — { swapstring } — 🔒 confirm-gated
 Tell the node "I accept this swap." Args: the `swapstring` returned by
 `kaleidoswap_atomic_init`. The node validates and stores it; **no funds move
 here**, but the user is committing to the swap so the engine pauses for
@@ -90,7 +90,7 @@ A user-driven swap on KaleidoSwap is a two-service flow. Keep them straight:
 | Quote | maker | `kaleidoswap_get_quote` |
 | Init  | maker | `kaleidoswap_atomic_init` (returns swapstring + payment_hash) |
 | Pubkey | **node** | `rln_get_node_info` (read `pubkey`) |
-| Whitelist | **node** | `rln_whitelist_swap` (pass the swapstring) |
+| Whitelist | **node** | `rln_atomic_taker` (pass the swapstring) |
 | Execute | maker | `kaleidoswap_atomic_execute` (needs swapstring + taker_pubkey + payment_hash) |
 | Status | maker | `kaleidoswap_atomic_status` |
 

package/skills/wallet-assistant/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wallet-assistant
 description: Everyday wallet tasks on this phone — check the BTC/asset balance, create an invoice to receive, send a payment, look up a contact, or quote a swap (e.g. "how many sats is 10 USDT?"). Triggers when the user asks about their balance, wants to receive or send money, pay an invoice, pay a contact, or convert between BTC and supported assets.
-tools: get_balances, resolve_contact, send_payment, rln_pay_invoice, rln_create_ln_invoice, spark_create_invoice, kaleidoswap_get_quote
+tools: get_balances, rln_get_balances, wdk_get_balances, spark_get_balance, rln_get_asset_balance, wdk_get_asset_balance, rln_list_assets, wdk_list_assets, rln_get_address, wdk_get_address, spark_get_address, resolve_contact, send_payment, rln_send_btc, wdk_send_btc, rln_send_asset, wdk_send_asset, spark_send_sats, rln_pay_invoice, wdk_pay_invoice, spark_pay_lightning_invoice, rln_create_ln_invoice, wdk_create_ln_invoice, spark_create_lightning_invoice, rln_create_rgb_invoice, wdk_create_rgb_invoice, rln_list_payments, wdk_list_payments, kaleidoswap_get_quote
 triggers: balance, pay, send, receive, address, invoice, transactions, contact, funds, money, sats
 ---