@vike-io/cli 0.12.1 → 0.13.0

package/skills/vike-polymarket-smart-money/SKILL.md

@@ -14,13 +14,13 @@ The "smart-money cohort" is wallets meeting all three criteria:
 ## Command
 
 ```bash
-vike polymarket smart-money --mode flows|mispricings [--hours N] [--category C] [--limit N] [--json]
+vike-data polymarket smart-money --mode flows|mispricings [--hours N] [--category C] [--limit N] [--json]
 ```
 
 ## Mode A — flows (default)
 
 ```bash
-vike polymarket smart-money --mode flows --hours 24 --category all
+vike-data polymarket smart-money --mode flows --hours 24 --category all
 ```
 
 Markets with the largest **net buy** from cohort wallets in the last N hours.
@@ -31,7 +31,7 @@ Output: `condition_id`, `title`, `slug`, `smart_wallets` (cohort count), `buy_in
 ## Mode B — mispricings
 
 ```bash
-vike polymarket smart-money --mode mispricings --hours 24 --category Crypto
+vike-data polymarket smart-money --mode mispricings --hours 24 --category Crypto
 ```
 
 Markets where cohort wallets recently bought meaningfully **below** the current mid — i.e. the market has moved away from where cohort got their fills.

package/skills/vike-polymarket-trader/SKILL.md

@@ -9,14 +9,14 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike polymarket wallet <address> [--window 24h|7d|30d|all] [--json]
+vike-data polymarket wallet <address> [--window 24h|7d|30d|all] [--json]
 ```
 
 ## Example
 
 ```bash
-vike polymarket wallet 0xabcdef1234... --window 30d
-vike pm wallet 0xabcdef1234... --json     # `pm` alias
+vike-data polymarket wallet 0xabcdef1234... --window 30d
+vike-data pm wallet 0xabcdef1234... --json     # `pm` alias
 ```
 
 ## Output

package/skills/vike-router/SKILL.md

@@ -33,19 +33,19 @@ Route the user's question to the right `vike-*` skill.
 ## Quick command map
 
 ```
-vike token   search | transfers | screener | holders
-vike wallet  summary | discover
-vike perp    funding | spreads | top-traders
-vike candles hl <symbol> | polymarket <token_id>
-vike alerts  list | channels | create | edit | delete
-vike init | doctor | schema | whoami | login | logout
+vike-data token   search | transfers | screener | holders
+vike-data wallet  summary | discover
+vike-data perp    funding | spreads | top-traders
+vike-data candles hl <symbol> | polymarket <token_id>
+vike-data alerts  list | channels | create | edit | delete
+vike-data init | doctor | schema | whoami | login | logout
 ```
 
 ## Bias
 
 - If unsure between two skills, prefer the **task skill** (specific workflow) over the **per-tool skill** (single command).
 - If the user wants raw data, use the per-tool skill with `--json`.
-- If the user is exploring, lead with `vike schema --pretty` to show what's available.
+- If the user is exploring, lead with `vike-data schema --pretty` to show what's available.
 
 ## Cost note
 

package/skills/vike-smart-money-discovery/SKILL.md

@@ -13,7 +13,7 @@ Composite playbook — combines wallet leaderboards + token-side buyer list + la
 ### A. Top realized-PnL wallets on a chain
 
 ```bash
-vike wallet discover --sort pnl --window 90d --chain ethereum --size 20 --json
+vike-data wallet discover --sort pnl --window 90d --chain ethereum --size 20 --json
 ```
 
 Keep only rows where:
@@ -28,13 +28,13 @@ That set = your "smart money universe" for the next step.
 If the user asks about a specific token, resolve it first:
 
 ```bash
-vike token search <symbol> --chain <chain> --limit 3 --json
+vike-data token search <symbol> --chain <chain> --limit 3 --json
 ```
 
 Then list its recent buyers:
 
 ```bash
-vike token transfers <addr> --tab bought --period 7d --chain <chain> --json
+vike-data token transfers <addr> --tab bought --period 7d --chain <chain> --json
 ```
 
 **Intersect** the buyer addresses with your smart-money universe from step A. Any overlap = a smart-money wallet currently accumulating this token.
@@ -44,7 +44,7 @@ vike token transfers <addr> --tab bought --period 7d --chain <chain> --json
 For every overlap address, run:
 
 ```bash
-vike wallet summary <addr> --json
+vike-data wallet summary <addr> --json
 ```
 
 Report:

package/skills/vike-token-holders/SKILL.md

@@ -9,16 +9,16 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike token holders <token_address> [--chain ethereum|bsc|base] [--limit N] [--json]
+vike-data token holders <token_address> [--chain ethereum|bsc|base] [--limit N] [--json]
 ```
 
 ## Examples
 
 ```bash
 # Resolve symbol first if needed:
-vike token search PEPE --chain ethereum --limit 1 --json
+vike-data token search PEPE --chain ethereum --limit 1 --json
 # Then holders:
-vike token holders 0x6982508145454ce325ddbe47a25d4ec3d2311933 --limit 20
+vike-data token holders 0x6982508145454ce325ddbe47a25d4ec3d2311933 --limit 20
 ```
 
 ## Output columns
@@ -40,6 +40,6 @@ vike token holders 0x6982508145454ce325ddbe47a25d4ec3d2311933 --limit 20
 
 ## Pairs well with
 
-- `vike labels <addr>` — drill into any holder's full label cascade
-- `vike token transfers <addr>` — see who's currently buying/selling in last 24h
-- `vike wallet summary <addr>` — full activity profile of any holder
+- `vike-data labels <addr>` — drill into any holder's full label cascade
+- `vike-data token transfers <addr>` — see who's currently buying/selling in last 24h
+- `vike-data wallet summary <addr>` — full activity profile of any holder

package/skills/vike-token-research/SKILL.md

@@ -12,14 +12,14 @@ Multi-call token research workflow.
 
 1. **Resolve address** (skip if user already gave one)
    ```bash
-   vike token search <symbol> --chain <chain> --limit 3 --json
+   vike-data token search <symbol> --chain <chain> --limit 3 --json
    ```
    Pick the highest-volume match; capture the address.
 
 2. **Recent buyers + sellers** (parallel calls)
    ```bash
-   vike token transfers <addr> --tab bought --period 24h --chain <chain> --json
-   vike token transfers <addr> --tab sold   --period 24h --chain <chain> --json
+   vike-data token transfers <addr> --tab bought --period 24h --chain <chain> --json
+   vike-data token transfers <addr> --tab sold   --period 24h --chain <chain> --json
    ```
 
 ## Verdict heuristics

package/skills/vike-token-screener/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike token screener
+vike-data token screener
   [--chain ethereum|bsc|base]
   [--window 24h|7d|30d|90d]
   [--sort volume|net_inflow|holders|smart_inflow]
@@ -24,16 +24,16 @@ vike token screener
 
 ```bash
 # Trending today by volume
-vike token screener --window 24h --sort volume --limit 20
+vike-data token screener --window 24h --sort volume --limit 20
 
 # Find tokens smart money is accumulating
-vike token screener --window 7d --sort smart_inflow --smart-money-only
+vike-data token screener --window 7d --sort smart_inflow --smart-money-only
 
 # Rising holders count (organic growth signal)
-vike token screener --window 30d --sort holders --min-volume 100000
+vike-data token screener --window 30d --sort holders --min-volume 100000
 
 # Mid-cap tokens with real activity
-vike token screener --min-volume 1000000 --min-holders 100 --sort net_inflow
+vike-data token screener --min-volume 1000000 --min-holders 100 --sort net_inflow
 ```
 
 ## Output columns
@@ -77,6 +77,6 @@ vike token screener --min-volume 1000000 --min-holders 100 --sort net_inflow
 
 ## Pairs well with
 
-- `vike token holders <addr>` — drill into the top holders of any flagged token
-- `vike token transfers <addr>` — see WHO is buying/selling once a token is interesting
+- `vike-data token holders <addr>` — drill into the top holders of any flagged token
+- `vike-data token transfers <addr>` — see WHO is buying/selling once a token is interesting
 - `vike-smart-money-discovery` — composite playbook starting from this screen

package/skills/vike-token-search/SKILL.md

@@ -11,13 +11,13 @@ Symbol/name → address resolver.
 ## Command
 
 ```bash
-vike token search <query> [--chain ethereum|bsc|base] [--limit N] [--json]
+vike-data token search <query> [--chain ethereum|bsc|base] [--limit N] [--json]
 ```
 
 ## Example
 
 ```bash
-vike token search PEPE --chain ethereum --limit 5
+vike-data token search PEPE --chain ethereum --limit 5
 # →  symbol  name    address                                     chain
 #    PEPE    Pepe    0x6982508145454ce325ddbe47a25d4ec3d2311933  ethereum
 #    PEPE2   ...     0x...                                       ethereum
@@ -35,5 +35,5 @@ vike token search PEPE --chain ethereum --limit 5
 
 ## Pairs well with
 
-- `vike token transfers <address>` after resolution
+- `vike-data token transfers <address>` after resolution
 - `vike-token-research` for a full multi-call report

package/skills/vike-token-transfers/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike token transfers <token_address>
+vike-data token transfers <token_address>
   [--tab bought|sold]
   [--period 1h|24h|7d|30d]
   [--chain ethereum|bsc|base|all]
@@ -29,7 +29,7 @@ Each row is one wallet: `address`, `qty`, `usd_value`, `label` (if known), `tx_c
 ## Reading tips
 
 - The same wallet appearing in both `bought` and `sold` lists for the same period = market maker / churn (not a signal).
-- High `usd_value` with low `tx_count` = a single large discretionary trade. Worth investigating with `vike wallet summary <address>`.
+- High `usd_value` with low `tx_count` = a single large discretionary trade. Worth investigating with `vike-data wallet summary <address>`.
 - Many small transfers from labeled exchanges = retail flow via that CEX (Binance, Coinbase, etc.).
 
 ## Anti-patterns
@@ -39,4 +39,4 @@ Each row is one wallet: `address`, `qty`, `usd_value`, `label` (if known), `tx_c
 
 ## Pairs well with
 
-- `vike wallet summary <addr>` to profile any interesting buyer/seller
+- `vike-data wallet summary <addr>` to profile any interesting buyer/seller

package/skills/vike-wallet-balances/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet balances <address>
+vike-data wallet balances <address>
   [--chains eth,bsc,base,arbitrum,polygon,optimism]  (default = all 6)
   [--min-usd 1]   (filter dust below this)
   [--json]
@@ -18,7 +18,7 @@ vike wallet balances <address>
 ## Example
 
 ```bash
-vike wallet balances 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --chains eth,arbitrum
+vike-data wallet balances 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --chains eth,arbitrum
 ```
 
 ## Output
@@ -53,6 +53,6 @@ Holdings sorted by `usd_value` descending.
 
 ## Pairs well with
 
-- `vike wallet pnl-history <addr>` — how the wallet got to its current state
-- `vike labels <addr>` — institutional context
-- `vike wallet ens <addr>` — friendly identifier
+- `vike-data wallet pnl-history <addr>` — how the wallet got to its current state
+- `vike-data labels <addr>` — institutional context
+- `vike-data wallet ens <addr>` — friendly identifier

package/skills/vike-wallet-batch/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet batch <addr1> <addr2> <addr3> ...
+vike-data wallet batch <addr1> <addr2> <addr3> ...
   [--chain ethereum|bsc|base]
   [--json]
 ```
@@ -19,7 +19,7 @@ Caps at 100 addresses per call. For larger lists, split into chunks.
 ## Example
 
 ```bash
-vike wallet batch 0xd8da... 0xabc... 0xdef... --json
+vike-data wallet batch 0xd8da... 0xabc... 0xdef... --json
 ```
 
 ## Output
@@ -45,11 +45,11 @@ One row per INPUT address (preserves input order — useful when joining back to
 
 ## Anti-patterns
 
-- Don't run individual `vike wallet summary` in a loop for >5 addresses — this batch is ~20× faster
+- Don't run individual `vike-data wallet summary` in a loop for >5 addresses — this batch is ~20× faster
 - Don't pass mixed-case addresses inconsistently — they're normalised but cleaner CSVs help readers
 - Don't expect lifetime data — this is 30d window. For lifetime use the individual `wallet summary`
 
 ## Pairs well with
 
-- `vike labels <addr>` — drill into any address showing high-confidence labels
-- `vike wallet compare <a> <b>` — pick two interesting batch results and diff them
+- `vike-data labels <addr>` — drill into any address showing high-confidence labels
+- `vike-data wallet compare <a> <b>` — pick two interesting batch results and diff them

package/skills/vike-wallet-compare/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet compare <address_a> <address_b>
+vike-data wallet compare <address_a> <address_b>
   [--chain ethereum|bsc|base]
   [--window 24h|7d|30d|90d|180d|all]
   [--limit N]   (max 50)
@@ -51,6 +51,6 @@ vike wallet compare <address_a> <address_b>
 
 ## Pairs well with
 
-- `vike labels <addr>` — drill into any interesting shared counterparty
-- `vike wallet trace <addr>` — follow money outward from either wallet
-- `vike wallet counterparties <addr>` — top partners per wallet individually
+- `vike-data labels <addr>` — drill into any interesting shared counterparty
+- `vike-data wallet trace <addr>` — follow money outward from either wallet
+- `vike-data wallet counterparties <addr>` — top partners per wallet individually

package/skills/vike-wallet-counterparties/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet counterparties <address>
+vike-data wallet counterparties <address>
   [--chain ethereum|bsc|base]
   [--window 24h|7d|30d|90d|180d|all]
   [--limit N]   (max 50)
@@ -19,7 +19,7 @@ vike wallet counterparties <address>
 ## Example
 
 ```bash
-vike wallet counterparties 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --window 30d
+vike-data wallet counterparties 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --window 30d
 ```
 
 ## Output columns
@@ -33,7 +33,7 @@ vike wallet counterparties 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --window 3
 - **Received >> Sent** = wallet receives from this counterparty (funding source, employer, airdrop)
 - `entity = "Binance"` (CEX) on the top row = the wallet deposits to / withdraws from that exchange
 - `wallet_type = "dex"` = router contracts (Uniswap, 1inch, Curve routers) — typical for active traders
-- Unlabeled top counterparty with high volume = potentially related wallet worth investigating with `vike labels`
+- Unlabeled top counterparty with high volume = potentially related wallet worth investigating with `vike-data labels`
 
 ## Anti-patterns
 
@@ -43,6 +43,6 @@ vike wallet counterparties 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --window 3
 
 ## Pairs well with
 
-- `vike labels <addr>` — drill into any interesting counterparty's full label cascade
-- `vike wallet summary <addr>` — total activity of any counterparty
-- `vike wallet balances <addr>` — see what tokens that counterparty currently holds
+- `vike-data labels <addr>` — drill into any interesting counterparty's full label cascade
+- `vike-data wallet summary <addr>` — total activity of any counterparty
+- `vike-data wallet balances <addr>` — see what tokens that counterparty currently holds

package/skills/vike-wallet-discover/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet discover
+vike-data wallet discover
   [--window 24h|7d|30d|90d|all]
   [--sort volume|inflow|outflow|net_flow|tx_count|pnl]
   [--order asc|desc]
@@ -36,7 +36,7 @@ vike wallet discover
 
 - Labeled wallets first — `label = "binance_cold_t1"` means it's a CEX hot/cold wallet, not a discretionary trader.
 - Always filter mentally for unlabeled wallets first if the user wants "real traders" (not exchanges).
-- For PnL sort, realized PnL only — open positions are NOT counted. Use `vike perp top-traders` for HL perps PnL (which includes unrealized).
+- For PnL sort, realized PnL only — open positions are NOT counted. Use `vike-data perp top-traders` for HL perps PnL (which includes unrealized).
 
 ## Anti-patterns
 
@@ -45,5 +45,5 @@ vike wallet discover
 
 ## Pairs well with
 
-- `vike wallet summary <address>` to drill into any interesting row
+- `vike-data wallet summary <address>` to drill into any interesting row
 - `vike-smart-money-discovery` for a composite multi-signal read

package/skills/vike-wallet-ens/SKILL.md

@@ -9,16 +9,16 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet ens <address> [--json]
+vike-data wallet ens <address> [--json]
 ```
 
 ## Example
 
 ```bash
-vike wallet ens 0xd8da6bf26964af9d7eed9e03e53415d37aa96045
+vike-data wallet ens 0xd8da6bf26964af9d7eed9e03e53415d37aa96045
 # → { "address": "0xd8da...", "ens": "vitalik.eth" }
 
-vike wallet ens 0x28c6c06298d514db089934071355e5743bf21d60
+vike-data wallet ens 0x28c6c06298d514db089934071355e5743bf21d60
 # → { "address": "0x28c6...", "ens": null }      (most exchange wallets have no ENS)
 ```
 
@@ -36,5 +36,5 @@ vike wallet ens 0x28c6c06298d514db089934071355e5743bf21d60
 
 ## Pairs well with
 
-- `vike labels <addr>` — combine ENS + labels for the fullest identity view
-- `vike wallet summary <addr>` — ENS + activity profile
+- `vike-data labels <addr>` — combine ENS + labels for the fullest identity view
+- `vike-data wallet summary <addr>` — ENS + activity profile

package/skills/vike-wallet-label-provenance/SKILL.md

@@ -11,13 +11,13 @@ The headline differentiator: we don't just show a label, we show **which sources
 ## Command
 
 ```bash
-vike labels <address> [--json]
+vike-data labels <address> [--json]
 ```
 
 ## Example
 
 ```bash
-vike labels 0x28C6c06298d514Db089934071355E5743bf21d60     # Binance Hot Wallet 14
+vike-data labels 0x28C6c06298d514Db089934071355E5743bf21d60     # Binance Hot Wallet 14
 ```
 
 ## Output shape
@@ -60,4 +60,4 @@ vike labels 0x28C6c06298d514Db089934071355E5743bf21d60     # Binance Hot Wallet
 
 ## Pairs well with
 
-- `vike wallet summary <addr>` — for the flow metrics of the labeled wallet
+- `vike-data wallet summary <addr>` — for the flow metrics of the labeled wallet

package/skills/vike-wallet-pnl-history/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet pnl-history <address>
+vike-data wallet pnl-history <address>
   [--chain ethereum|bsc|base]
   [--days N]   (max 365, default 30)
   [--json]
@@ -35,7 +35,7 @@ vike wallet pnl-history <address>
 
 **This is NET INFLOW USD, not realized PnL.** True realized PnL requires WAC (weighted-average cost) accounting per token, which we don't do in this fast tool. A wallet that bought $10K and sold $10K of the same token at the SAME price would show $0 here — but if they sold higher, true PnL would be positive (and this tool wouldn't reflect that). Use this for direction + trend, not for tax-grade PnL.
 
-For lifetime realized PnL: `vike wallet discover --sort pnl --window all`.
+For lifetime realized PnL: `vike-data wallet discover --sort pnl --window all`.
 
 ## Reading
 
@@ -53,5 +53,5 @@ For lifetime realized PnL: `vike wallet discover --sort pnl --window all`.
 
 ## Pairs well with
 
-- `vike wallet summary <addr>` for the aggregate context
-- `vike wallet counterparties <addr>` to see WHO they traded with
+- `vike-data wallet summary <addr>` for the aggregate context
+- `vike-data wallet counterparties <addr>` to see WHO they traded with

package/skills/vike-wallet-portfolio/SKILL.md

@@ -13,11 +13,11 @@ Multi-call playbook for a complete wallet snapshot.
 ```bash
 ADDR=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
 
-vike wallet ens     $ADDR --json &     # cheap, ~1 credit
-vike labels         $ADDR --json &     # cheap, ~1 credit
-vike wallet summary $ADDR --json &     # cheap, ~2 credits
-vike wallet balances $ADDR --json &    # multi-chain, ~3 credits
-vike wallet pnl-history $ADDR --days 30 --json &
+vike-data wallet ens     $ADDR --json &     # cheap, ~1 credit
+vike-data labels         $ADDR --json &     # cheap, ~1 credit
+vike-data wallet summary $ADDR --json &     # cheap, ~2 credits
+vike-data wallet balances $ADDR --json &    # multi-chain, ~3 credits
+vike-data wallet pnl-history $ADDR --days 30 --json &
 wait
 ```
 

package/skills/vike-wallet-summary/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet summary <address> [--json]
+vike-data wallet summary <address> [--json]
 ```
 
 ## Output
@@ -26,10 +26,10 @@ Per-window rows: `window`, `volume_usd`, `inflow_usd`, `outflow_usd`, `net_flow_
 
 ## Anti-patterns
 
-- Don't claim a wallet is "smart money" based on summary alone — cross-reference with labels and PnL: `vike wallet discover --sort pnl` to see if this address is in the top-PnL set.
+- Don't claim a wallet is "smart money" based on summary alone — cross-reference with labels and PnL: `vike-data wallet discover --sort pnl` to see if this address is in the top-PnL set.
 - A single big inflow can dominate `net_flow_usd` for a window — eyeball `tx_count` to gauge whether it's one trade or many.
 
 ## Pairs well with
 
-- `vike wallet discover` to see if this wallet ranks in any leaderboard
-- `vike token transfers` after identifying which tokens the wallet trades
+- `vike-data wallet discover` to see if this wallet ranks in any leaderboard
+- `vike-data token transfers` after identifying which tokens the wallet trades

package/skills/vike-wallet-trace/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet trace <address>
+vike-data wallet trace <address>
   [--chain ethereum|bsc|base]
   [--depth N]    (1-5, default 2)
   [--width N]    (1-10, default 5)
@@ -45,7 +45,7 @@ vike wallet trace <address>
 - **Depth 2-3** = "friend-of-friend" — useful for finding where funds end up.
 - **Edge volume_usd** = the volume between those two specific addresses, NOT cumulative.
 - **`wallet_type = "cex"`** at depth 1 = funds went to / came from an exchange. Often the END of the trail (anonymous from there).
-- **Unlabeled wallet with high volume at depth 1-2** = potentially related wallet, investigate with `vike labels`.
+- **Unlabeled wallet with high volume at depth 1-2** = potentially related wallet, investigate with `vike-data labels`.
 
 ## Parameter tuning
 
@@ -80,6 +80,6 @@ Tell them to click the **Graph** tab. It renders the same trace data as a force-
 
 ## Pairs well with
 
-- `vike labels <addr>` — identify any interesting node
-- `vike wallet compare <addr_a> <addr_b>` — confirm relatedness once trace surfaces candidates
-- `vike wallet transactions <addr>` — drill into specific transfers between two nodes
+- `vike-data labels <addr>` — identify any interesting node
+- `vike-data wallet compare <addr_a> <addr_b>` — confirm relatedness once trace surfaces candidates
+- `vike-data wallet transactions <addr>` — drill into specific transfers between two nodes

package/skills/vike-wallet-transactions/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike wallet transactions <address>     # alias: vike wallet txs
+vike-data wallet transactions <address>     # alias: vike-data wallet txs
   [--chain ethereum|bsc|base]
   [--direction in|out|all]
   [--days N]   (max 365)
@@ -23,13 +23,13 @@ vike wallet transactions <address>     # alias: vike wallet txs
 
 ```bash
 # Recent in+out transfers, last 7 days
-vike wallet txs 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --days 7 --limit 20
+vike-data wallet txs 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --days 7 --limit 20
 
 # Only outgoing > $10k in last 30d
-vike wallet txs 0xabc... --direction out --min-usd 10000
+vike-data wallet txs 0xabc... --direction out --min-usd 10000
 
 # Only USDC transfers
-vike wallet txs 0xabc... --token 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
+vike-data wallet txs 0xabc... --token 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
 ```
 
 ## Output columns
@@ -53,7 +53,7 @@ Sorted descending by time (most recent first).
 
 ## Pairs well with
 
-- `vike wallet summary <addr>` — aggregate metrics over same window
-- `vike wallet counterparties <addr>` — who they trade with most
-- `vike wallet trace <addr>` — graph-traverse outward from this wallet
-- `vike labels <addr>` — identify the wallet itself
+- `vike-data wallet summary <addr>` — aggregate metrics over same window
+- `vike-data wallet counterparties <addr>` — who they trade with most
+- `vike-data wallet trace <addr>` — graph-traverse outward from this wallet
+- `vike-data labels <addr>` — identify the wallet itself

package/src/auth.js

@@ -47,7 +47,7 @@ export function requireApiKey() {
   const key = getApiKey();
   if (!key) {
     throw new Error(
-      'No API key. Run `vike login --api-key <key>` or set VIKE_API_KEY. ' +
+      'No API key. Run `vike-data login --api-key <key>` or set VIKE_API_KEY. ' +
       'Get a key at https://vike.io/account?tab=api-keys',
     );
   }

package/src/chains.js

@@ -62,7 +62,7 @@ export function normaliseChain(input, fallback = 'ethereum') {
   return CHAIN_ALIASES[key] ?? input;
 }
 
-// Address-format expectations per chain. Used by `vike doctor` and
+// Address-format expectations per chain. Used by `vike-data doctor` and
 // future input validation. EVM = 0x + 40 hex; Solana = base58 32-44 chars;
 // BTC = various encodings; privacy chains = chain-specific.
 export const ADDRESS_FORMATS = {

package/src/commands/doctor.js

@@ -24,7 +24,7 @@ export function registerDoctor(program) {
         ok: Boolean(key),
         detail: key
           ? `${key.slice(0, 8)}... (source: ${process.env.VIKE_API_KEY ? 'env' : 'config'})`
-          : 'Not set. Run `vike init` or `vike login --api-key <key>`',
+          : 'Not set. Run `vike-data init` or `vike-data login --api-key <key>`',
       });
 
       // 3. Endpoint
@@ -81,7 +81,7 @@ export function registerDoctor(program) {
         console.log(`\n${failed} check(s) failed.`);
         process.exitCode = 1;
       } else {
-        console.log('\nAll checks passed. Try: vike token search BTC');
+        console.log('\nAll checks passed. Try: vike-data token search BTC');
       }
     });
 }

package/src/commands/init.js

@@ -44,7 +44,7 @@ export function registerInit(program) {
         server: info.name,
         version: info.version,
         protocol: body?.result?.protocolVersion,
-        next: 'Try: vike token search BTC',
+        next: 'Try: vike-data token search BTC',
       });
     });
 }

package/src/commands/install.js

@@ -1,4 +1,4 @@
-// `vike install` — copy SKILL.md into the agent-discoverable locations for
+// `vike-data install` — copy SKILL.md into the agent-discoverable locations for
 // supported IDEs/agents so the skill loads without the user having to wire
 // it up manually.
 //
@@ -95,8 +95,8 @@ export function registerInstall(program) {
       if (!targets.claude && !targets.cursor && !targets.copilot && !targets.agents) {
         console.error('No target selected. Use --claude / --cursor / --copilot / --agents / --all.');
         console.error('Examples:');
-        console.error('  vike install --claude');
-        console.error('  vike install --all');
+        console.error('  vike-data install --claude');
+        console.error('  vike-data install --all');
         process.exitCode = 1;
         return;
       }
@@ -104,7 +104,7 @@ export function registerInstall(program) {
       try {
         skill = readSkillSource();
       } catch (e) {
-        console.error(`vike install: ${e.message}`);
+        console.error(`vike-data install: ${e.message}`);
         process.exitCode = 1;
         return;
       }
@@ -115,7 +115,7 @@ export function registerInstall(program) {
         if (targets.copilot) results.push(installCopilot(skill, cwd));
         if (targets.agents) results.push(installAgents(skill, cwd));
       } catch (e) {
-        console.error(`vike install: ${e.message}`);
+        console.error(`vike-data install: ${e.message}`);
         process.exitCode = 1;
         return;
       }