@vike-io/cli 0.12.0 → 0.13.0

package/skills/vike/SKILL.md

@@ -5,11 +5,17 @@ description: "Use this skill whenever the user asks any question about on-chain
 
 # vike — Multi-chain On-chain Analytics
 
+This skill is for anyone who asks an AI agent about crypto data: who is buying a token, what a wallet holds, what Hyperliquid or Polymarket traders are doing right now. It tells the agent which vike tool answers which question and how to read the result, so it does not guess or invent numbers. It reads its data from vike.io and needs a free vike API key.
+
 Answer on-chain questions using the vike.io platform: 11 chains (ETH, BSC, Base, Arbitrum, HyperEVM, BTC, Solana, Tron, XMR, ZEC, Dash), full Hyperliquid perps coverage, CEX perps across 5 venues, Polymarket prediction markets, multi-source wallet labels, and a 34-tool MCP server.
 
 **MCP endpoint for all calls:** `https://vike.io/mcp` (JSON-RPC 2.0)
 **Or use the CLI:** `npm install -g @vike-io/cli` → `vike <command>`
 
+## What it does and who it is for
+
+It is for traders, researchers and developers who use an AI agent to look at crypto data. With this skill the agent knows which vike tool to call for wallets, tokens, smart money, Hyperliquid perps, Polymarket markets and alerts. It also knows how to read each answer and what the tools cannot do, so it reports real numbers instead of guesses. The data comes from vike.io and a free vike API key is needed.
+
 ---
 
 ## Critical Rules
@@ -32,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).
 ```
 
@@ -48,12 +54,12 @@ 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.
 
-If using the MCP server directly (without the CLI), send the key as a header:
+If using the MCP server directly (without the CLI), authenticate with the key in this header:
 ```
 X-API-KEY: vk_...
 ```
@@ -64,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
 ```
@@ -114,44 +120,29 @@ 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 MCP JSON-RPC (recommended when an MCP connector is available).** All 34 tools live at `https://vike.io/mcp`:
-```http
-POST https://vike.io/mcp
-X-API-KEY: vk_...
-Content-Type: application/json
-
-{
-  "jsonrpc": "2.0",
-  "id": 1,
-  "method": "tools/call",
-  "params": {
-    "name": "wallet_summary",
-    "arguments": {"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", "chain": "ethereum"}
-  }
-}
-```
+**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.
 
 ---
 
 ## Per-service tool reference
 
-For deeper per-tool workflows (multi-step recipes, common pitfalls, output schemas), see the `skills/` directory in this repo. The router lives at [`skills/vike-router/SKILL.md`](skills/vike-router/SKILL.md).
+For deeper per-tool workflows (multi-step recipes, common pitfalls, output schemas), see the `skills/` directory in this repo. The router lives at `vike-router`.
 
 ### Tokens
 Address resolution, transfers, holder cohorts, screening.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `token_search` | Symbol/name → contract address + chain + market cap | [vike-token-search](skills/vike-token-search/SKILL.md) |
-| `token_transfers` | Recent transfers with USD values; supports `--min-usd`, time windows | [vike-token-transfers](skills/vike-token-transfers/SKILL.md) |
-| `token_holders` | Top holders + concentration metrics | [vike-token-holders](skills/vike-token-holders/SKILL.md) |
-| `token_screener` | Filter tokens by smart-money inflow, age, liquidity, sector | [vike-token-screener](skills/vike-token-screener/SKILL.md) |
+| `token_search` | Symbol/name → contract address + chain + market cap | `vike-token-search` |
+| `token_transfers` | Recent transfers with USD values; supports `--min-usd`, time windows | `vike-token-transfers` |
+| `token_holders` | Top holders + concentration metrics | `vike-token-holders` |
+| `token_screener` | Filter tokens by smart-money inflow, age, liquidity, sector | `vike-token-screener` |
 
 **Key chains:** `ethereum`, `bsc`, `base`, `arbitrum`, `hyperevm` (EVM); `bitcoin`, `solana`, `tron`, `xmr`, `zec`, `dash` (non-EVM, limited tool support).
 
@@ -162,16 +153,16 @@ Profile, PnL, transactions, comparison, tracing, counterparty graph.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `wallet_summary` | One-call profile: PnL, top holdings, recent activity, labels | [vike-wallet-summary](skills/vike-wallet-summary/SKILL.md) |
-| `wallet_discover` | Leaderboard of top wallets by PnL/inflow on a token | [vike-wallet-discover](skills/vike-wallet-discover/SKILL.md), [vike-smart-money-discovery](skills/vike-smart-money-discovery/SKILL.md) |
-| `wallet_transactions` | Raw recent transactions (tx_hash, ts, from, to, token, usd) | [vike-wallet-transactions](skills/vike-wallet-transactions/SKILL.md) |
-| `wallet_compare` | Side-by-side metrics for 2+ wallets | [vike-wallet-compare](skills/vike-wallet-compare/SKILL.md) |
-| `wallet_trace` | BFS funds tracing N hops from a starting wallet | [vike-wallet-trace](skills/vike-wallet-trace/SKILL.md) |
-| `wallet_counterparties` | Top counterparties (who they send to / receive from) | [vike-wallet-counterparties](skills/vike-wallet-counterparties/SKILL.md) |
-| `wallet_pnl_history` | Daily PnL timeseries over `--days N` | [vike-wallet-pnl-history](skills/vike-wallet-pnl-history/SKILL.md) |
-| `wallet_token_balances` | Current token balances (Moralis-backed) | [vike-wallet-balances](skills/vike-wallet-balances/SKILL.md) |
-| `wallet_ens` | ENS name ↔ address (local cache: 477K wallets pre-resolved) | [vike-wallet-ens](skills/vike-wallet-ens/SKILL.md) |
-| `wallet_batch_labels` | Bulk-label up to 100 addresses in one call | [vike-wallet-batch](skills/vike-wallet-batch/SKILL.md) |
+| `wallet_summary` | One-call profile: PnL, top holdings, recent activity, labels | `vike-wallet-summary` |
+| `wallet_discover` | Leaderboard of top wallets by PnL/inflow on a token | `vike-wallet-discover`, `vike-smart-money-discovery` |
+| `wallet_transactions` | Raw recent transactions (tx_hash, ts, from, to, token, usd) | `vike-wallet-transactions` |
+| `wallet_compare` | Side-by-side metrics for 2+ wallets | `vike-wallet-compare` |
+| `wallet_trace` | BFS funds tracing N hops from a starting wallet | `vike-wallet-trace` |
+| `wallet_counterparties` | Top counterparties (who they send to / receive from) | `vike-wallet-counterparties` |
+| `wallet_pnl_history` | Daily PnL timeseries over `--days N` | `vike-wallet-pnl-history` |
+| `wallet_token_balances` | Current token balances (Moralis-backed) | `vike-wallet-balances` |
+| `wallet_ens` | ENS name ↔ address (local cache: 477K wallets pre-resolved) | `vike-wallet-ens` |
+| `wallet_batch_labels` | Bulk-label up to 100 addresses in one call | `vike-wallet-batch` |
 
 **Address shape:** always full 0x-prefixed hex (42 chars). Never truncate when reporting back to the user.
 
@@ -182,7 +173,7 @@ Wallet label provenance.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `wallet_label_provenance` | Why a wallet got a given label (sources + confidence) | [vike-wallet-label-provenance](skills/vike-wallet-label-provenance/SKILL.md) |
+| `wallet_label_provenance` | Why a wallet got a given label (sources + confidence) | `vike-wallet-label-provenance` |
 
 Vike's label cascade is multi-source — when an answer hinges on "is this really a CEX hot wallet?", call `wallet_label_provenance` rather than trusting a single source.
 
@@ -193,8 +184,8 @@ Vike's label cascade is multi-source — when an answer hinges on "is this reall
 
 | Tool | Description | Skill |
 |---|---|---|
-| `perp_funding` | Funding rates per symbol per venue + 24h/7d averages | [vike-perp-funding-arb](skills/vike-perp-funding-arb/SKILL.md) |
-| `perp_spreads` | Mark-price spreads of the same symbol across venues | [vike-perp-spread-arb](skills/vike-perp-spread-arb/SKILL.md), [vike-cross-venue-perps](skills/vike-cross-venue-perps/SKILL.md) |
+| `perp_funding` | Funding rates per symbol per venue + 24h/7d averages | `vike-perp-funding-arb` |
+| `perp_spreads` | Mark-price spreads of the same symbol across venues | `vike-perp-spread-arb`, `vike-cross-venue-perps` |
 
 ---
 
@@ -203,10 +194,10 @@ On-chain perps data: snapshots, fills, ledger, funding, attribution.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `hl_perp_top_traders` | Top HL traders by PnL/volume over a window | [vike-hl-top-traders](skills/vike-hl-top-traders/SKILL.md), [vike-hl-trader-profile](skills/vike-hl-trader-profile/SKILL.md) |
-| `hl_position_match` | Reverse-lookup: share-card details (coin/side/lev/entry) → wallet holding that open position | [vike-hl-position-match](skills/vike-hl-position-match/SKILL.md) |
+| `hl_perp_top_traders` | Top HL traders by PnL/volume over a window | `vike-hl-top-traders`, `vike-hl-trader-profile` |
+| `hl_position_match` | Reverse-lookup: share-card details (coin/side/lev/entry) → wallet holding that open position | `vike-hl-position-match` |
 
-For per-symbol HL screening / individual trader deep-dive, use [vike-perp-screener](skills/vike-perp-screener/SKILL.md) and [vike-hl-trader-profile](skills/vike-hl-trader-profile/SKILL.md).
+For per-symbol HL screening / individual trader deep-dive, use `vike-perp-screener` and `vike-hl-trader-profile`.
 
 ---
 
@@ -215,8 +206,8 @@ Historical OHLCV from venues whose data is on-chain.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `hl_ohlcv` | Hyperliquid perp or spot candles, 1m–1d, built from HL's own executed fills (also HIP-3 builder DEXs) | [vike-candles](skills/vike-candles/SKILL.md) |
-| `polymarket_ohlcv` | Candles for ONE Polymarket outcome token (price = probability, 0–1); needs `token_id`, not a condition_id | [vike-candles](skills/vike-candles/SKILL.md) |
+| `hl_ohlcv` | Hyperliquid perp or spot candles, 1m–1d, built from HL's own executed fills (also HIP-3 builder DEXs) | `vike-candles` |
+| `polymarket_ohlcv` | Candles for ONE Polymarket outcome token (price = probability, 0–1); needs `token_id`, not a condition_id | `vike-candles` |
 
 ---
 
@@ -225,10 +216,10 @@ Prediction markets — markets, traders, smart-money.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `polymarket_markets` | Active markets sorted by volume / liquidity / volatility | [vike-polymarket-markets](skills/vike-polymarket-markets/SKILL.md), [vike-polymarket-screener](skills/vike-polymarket-screener/SKILL.md) |
-| `polymarket_market_detail` | Single market: outcomes, holders, recent trades, time-to-resolution | [vike-polymarket-market-detail](skills/vike-polymarket-market-detail/SKILL.md) |
-| `polymarket_wallet` | One trader's positions, PnL, win rate | [vike-polymarket-trader](skills/vike-polymarket-trader/SKILL.md) |
-| `polymarket_smart_money` | Top-PnL Polymarket traders + their current open positions | [vike-polymarket-smart-money](skills/vike-polymarket-smart-money/SKILL.md) |
+| `polymarket_markets` | Active markets sorted by volume / liquidity / volatility | `vike-polymarket-markets`, `vike-polymarket-screener` |
+| `polymarket_market_detail` | Single market: outcomes, holders, recent trades, time-to-resolution | `vike-polymarket-market-detail` |
+| `polymarket_wallet` | One trader's positions, PnL, win rate | `vike-polymarket-trader` |
+| `polymarket_smart_money` | Top-PnL Polymarket traders + their current open positions | `vike-polymarket-smart-money` |
 
 ---
 
@@ -237,12 +228,12 @@ Create + manage alerts; deliver to email, Telegram, Discord, Webhook.
 
 | Tool | Description | Skill |
 |---|---|---|
-| `alerts_list` | List user's existing alerts | [vike-alerts-setup](skills/vike-alerts-setup/SKILL.md) |
-| `alerts_create` | Create a new price/transfer/funding alert | [vike-alerts-setup](skills/vike-alerts-setup/SKILL.md) |
-| `alerts_edit` | Edit an existing alert | [vike-alerts-setup](skills/vike-alerts-setup/SKILL.md) |
-| `alerts_delete` | Delete an alert | [vike-alerts-setup](skills/vike-alerts-setup/SKILL.md) |
-| `alerts_list_channels` | List user's registered delivery channels | [vike-alerts-setup](skills/vike-alerts-setup/SKILL.md) |
-| `alerts_register_webhook` | Register an HTTPS webhook (HMAC-signed deliveries) | [vike-alerts-webhook](skills/vike-alerts-webhook/SKILL.md) |
+| `alerts_list` | List user's existing alerts | `vike-alerts-setup` |
+| `alerts_create` | Create a new price/transfer/funding alert | `vike-alerts-setup` |
+| `alerts_edit` | Edit an existing alert | `vike-alerts-setup` |
+| `alerts_delete` | Delete an alert | `vike-alerts-setup` |
+| `alerts_list_channels` | List user's registered delivery channels | `vike-alerts-setup` |
+| `alerts_register_webhook` | Register an HTTPS webhook (HMAC-signed deliveries) | `vike-alerts-webhook` |
 
 Alerts fire on a 2-minute cron cycle (not streaming). Don't recommend WebSocket / push streaming — it's not how the platform works.
 

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

@@ -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

@@ -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

@@ -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,6 +1,6 @@
 ---
 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:
@@ -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

@@ -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

@@ -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,10 +77,10 @@ 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
 
-- [vike-wallet-summary](../vike-wallet-summary/SKILL.md) — once you have the address, get the trader's HL profile + multi-chain identity.
-- [vike-hl-top-traders](../vike-hl-top-traders/SKILL.md) — check if the matched wallet is on a leaderboard.
-- [vike-wallet-label-provenance](../vike-wallet-label-provenance/SKILL.md) — find out if the wallet is a known CEX/fund/MM rather than a retail trader.
+- `vike-wallet-summary` — once you have the address, get the trader's HL profile + multi-chain identity.
+- `vike-hl-top-traders` — check if the matched wallet is on a leaderboard.
+- `vike-wallet-label-provenance` — find out if the wallet is a known CEX/fund/MM rather than a retail trader.

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

@@ -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

@@ -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

@@ -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
 

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

@@ -11,9 +11,9 @@ One-shot market overview for perpetuals.
 ## Workflow (3 parallel calls)
 
 ```bash
-vike perp funding --json &              # top funding-arb opportunities
-vike perp spreads --json &              # top spot-perp price spreads
-vike perp top-traders --window 1d --sort pnl --size 10 --json &
+vike-data perp funding --json &              # top funding-arb opportunities
+vike-data perp spreads --json &              # top spot-perp price spreads
+vike-data perp top-traders --window 1d --sort pnl --size 10 --json &
 wait
 ```
 

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

@@ -9,8 +9,8 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike perp spreads --json                 # full matrix, all symbols with spread >= 0.5%
-vike perp spreads --symbol BTC --json    # one specific symbol
+vike-data perp spreads --json                 # full matrix, all symbols with spread >= 0.5%
+vike-data perp spreads --symbol BTC --json    # one specific symbol
 ```
 
 ## Output

package/skills/vike-polymarket-market-detail/SKILL.md

@@ -9,17 +9,17 @@ allowed-tools: Bash(vike:*)
 ## Command
 
 ```bash
-vike polymarket market <condition_id> [--json]
+vike-data polymarket market <condition_id> [--json]
 ```
 
-`condition_id` is a hex string (you'll have it from `vike polymarket markets` output).
+`condition_id` is a hex string (you'll have it from `vike-data polymarket markets` output).
 
 ## Example
 
 ```bash
-vike polymarket markets --category Crypto --limit 5 --json
+vike-data polymarket markets --category Crypto --limit 5 --json
 #   → pick a condition_id from the output, then:
-vike polymarket market 0x1234abcd...
+vike-data polymarket market 0x1234abcd...
 ```
 
 ## What it returns