@vike-io/cli 0.12.1 → 0.13.1

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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-ens
 description: Reverse ENS lookup — turn a 0x address into a human-readable name like `vitalik.eth`. Cheap, single API call. Use whenever you have an address and want to display a friendlier identifier alongside it.
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-ens
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-label-provenance
 description: Multi-source label cascade for any ETH wallet — shows what every upstream label provider AND our in-house heuristic classifier says about an address, with consensus entity/type and per-source attribution. Use when the user asks "who is this address" / "what do you know about this wallet" / "is this address labeled".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-label-provenance
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-pnl-history
 description: Daily net-flow series for a wallet over the last N days — a directional proxy for daily PnL. Use when the user asks "how has wallet X done over time" / "show me daily flows for Y" / "is this wallet trending up or down".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-pnl-history
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-portfolio
 description: Composite wallet portfolio view — combines ENS + labels + ERC-20 balances + DeFi positions + recent net flow in one report. Use when the user gives a wallet address and asks for a complete picture ("full report on X" / "everything about this wallet" / "wallet snapshot").
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-portfolio
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-summary
 description: Aggregate metrics for a single wallet — volume, inflow, outflow, net flow, tx count, tokens traded across 24h / 7d / 30d / 90d / all windows. Use when the user gives an address and asks "what's this wallet doing".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-summary
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-trace
 description: Counterparty graph traversal from a root wallet outward. At each hop, expand to the top N counterparties by USD volume. Use when the user asks "where did funds from X go" / "follow the money 3 hops out" / "trace the network around this wallet" / wallet investigation.
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-trace
@@ -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

@@ -1,7 +1,7 @@
 ---
 name: vike-wallet-transactions
 description: Raw per-wallet transfer list (individual transactions, not aggregates) with direction, day, USD, and token filters. Use when the user asks "show me recent transfers for X" / "last 100 transactions of Y" / "all USDC moves from this wallet" / any forensic audit query.
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-wallet-transactions
@@ -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;
       }

package/src/commands/labels.js

@@ -2,7 +2,7 @@ import { callTool } from '../mcp-client.js';
 import { emit, emitError } from '../format.js';
 
 export function registerLabels(program) {
-  // `vike labels <address>` — multi-source label provenance for one wallet
+  // `vike-data labels <address>` — multi-source label provenance for one wallet
   program
     .command('labels <address>')
     .description('Multi-source label cascade for a wallet (10+ providers + in-house heuristic + consensus view)')

package/src/index.js

@@ -34,7 +34,7 @@ if (updateNotice) process.stderr.write(updateNotice);
 const program = new Command();
 
 program
-  .name('vike')
+  .name('vike-data')
   .description('AI-agent CLI for vike.io on-chain analytics')
   .version(version, '-v, --version', 'Show CLI version');