@vike-io/cli 0.12.1 → 0.13.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.13.1
+
+### Patch Changes
+
+- Skills: `allowed-tools` is `Bash(vike-data:*)` and `vike-core` requires the `vike-data` binary. 0.13.0 renamed the command but left all 35 skills granting `Bash(vike:*)`, which does not match `vike-data …`, so an agent was asked to approve, or was refused, every call.
+
+## 0.13.0
+
+### Minor Changes
+
+- The command is `vike-data`. The `vike` binary is removed with no alias: run `vike-data init`, `vike-data token search PEPE` and so on. README, `--help`, error messages and all 36 skill playbooks now name `vike-data`; installed skills that still call `vike` need `npx skills add vike-io/vike-data-cli` again. The skill names, the umbrella skill `vike` and its install path `~/.claude/skills/vike/` are unchanged.
+
 ## 0.12.1
 
 ### Patch Changes

package/README.md

@@ -1,6 +1,6 @@
 # @vike-io/cli — the Vike Data API from your terminal and your AI agent
 
-> Repo + package: `@vike-io/cli` (npm) · `vike-io/vike-data-cli` (GitHub) · binary: `vike` (alias `vike-data`)
+> Repo + package: `@vike-io/cli` (npm) · `vike-io/vike-data-cli` (GitHub) · binary: `vike-data`
 
 [![npm version](https://img.shields.io/npm/v/@vike-io/cli.svg)](https://www.npmjs.com/package/@vike-io/cli)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
@@ -22,7 +22,7 @@ at all. Market data from centralised exchanges is not offered through the REST A
 ## Install
 
 ```bash
-# The CLI (Node.js >= 22.12). Installs the `vike` binary.
+# The CLI (Node.js >= 22.12). Installs the `vike-data` binary.
 npm install -g @vike-io/cli
 
 # OR install only the skill playbooks into your AI agent (Claude Code, Cursor,
@@ -36,16 +36,16 @@ Get a free key at [vike.io/account?tab=api-keys](https://vike.io/account?tab=api
 with `vk_`), then:
 
 ```bash
-vike init                                   # paste the key; saves ~/.vike/config.json, checks vike.io/mcp
-vike doctor                                 # Node version, key, MCP connectivity, tool list
-vike token search PEPE                      # first query
-vike perp top-traders --window 7d           # Hyperliquid wallets ranked by PnL
-vike candles hl BTC --interval 1h --limit 48
-vike polymarket markets --category Crypto   # trending markets by 24h volume
+vike-data init                                   # paste the key; saves ~/.vike/config.json, checks vike.io/mcp
+vike-data doctor                                 # Node version, key, MCP connectivity, tool list
+vike-data token search PEPE                      # first query
+vike-data perp top-traders --window 7d           # Hyperliquid wallets ranked by PnL
+vike-data candles hl BTC --interval 1h --limit 48
+vike-data polymarket markets --category Crypto   # trending markets by 24h volume
 ```
 
 The key is read from `VIKE_API_KEY` first, then from `~/.vike/config.json`
-(`vike login --api-key vk_...` writes it, `vike logout` removes it).
+(`vike-data login --api-key vk_...` writes it, `vike-data logout` removes it).
 
 ## Free datasets
 
@@ -132,24 +132,24 @@ not only the HTTP status. A rate-limited call gets HTTP 429 with `Retry-After: 6
 
 ## CLI commands
 
-Every data command is one `tools/call` to the MCP server. `vike <group> --help` lists the flags;
-`vike schema --pretty` prints every tool the server exposes, with its parameters.
+Every data command is one `tools/call` to the MCP server. `vike-data <group> --help` lists the flags;
+`vike-data schema --pretty` prints every tool the server exposes, with its parameters.
 
 | Command | Subcommands | MCP tool |
 |---|---|---|
-| `vike token` | `search`, `transfers`, `screener`, `holders` (`--chain ethereum\|bsc\|base`) | `token_search`, `token_transfers`, `token_screener`, `token_holders` |
-| `vike wallet` | `summary`, `transactions` (`txs`), `compare`, `trace`, `batch`, `counterparties`, `pnl-history`, `balances`, `ens`, `discover` | `wallet_summary`, `wallet_transactions`, `wallet_compare`, `wallet_trace`, `wallet_batch_labels`, `wallet_counterparties`, `wallet_pnl_history`, `wallet_token_balances`, `wallet_ens`, `wallet_discover` |
-| `vike labels <address>` | multi-source label provenance for one wallet | `wallet_label_provenance` |
-| `vike perp` | `top-traders`, `find-position` (Hyperliquid); `funding`, `spreads` (cross-venue funding rates and spot-perp spreads) | `hl_perp_top_traders`, `hl_position_match`, `perp_funding`, `perp_spreads` |
-| `vike candles` | `hl <symbol>` (Hyperliquid perp or spot, from executed fills), `polymarket <token_id>` (one outcome token) | `hl_ohlcv`, `polymarket_ohlcv` |
-| `vike polymarket` (`pm`) | `markets`, `market <condition_id>`, `wallet <address>`, `smart-money` | `polymarket_markets`, `polymarket_market_detail`, `polymarket_wallet`, `polymarket_smart_money` |
-| `vike alerts` | `list`, `channels`, `create`, `edit`, `delete`, `register-webhook` (email, Discord, or an HTTPS webhook, HMAC-signed when you set a secret) | `alerts_*` |
+| `vike-data token` | `search`, `transfers`, `screener`, `holders` (`--chain ethereum\|bsc\|base`) | `token_search`, `token_transfers`, `token_screener`, `token_holders` |
+| `vike-data wallet` | `summary`, `transactions` (`txs`), `compare`, `trace`, `batch`, `counterparties`, `pnl-history`, `balances`, `ens`, `discover` | `wallet_summary`, `wallet_transactions`, `wallet_compare`, `wallet_trace`, `wallet_batch_labels`, `wallet_counterparties`, `wallet_pnl_history`, `wallet_token_balances`, `wallet_ens`, `wallet_discover` |
+| `vike-data labels <address>` | multi-source label provenance for one wallet | `wallet_label_provenance` |
+| `vike-data perp` | `top-traders`, `find-position` (Hyperliquid); `funding`, `spreads` (cross-venue funding rates and spot-perp spreads) | `hl_perp_top_traders`, `hl_position_match`, `perp_funding`, `perp_spreads` |
+| `vike-data candles` | `hl <symbol>` (Hyperliquid perp or spot, from executed fills), `polymarket <token_id>` (one outcome token) | `hl_ohlcv`, `polymarket_ohlcv` |
+| `vike-data polymarket` (`pm`) | `markets`, `market <condition_id>`, `wallet <address>`, `smart-money` | `polymarket_markets`, `polymarket_market_detail`, `polymarket_wallet`, `polymarket_smart_money` |
+| `vike-data alerts` | `list`, `channels`, `create`, `edit`, `delete`, `register-webhook` (email, Discord, or an HTTPS webhook, HMAC-signed when you set a secret) | `alerts_*` |
 | setup | `init`, `login`, `logout`, `doctor`, `schema`, `install` | — |
 
 Output is a table on a terminal and JSON with `--json` or whenever stdout is piped:
 
 ```bash
-vike token search BTC --json | jq '.'
+vike-data token search BTC --json | jq '.'
 ```
 
 ## Examples
@@ -183,14 +183,14 @@ npx skills add vike-io/vike-data-cli --list    # see them first
 npx skills add vike-io/vike-data-cli           # install
 
 # Or, from the installed CLI, write the umbrella skill into each agent's location:
-vike install --claude     # ~/.claude/skills/vike/SKILL.md
-vike install --cursor     # ./.cursorrules
-vike install --copilot    # ./.github/copilot-instructions.md
-vike install --agents     # ./AGENTS.md
-vike install --all        # all four
+vike-data install --claude     # ~/.claude/skills/vike/SKILL.md
+vike-data install --cursor     # ./.cursorrules
+vike-data install --copilot    # ./.github/copilot-instructions.md
+vike-data install --agents     # ./AGENTS.md
+vike-data install --all        # all four
 ```
 
-`vike install` replaces only its own `<!-- vike-skill:begin -->` ... `<!-- vike-skill:end -->`
+`vike-data install` replaces only its own `<!-- vike-skill:begin -->` ... `<!-- vike-skill:end -->`
 block in files it does not own.
 
 ## Environment
@@ -205,7 +205,7 @@ block in files it does not own.
 Telemetry sends the command name, the flag names (never their values), the duration, an error code
 and a random device id. It never sends what you queried, and it is off when `CI` is set.
 
-`vike` here is the Data API client. The Vike Trader platform has its own, separate command line,
+`vike-data` is the Data API client. The Vike Trader platform has its own, separate command line,
 `vike-cli` ([docs](https://vike.io/docs/trader/cli)).
 
 ## License

package/package.json

@@ -3,12 +3,11 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.12.1",
+  "version": "0.13.1",
   "description": "CLI, agent skills and MCP client for the free Vike Data API: a Polymarket full-L2 order-book archive in Parquet (CC BY 4.0), Hyperliquid positions, fills and cohorts, and labelled Ethereum/BNB wallets",
   "type": "module",
   "main": "src/index.js",
   "bin": {
-    "vike": "./src/index.js",
     "vike-data": "./src/index.js"
   },
   "files": [

package/scripts/postinstall.js

@@ -26,9 +26,9 @@ try {
     '  @vike-io/cli installed.',
     '',
     '  Next steps:',
-    '    vike init                  — interactive setup',
-    '    vike doctor                — verify your install',
-    '    vike token search BTC      — your first query',
+    '    vike-data init                  — interactive setup',
+    '    vike-data doctor                — verify your install',
+    '    vike-data token search BTC      — your first query',
     '',
     '  Docs:    https://vike.io/data/',
     '  API key: https://vike.io/account?tab=api-keys',

package/skills/vike/SKILL.md

@@ -38,12 +38,12 @@ Hard rules — agents that violate these produce wrong answers. Read once, apply
 Follow this decision tree **before every session**. Do not skip to Step 2 until auth is confirmed.
 
 ```
-1. Is the `vike` CLI installed? (`vike --version`)
+1. Is the `vike` CLI installed? (`vike-data --version`)
    ├── YES → continue
    └── NO  → `npm install -g @vike-io/cli`
 
-2. Is $VIKE_API_KEY set OR has the user run `vike init` / `vike login` already?
-   ├── YES → run `vike doctor` to verify the key + endpoint reachability. Proceed.
+2. Is $VIKE_API_KEY set OR has the user run `vike-data init` / `vike-data login` already?
+   ├── YES → run `vike-data doctor` to verify the key + endpoint reachability. Proceed.
    └── NO  → prompt the user (see Setup below).
 ```
 
@@ -54,8 +54,8 @@ If the user has no API key yet, tell them:
 > **To use vike, you'll need a free API key:**
 >
 > 1. Visit https://vike.io/account?tab=api-keys&utm_source=skill&utm_medium=ai&utm_campaign=cli_skill, sign in, and copy a key (starts with `vk_`).
-> 2. Save it: `vike login --api-key vk_...` (or `export VIKE_API_KEY=vk_...`).
-> 3. Verify: `vike doctor`.
+> 2. Save it: `vike-data login --api-key vk_...` (or `export VIKE_API_KEY=vk_...`).
+> 3. Verify: `vike-data doctor`.
 >
 > Per-key default cap: 2000 requests/hour. Most calls return in <500ms.
 
@@ -70,33 +70,33 @@ X-API-KEY: vk_...
 
 | User is asking about... | Service | CLI / Tool |
 |---|---|---|
-| Token by symbol/name → address, market cap, holders | **Tokens** | `vike token search` / `token_search` |
-| Token holders, who bought/sold, top inflows | **Tokens** | `vike token transfers` / `token_transfers` |
-| Filter/screen tokens by smart-money flow, liquidity, age | **Tokens** | `vike token screener` / `token_screener` |
-| Single wallet's PnL, holdings, recent activity | **Wallets** | `vike wallet summary` / `wallet_summary` |
-| Top wallets by PnL on a token / leaderboard | **Wallets** | `vike wallet discover` / `wallet_discover` |
-| Recent wallet transactions with USD values | **Wallets** | `vike wallet transactions` / `wallet_transactions` |
-| Compare 2+ wallets side by side | **Wallets** | `vike wallet compare` / `wallet_compare` |
-| Trace funds N hops from a starting wallet | **Wallets** | `vike wallet trace` / `wallet_trace` |
-| Find counterparties (who sends to / receives from) | **Wallets** | `vike wallet counterparties` / `wallet_counterparties` |
-| Wallet PnL history (timeseries) | **Wallets** | `vike wallet pnl-history` / `wallet_pnl_history` |
-| Token balances for a wallet | **Wallets** | `vike wallet balances` / `wallet_token_balances` |
-| ENS name → address or address → ENS | **Wallets** | `vike wallet ens` / `wallet_ens` |
-| Bulk-label many wallets at once | **Wallets** | `vike wallet batch` / `wallet_batch_labels` |
-| Why is this wallet labeled X? (provenance) | **Labels** | `vike labels provenance` / `wallet_label_provenance` |
-| Funding rates across CEX perps (Binance/Bybit/OKX/Aster/HL) | **CEX Perps** | `vike perp funding` / `perp_funding` |
-| Price spreads of same symbol across CEX perp venues | **CEX Perps** | `vike perp spreads` / `perp_spreads` |
-| Top Hyperliquid perp traders by PnL / volume | **HL Perps** | `vike perp top-traders` / `hl_perp_top_traders` |
-| Reverse-lookup an HL share card → which wallet holds it | **HL Perps** | `vike perp find-position` / `hl_position_match` |
-| Historical candles for a Hyperliquid perp or spot market (1m–1d) | **Candles** | `vike candles hl <symbol>` / `hl_ohlcv` |
-| Historical probability candles for a Polymarket outcome token | **Candles** | `vike candles polymarket <token_id>` / `polymarket_ohlcv` |
-| Active Polymarket markets, volume, odds | **Polymarket** | `vike polymarket markets` / `polymarket_markets` |
-| Single Polymarket market detail | **Polymarket** | `vike polymarket detail` / `polymarket_market_detail` |
-| Polymarket trader profile / positions | **Polymarket** | `vike polymarket wallet` / `polymarket_wallet` |
-| Best-performing Polymarket traders | **Polymarket** | `vike polymarket smart-money` / `polymarket_smart_money` |
-| Create / list / edit price-or-flow alerts | **Alerts** | `vike alerts ...` / `alerts_*` |
-
-**When in doubt, start with `vike token search` or `vike wallet summary`** — both are cheap, return instantly, and disambiguate what the user actually meant.
+| Token by symbol/name → address, market cap, holders | **Tokens** | `vike-data token search` / `token_search` |
+| Token holders, who bought/sold, top inflows | **Tokens** | `vike-data token transfers` / `token_transfers` |
+| Filter/screen tokens by smart-money flow, liquidity, age | **Tokens** | `vike-data token screener` / `token_screener` |
+| Single wallet's PnL, holdings, recent activity | **Wallets** | `vike-data wallet summary` / `wallet_summary` |
+| Top wallets by PnL on a token / leaderboard | **Wallets** | `vike-data wallet discover` / `wallet_discover` |
+| Recent wallet transactions with USD values | **Wallets** | `vike-data wallet transactions` / `wallet_transactions` |
+| Compare 2+ wallets side by side | **Wallets** | `vike-data wallet compare` / `wallet_compare` |
+| Trace funds N hops from a starting wallet | **Wallets** | `vike-data wallet trace` / `wallet_trace` |
+| Find counterparties (who sends to / receives from) | **Wallets** | `vike-data wallet counterparties` / `wallet_counterparties` |
+| Wallet PnL history (timeseries) | **Wallets** | `vike-data wallet pnl-history` / `wallet_pnl_history` |
+| Token balances for a wallet | **Wallets** | `vike-data wallet balances` / `wallet_token_balances` |
+| ENS name → address or address → ENS | **Wallets** | `vike-data wallet ens` / `wallet_ens` |
+| Bulk-label many wallets at once | **Wallets** | `vike-data wallet batch` / `wallet_batch_labels` |
+| Why is this wallet labeled X? (provenance) | **Labels** | `vike-data labels provenance` / `wallet_label_provenance` |
+| Funding rates across CEX perps (Binance/Bybit/OKX/Aster/HL) | **CEX Perps** | `vike-data perp funding` / `perp_funding` |
+| Price spreads of same symbol across CEX perp venues | **CEX Perps** | `vike-data perp spreads` / `perp_spreads` |
+| Top Hyperliquid perp traders by PnL / volume | **HL Perps** | `vike-data perp top-traders` / `hl_perp_top_traders` |
+| Reverse-lookup an HL share card → which wallet holds it | **HL Perps** | `vike-data perp find-position` / `hl_position_match` |
+| Historical candles for a Hyperliquid perp or spot market (1m–1d) | **Candles** | `vike-data candles hl <symbol>` / `hl_ohlcv` |
+| Historical probability candles for a Polymarket outcome token | **Candles** | `vike-data candles polymarket <token_id>` / `polymarket_ohlcv` |
+| Active Polymarket markets, volume, odds | **Polymarket** | `vike-data polymarket markets` / `polymarket_markets` |
+| Single Polymarket market detail | **Polymarket** | `vike-data polymarket detail` / `polymarket_market_detail` |
+| Polymarket trader profile / positions | **Polymarket** | `vike-data polymarket wallet` / `polymarket_wallet` |
+| Best-performing Polymarket traders | **Polymarket** | `vike-data polymarket smart-money` / `polymarket_smart_money` |
+| Create / list / edit price-or-flow alerts | **Alerts** | `vike-data alerts ...` / `alerts_*` |
+
+**When in doubt, start with `vike-data token search` or `vike-data wallet summary`** — both are cheap, return instantly, and disambiguate what the user actually meant.
 
 ### Example query routing
 ```
@@ -120,13 +120,13 @@ X-API-KEY: vk_...
 
 **A) Via CLI (recommended for shell-bound agents).** All commands accept `--json` for machine-readable output:
 ```bash
-vike wallet summary 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --json
-vike perp funding --symbol BTC --window 24h --json
+vike-data wallet summary 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --json
+vike-data perp funding --symbol BTC --window 24h --json
 ```
 
 **B) Via an MCP connector (recommended when your client has one).** All 31 tools live at `https://vike.io/mcp`. Connect the client to that address with the `X-API-KEY` header above, then call a tool by name with its arguments, for example `wallet_summary` with `address` set to a full 0x address and `chain` set to `ethereum`.
 
-Run `vike schema --pretty` (or call MCP `tools/list`) to see the live arg shape for every tool. Always read the schema before constructing arguments — defaults and enum values change.
+Run `vike-data schema --pretty` (or call MCP `tools/list`) to see the live arg shape for every tool. Always read the schema before constructing arguments — defaults and enum values change.
 
 ---
 

package/skills/vike-alerts-setup/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-alerts-setup
 description: Create, list, edit, and delete on-chain transfer alerts. Alerts fire when a token transfer crosses USD thresholds you set and deliver to email or Discord. Use when the user asks "alert me when X" / "watch for big transfers" / "notify on whale moves".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-alerts-setup
@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Pre-check: what channels does the user have set up?
 
 ```bash
-vike alerts channels --json
+vike-data alerts channels --json
 ```
 
 Returns enabled email + Discord channels. **If a user creates an alert with a channel they haven't verified, the alert is saved but won't fire notifications.** Always check first.
@@ -19,14 +19,14 @@ Returns enabled email + Discord channels. **If a user creates an alert with a ch
 ### List
 
 ```bash
-vike alerts list --json                    # active alerts
-vike alerts list --include-inactive --json # also paused/deleted
+vike-data alerts list --json                    # active alerts
+vike-data alerts list --include-inactive --json # also paused/deleted
 ```
 
 ### Create
 
 ```bash
-vike alerts create \
+vike-data alerts create \
   --label "Big USDC moves" \
   --token USDC \
   --chain eth \
@@ -40,16 +40,16 @@ Required: `--label`. Common: `--token`, `--chain eth|bsc`, `--min-usd`, `--chann
 ### Edit (partial update — only fields you pass are changed)
 
 ```bash
-vike alerts edit 42 --min-usd 5000000          # raise threshold
-vike alerts edit 42 --active false             # pause
-vike alerts edit 42 --channel email --channel discord  # add second channel
+vike-data alerts edit 42 --min-usd 5000000          # raise threshold
+vike-data alerts edit 42 --active false             # pause
+vike-data alerts edit 42 --channel email --channel discord  # add second channel
 ```
 
 ### Delete
 
 ```bash
-vike alerts delete 42                          # soft-delete (pauses, keeps history)
-vike alerts delete 42 --hard                   # permanently remove
+vike-data alerts delete 42                          # soft-delete (pauses, keeps history)
+vike-data alerts delete 42 --hard                   # permanently remove
 ```
 
 ## Notes + gotchas
@@ -58,7 +58,7 @@ vike alerts delete 42 --hard                   # permanently remove
 - Thresholds are in **USD value** of the transfer at fire time, not token quantity.
 - `--cooldown` is per-alert minimum gap between triggers (default 60 min). Useful to avoid spam during high-volume hours.
 - Tokens are matched by symbol (UPPERCASE). For cross-chain symbols like `USDC` that exist on multiple chains, be explicit with `--chain`.
-- Alerts created without a verified channel will be **silently inactive at fire time** — there is no automatic warning. Use `vike alerts channels` first.
+- Alerts created without a verified channel will be **silently inactive at fire time** — there is no automatic warning. Use `vike-data alerts channels` first.
 
 ## Confirmation flow with the user
 
@@ -66,7 +66,7 @@ Before creating an alert, summarize back what will be created:
 
 > Creating alert "**Big USDC moves**": will fire when a USDC transfer on **eth** exceeds **$1M**, delivered via **email**, with a 60-minute cooldown. OK to proceed?
 
-Wait for confirmation, then run `vike alerts create`.
+Wait for confirmation, then run `vike-data alerts create`.
 
 ## Anti-patterns
 

package/skills/vike-alerts-webhook/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-alerts-webhook
 description: Register an HTTPS webhook as an alert delivery channel — get HMAC-signed POST notifications when alerts fire. Use when the user has a server / bot / Slack integration and wants programmatic alert delivery instead of email/Discord.
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-alerts-webhook
@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Registration
 
 ```bash
-vike alerts register-webhook <https://your-server.com/vike-hook>
+vike-data alerts register-webhook <https://your-server.com/vike-hook>
   [--secret <16+ char HMAC secret>]
   [--json]
 ```
@@ -23,7 +23,7 @@ The secret is **optional but strongly recommended** — without it we still POST
 openssl rand -hex 32
 # → 7f5c8b...  (paste below)
 
-vike alerts register-webhook https://api.mycoolbot.com/vike-alert \
+vike-data alerts register-webhook https://api.mycoolbot.com/vike-alert \
   --secret 7f5c8b... \
   --json
 # → { "ok": true, "channel_id": 42, "url_preview": "https://api.myc...", "signed": true }
@@ -80,5 +80,5 @@ def verify(secret, headers, body):
 
 ## Pairs well with
 
-- `vike alerts create` — create the alert that fires to your webhook
-- `vike alerts list` / `vike alerts channels` — confirm registration
+- `vike-data alerts create` — create the alert that fires to your webhook
+- `vike-data alerts list` / `vike-data alerts channels` — confirm registration

package/skills/vike-candles/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-candles
 description: Historical OHLCV candles for a Hyperliquid perp or spot market, or for one Polymarket outcome token. Use when the user asks for a price chart, candles, OHLCV, or price history of a Hyperliquid asset or a Polymarket outcome (its probability over time).
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-candles
@@ -15,7 +15,7 @@ rather than guessing a venue.
 Hyperliquid (perp or spot), built from HL's own executed fills:
 
 ```bash
-vike candles hl <symbol>
+vike-data candles hl <symbol>
   [--interval 1m|5m|15m|30m|1h|4h|1d]   # default 1h
   [--market perp|spot]                  # default perp
   [--dex <name>]                        # HIP-3 builder DEX; default HL (the core venue)
@@ -27,7 +27,7 @@ vike candles hl <symbol>
 Polymarket, ONE outcome token (a probability, 0-1):
 
 ```bash
-vike candles polymarket <token_id>
+vike-data candles polymarket <token_id>
   [--interval 1m|5m|1h|1d]              # default 1h
   [--from <epoch-ms>] [--to <epoch-ms>] # both inclusive
   [--limit N]                           # default 500, max 1000
@@ -38,10 +38,10 @@ vike candles polymarket <token_id>
 
 | Question | Command |
 |---|---|
-| "Hourly BTC perp candles, last week" | `vike candles hl BTC --interval 1h --limit 168` |
-| "HYPE spot daily candles" | `vike candles hl HYPE --market spot --interval 1d` |
-| "4h ETH, 200 bars" | `vike candles hl ETH --interval 4h --limit 200` |
-| "Price history of the YES outcome of market X" | get `clob_token_ids` from `vike polymarket market <condition_id>`, then `vike candles polymarket <token_id> --interval 1h` |
+| "Hourly BTC perp candles, last week" | `vike-data candles hl BTC --interval 1h --limit 168` |
+| "HYPE spot daily candles" | `vike-data candles hl HYPE --market spot --interval 1d` |
+| "4h ETH, 200 bars" | `vike-data candles hl ETH --interval 4h --limit 200` |
+| "Price history of the YES outcome of market X" | get `clob_token_ids` from `vike-data polymarket market <condition_id>`, then `vike-data candles polymarket <token_id> --interval 1h` |
 
 ## Output
 
@@ -50,12 +50,12 @@ Polymarket: `ts`, `open`, `high`, `low`, `close`, `volume`, `trades`, oldest fir
 
 ## Pitfalls
 
-- Polymarket takes an **outcome token id**, not a `condition_id`. A condition id returns nothing useful; read the token ids off `clob_token_ids` in `vike polymarket market`.
+- Polymarket takes an **outcome token id**, not a `condition_id`. A condition id returns nothing useful; read the token ids off `clob_token_ids` in `vike-data polymarket market`.
 - Polymarket has no cursor: a window wider than `--limit` is truncated at the **old** end. Raise `--from` to reach the recent end.
 - Polymarket `--from` / `--to` are epoch **milliseconds**; HL `--start` / `--end` also accept ISO-8601.
 - HL buckets are left-aligned UTC and the window is half-open.
 
 ## Pairs well with
 
-- `vike polymarket market <condition_id>` — to find the token ids
-- `vike perp top-traders` — who is trading the asset behind the candles
+- `vike-data polymarket market <condition_id>` — to find the token ids
+- `vike-data perp top-traders` — who is trading the asset behind the candles

package/skills/vike-core/SKILL.md

@@ -1,17 +1,17 @@
 ---
 name: vike-core
-description: Install-first skill — authentication, setup, and CLI conventions for the vike toolkit. Use when you see any `vike <cmd>` reference or the user mentions on-chain analytics, Hyperliquid perps, options flow, or prediction markets.
+description: Install-first skill — authentication, setup, and CLI conventions for the vike toolkit. Use when you see any `vike-data <cmd>` reference or the user mentions on-chain analytics, Hyperliquid perps, options flow, or prediction markets.
 metadata:
   openclaw:
     requires:
       env: [VIKE_API_KEY]
-      bins: [vike]
+      bins: [vike-data]
     primaryEnv: VIKE_API_KEY
     install:
       - kind: node
         package: "@vike-io/cli"
-        bins: [vike]
-allowed-tools: Bash(vike:*)
+        bins: [vike-data]
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-core
@@ -27,8 +27,8 @@ npm install -g @vike-io/cli
 ## Authenticate (one of these)
 
 ```bash
-vike init                          # interactive: prompt for API key + verify
-vike login --api-key vk_...        # non-interactive
+vike-data init                          # interactive: prompt for API key + verify
+vike-data login --api-key vk_...        # non-interactive
 export VIKE_API_KEY=vk_...         # env (wins over saved config)
 ```
 
@@ -37,9 +37,9 @@ Get an API key at https://vike.io/account?tab=api-keys
 ## Verify
 
 ```bash
-vike doctor                        # Node version + API key + endpoint reachability + tool count
-vike whoami                        # which key is in use (masked)
-vike schema --pretty               # full command list with flags
+vike-data doctor                        # Node version + API key + endpoint reachability + tool count
+vike-data whoami                        # which key is in use (masked)
+vike-data schema --pretty               # full command list with flags
 ```
 
 ## Conventions
@@ -48,13 +48,13 @@ vike schema --pretty               # full command list with flags
 - Addresses: pass full 0x-prefixed hex (42 chars). Never truncate when reporting back to the user.
 - USD amounts: integers/decimals (e.g. `--min-usd 10000`).
 - Chain identifiers: `eth`, `bsc`, `base`, `arb`, `hyper`, `btc`, `sol`, `tron`, `xmr`, `zec`, `dash` (depending on the command — some only support a subset).
-- Time windows: `24h`, `7d`, `30d`, `90d`, `all` (per command; check `vike <cmd> --help`).
+- Time windows: `24h`, `7d`, `30d`, `90d`, `all` (per command; check `vike-data <cmd> --help`).
 
 ## Errors
 
-- `No API key` → run `vike init` or set `VIKE_API_KEY`.
+- `No API key` → run `vike-data init` or set `VIKE_API_KEY`.
 - `MCP error -32000: Hourly rate limit exceeded` → you hit the per-key cap; wait or upgrade your plan.
-- `Network error` / timeout → check `vike doctor`; the endpoint is `https://vike.io/mcp`.
+- `Network error` / timeout → check `vike-data doctor`; the endpoint is `https://vike.io/mcp`.
 - `503` from a tool → upstream data source temporarily down; retry in 30s.
 
 ## Cost awareness

package/skills/vike-cross-venue-perps/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-cross-venue-perps
 description: Compare a single perp symbol across all venues — funding, price, spreads. Use when the user asks "where to trade X" / "compare BTC perp across exchanges" / "best venue for ETH long".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-cross-venue-perps
@@ -12,11 +12,11 @@ Per-symbol cross-venue analysis.
 
 1. Per-venue funding
    ```bash
-   vike perp funding --symbol <SYM> --json
+   vike-data perp funding --symbol <SYM> --json
    ```
 2. Per-venue spread
    ```bash
-   vike perp spreads --symbol <SYM> --json
+   vike-data perp spreads --symbol <SYM> --json
    ```
 
 ## Report template

package/skills/vike-hl-position-match/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-hl-position-match
 description: Reverse-lookup a Hyperliquid open position from share-card details (coin + side + leverage + entry price). Use when the user pastes or describes a HL share card and asks "whose card is this?", "find this trader", or "who has a 25x ETH long open at $3,200?". Returns matching wallet(s) ranked by entry-price proximity.
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-hl-position-match
@@ -11,7 +11,7 @@ Find the wallet(s) holding an open Hyperliquid perp position that match a share
 ## Command
 
 ```bash
-vike perp find-position
+vike-data perp find-position
   --coin <SYM>         # e.g. BTC, ETH, SOL
   --side long|short
   --leverage <X>       # e.g. 25
@@ -77,7 +77,7 @@ The response includes `tolerance_used` so the caller knows which band matched (`
 
 - Don't fabricate matches when the tool returns `match_count: 0`. Say "no open position matches that share card" — closed positions, post-card adds, or non-HL cards all produce empty results.
 - Don't strip the address when displaying — share-card investigations always want the full 0x...40hex (users copy-paste it).
-- Don't infer trader skill from a single share-card match. Use `vike perp top-traders` or `vike wallet summary` for profile context.
+- Don't infer trader skill from a single share-card match. Use `vike-data perp top-traders` or `vike-data wallet summary` for profile context.
 
 ## Pairs well with
 

package/skills/vike-hl-top-traders/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-hl-top-traders
 description: Rank top Hyperliquid perp traders by PnL / ROI / win rate / volume / trade count / drawdown across a window. Use when the user asks "top HL traders" / "best Hyperliquid wallets" / "HL leaderboard".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-hl-top-traders
@@ -9,7 +9,7 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike perp top-traders
+vike-data perp top-traders
   [--window 1d|7d|30d|all]
   [--sort pnl|roi|win_rate|volume|trade_count|drawdown]
   [--order asc|desc]

package/skills/vike-hl-trader-profile/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-hl-trader-profile
 description: Profile a single Hyperliquid perp trader — leaderboard rank, recent performance, on-chain identity. Use when the user gives an HL wallet address and asks "is this trader any good" / "profile this address" / "what's this wallet's HL track record".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-hl-trader-profile
@@ -13,7 +13,7 @@ Composite profile combining ranking, identity, and trading metrics.
 ### 1. On-chain identity + balance
 
 ```bash
-vike wallet summary <address> --json
+vike-data wallet summary <address> --json
 ```
 
 Captures: total volume, inflow/outflow, tx count, unique tokens across ETH/BSC/Base. Tells you if the address is HL-only or also active on spot chains.
@@ -21,8 +21,8 @@ Captures: total volume, inflow/outflow, tx count, unique tokens across ETH/BSC/B
 ### 2. HL leaderboard rank
 
 ```bash
-vike perp top-traders --window 30d --sort pnl --size 20 --json
-vike perp top-traders --window 7d  --sort pnl --size 20 --json
+vike-data perp top-traders --window 30d --sort pnl --size 20 --json
+vike-data perp top-traders --window 7d  --sort pnl --size 20 --json
 ```
 
 Search the returned rows for the address. Report rank if found, "outside top 20" otherwise.
@@ -30,8 +30,8 @@ Search the returned rows for the address. Report rank if found, "outside top 20"
 ### 3. ROI + win rate context
 
 ```bash
-vike perp top-traders --sort roi --window 30d --min-trades 10 --size 20 --json
-vike perp top-traders --sort win_rate --window 30d --min-trades 10 --size 20 --json
+vike-data perp top-traders --sort roi --window 30d --min-trades 10 --size 20 --json
+vike-data perp top-traders --sort win_rate --window 30d --min-trades 10 --size 20 --json
 ```
 
 Same address-search; report rank or "not in top 20".

package/skills/vike-perp-funding-arb/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vike-perp-funding-arb
 description: Find cross-venue funding-rate arbitrage opportunities on perpetual futures. Use when the user asks "any funding arb today" / "where to long-short X for funding" / "highest funding rates".
-allowed-tools: Bash(vike:*)
+allowed-tools: Bash(vike-data:*)
 ---
 
 # vike-perp-funding-arb
@@ -13,7 +13,7 @@ Cross-venue funding rates across Binance, Bybit, OKX, Aster, and Hyperliquid.
 ### A. All arb opportunities (default)
 
 ```bash
-vike perp funding --json
+vike-data perp funding --json
 ```
 
 Returns pre-ranked rows where the spread between the highest-funding venue and the lowest is ≥ 0.3% (daily normalized). Each row already includes:
@@ -27,7 +27,7 @@ Returns pre-ranked rows where the spread between the highest-funding venue and t
 ### B. Single symbol per-venue rates
 
 ```bash
-vike perp funding --symbol BTC --json
+vike-data perp funding --symbol BTC --json
 ```
 
 Returns one row per venue: `{exchange, funding_rate_daily_pct, mark_price, ...}`.
@@ -39,7 +39,7 @@ spread_daily_pct = 0.42%   →  ~$420/day per $100k notional, gross
                               (before fees, slippage, transfer costs)
 ```
 
-A funding arb at 0.4–1% daily is real. > 3% daily on a liquid pair is almost always a halted-trading / venue-mispricing artifact — verify with `vike perp spreads --symbol <sym>` to make sure the underlying spot/perp prices are sane.
+A funding arb at 0.4–1% daily is real. > 3% daily on a liquid pair is almost always a halted-trading / venue-mispricing artifact — verify with `vike-data perp spreads --symbol <sym>` to make sure the underlying spot/perp prices are sane.
 
 ## Anti-patterns