@vike-io/cli 0.5.0

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

@@ -0,0 +1,74 @@
+---
+name: vike-smart-money-discovery
+description: Multi-signal smart money discovery — find wallets currently accumulating a token, ranked by realized PnL track record. Use when the user asks "is smart money buying X" / "find smart money on Y chain" / "any alpha wallets in Z".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-smart-money-discovery
+
+Composite playbook — combines wallet leaderboards + token-side buyer list + label inspection.
+
+## Workflow
+
+### A. Top realized-PnL wallets on a chain
+
+```bash
+vike wallet discover --sort pnl --window 90d --chain ethereum --size 20 --json
+```
+
+Keep only rows where:
+- `realized_pnl_usd > 100_000` (real conviction, not noise)
+- `tx_count > 20` (not a single lucky trade)
+- `label` is empty OR not a known CEX (these are real wallets, not exchanges)
+
+That set = your "smart money universe" for the next step.
+
+### B. Cross-reference with a specific token
+
+If the user asks about a specific token, resolve it first:
+
+```bash
+vike 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
+```
+
+**Intersect** the buyer addresses with your smart-money universe from step A. Any overlap = a smart-money wallet currently accumulating this token.
+
+### C. Profile each match
+
+For every overlap address, run:
+
+```bash
+vike wallet summary <addr> --json
+```
+
+Report:
+- Address
+- Known label (if any)
+- 90d realized PnL
+- 7d net flow on this token
+- 30d total volume
+
+## Verdict template
+
+> **Smart-money take on $TOKEN:** N of top-20 90d-PnL wallets (>$100k realized) bought $TOKEN in the last 7 days. Strongest names: `<addr1> (+$X PnL, label?)`, `<addr2> ...`. Aggregate net flow into $TOKEN from this cohort: $Y. **Read: accumulation / churn / no-signal.**
+
+## Anti-patterns
+
+- Don't accept any wallet labeled as a CEX (binance/coinbase/bybit/etc.) as "smart money" — they're aggregators.
+- Don't lower the PnL threshold to <$50k just to find more matches; below that, signal-to-noise is poor.
+- Single-token wallets (`unique_tokens < 3`) are usually airdrop-flippers, not strategic.
+
+## Cost note
+
+3 calls per discovery: 1× `wallet discover`, 1× `token transfers`, then 1× `wallet summary` per match (cap at 5).
+
+## Pairs well with
+
+- `vike-token-research` for the price/flow context
+- `vike-perp-funding-arb` if the token has a perp listing (positioning bias)

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

@@ -0,0 +1,45 @@
+---
+name: vike-token-holders
+description: Top holders of an ERC-20 token by cumulative net inflow USD, with known labels. Use when the user asks "top holders of X" / "who holds the most of token Y" / "is whale Z holding token A".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-token-holders
+
+## Command
+
+```bash
+vike 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
+# Then holders:
+vike token holders 0x6982508145454ce325ddbe47a25d4ec3d2311933 --limit 20
+```
+
+## Output columns
+
+`wallet`, `net_flow_usd` (lifetime), `volume_usd` (lifetime), `tx_count`, `first_seen`, `last_active`, `entity`, `wallet_type`
+
+## Reading
+
+- **Sorted descending by `net_flow_usd`** — the biggest accumulators are at the top
+- A row with `entity = "Binance"` is a CEX hot/cold wallet — these aggregate millions of retail holders, not single discretionary positions
+- `first_seen` earlier than the token's launch month = wallet was active before this token existed; probably an aggregator
+- Two wallets with similar `net_flow_usd` but very different `tx_count`: low-tx = single buy-and-hold; high-tx = active trader
+
+## Anti-patterns
+
+- "Top holders" here means cumulative net inflow over all time — NOT current on-chain balance (which would require querying the contract directly). A wallet that bought $10M and sold $9M shows `net_flow_usd = $1M`, even if current balance is zero. **Always call this out** when reporting top holders.
+- Don't list `tx_count = 1` whales as "smart money" without context — could be an airdrop receiver who never sold.
+- For BSC tokens, pass `--chain bsc` explicitly; default is ethereum.
+
+## 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

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

@@ -0,0 +1,55 @@
+---
+name: vike-token-research
+description: Full token research playbook — search → transfers → chart → flow direction → buyer/seller verdict. Use when the user asks "research <token>" or "what's happening with <token>".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-token-research
+
+Multi-call token research workflow.
+
+## Steps
+
+1. **Resolve address** (skip if user already gave one)
+   ```bash
+   vike 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
+   ```
+
+3. **Price action**
+   ```bash
+   vike token chart <addr> --interval 30 --json
+   ```
+
+## Verdict heuristics
+
+After step 2, classify direction-of-pressure:
+
+| Buyer count vs seller count (24h) | Verdict |
+|---|---|
+| Buyers > 2× sellers and net inflow > $1M | **Accumulation** |
+| Sellers > 2× buyers and net outflow > $1M | **Distribution** |
+| Roughly even (within 1.5×) | **Churn / range-bound** |
+| Both very low | **Illiquid — skip the read** |
+
+Cross-check against the chart: distribution + falling price = bearish; accumulation + flat price = stealth bid (interesting).
+
+## Anti-patterns
+
+- Don't run `transfers --period 30d` first — use 24h to see what's happening *now*; 30d for context only if needed.
+- Don't quote the first row of `token search` blindly — if the symbol has cross-chain collisions (`FUN`, `BEAM`, `LDO`), inspect `chain` + `address` for each result before picking.
+
+## Cost note
+
+Step 1: cheap. Step 2: 2× cheap. Step 3: cheap. Total ≈ 4 calls.
+
+## Pairs well with
+
+- `vike-smart-money-discovery` to find which smart wallets are involved
+- `vike-perp-funding-arb` if the token has a perp listing (BTC/ETH/SOL/major alts)

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

@@ -0,0 +1,40 @@
+---
+name: vike-token-search
+description: Resolve a token symbol or name into the canonical contract address + chain + metadata. Use this BEFORE any other token command — most tools need the address, not the symbol.
+allowed-tools: Bash(vike:*)
+---
+
+# vike-token-search
+
+Symbol/name → address resolver.
+
+## Command
+
+```bash
+vike token search <query> [--chain ethereum|bsc|base] [--limit N] [--json]
+```
+
+## Example
+
+```bash
+vike token search PEPE --chain ethereum --limit 5
+# →  symbol  name    address                                     chain
+#    PEPE    Pepe    0x6982508145454ce325ddbe47a25d4ec3d2311933  ethereum
+#    PEPE2   ...     0x...                                       ethereum
+```
+
+## When to use
+
+- Any time the user mentions a token by symbol — always confirm the address before downstream calls.
+- The default chain is **ethereum**; if the user asks "what's the address of CAKE", default to **bsc** if the symbol is bsc-native.
+
+## Anti-patterns
+
+- Do not hardcode addresses you "remember" — symbols collide across chains and tokens. Always resolve.
+- If `--limit 1` returns the wrong token, increase to 5-10 and pick the highest-volume / canonical match. The first row is not always the canonical one.
+
+## Pairs well with
+
+- `vike token transfers <address>` after resolution
+- `vike token chart <address>`
+- `vike-token-research` for a full multi-call report

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

@@ -0,0 +1,43 @@
+---
+name: vike-token-transfers
+description: Top buyers or top sellers of a specific token over a window. Use when the user asks "who bought X" / "who sold X" / "is whale Y buying Z".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-token-transfers
+
+## Command
+
+```bash
+vike token transfers <token_address>
+  [--tab bought|sold]
+  [--period 1h|24h|7d|30d]
+  [--chain ethereum|bsc|base|all]
+  [--json]
+```
+
+## When to use
+
+- "Who's accumulating X?" → `--tab bought --period 24h`
+- "Who's dumping X?" → `--tab sold --period 24h`
+- "Smart money on X this week" → `--tab bought --period 7d`, then cross-reference labels
+
+## Output columns
+
+Each row is one wallet: `address`, `qty`, `usd_value`, `label` (if known), `tx_count`.
+
+## 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>`.
+- Many small transfers from labeled exchanges = retail flow via that CEX (Binance, Coinbase, etc.).
+
+## Anti-patterns
+
+- Don't request `--chain all` unless you really need cross-chain — it's slower and returns more rows.
+- 1h period is sparse for low-liquidity tokens. Use 24h as the default starting window.
+
+## Pairs well with
+
+- `vike wallet summary <addr>` to profile any interesting buyer/seller
+- `vike token chart <addr>` to correlate flows with price action

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

@@ -0,0 +1,60 @@
+---
+name: vike-wallet-balances
+description: Current ERC-20 token balances for a wallet across major EVM chains (eth, bsc, base, arbitrum, polygon, optimism). Dust filtered. Use when the user asks "what does this wallet hold" / "current portfolio of X" / "show top holdings".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-wallet-balances
+
+## Command
+
+```bash
+vike wallet balances <address>
+  [--chains eth,bsc,base,arbitrum,polygon,optimism]  (default = all 6)
+  [--min-usd 1]   (filter dust below this)
+  [--json]
+```
+
+## Example
+
+```bash
+vike wallet balances 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --chains eth,arbitrum
+```
+
+## Output
+
+```json
+{
+  "address": "0x...",
+  "total_usd": 123456.78,
+  "chains_scanned": ["eth", "bsc", "base", "arbitrum", "polygon", "optimism"],
+  "holdings": [
+    { "chain": "eth", "symbol": "WETH", "name": "Wrapped Ether", "address": "0xc02a...", "balance": "12.34", "usd_value": 26345.67, "usd_price": 2134.94 },
+    { "chain": "arbitrum", "symbol": "USDC", "address": "0xaf88...", "balance": "5000.00", "usd_value": 5000.00, "usd_price": 1.0 },
+    ...
+  ]
+}
+```
+
+Holdings sorted by `usd_value` descending.
+
+## Reading
+
+- `total_usd` = sum across all chains scanned. Wallet might still hold value on chains not scanned (e.g. zkSync, Linea) — say so when relevant.
+- Stablecoin-heavy wallet → likely waiting for a buy / parked dry powder
+- WETH/WBTC + LSTs (stETH, wstETH, rETH) → "saver" wallet, low-risk
+- 50+ random tokens → airdrop farmer
+- Empty `holdings` array → either no balance OR the address hasn't been indexed yet (very new wallets)
+
+## Anti-patterns
+
+- This is ERC-20 only — does NOT include native ETH/BNB/MATIC (would need separate calls; not in our current tool surface). Mention this when reporting "total holdings".
+- Don't combine with `defi_positions` totals naively — there's overlap (e.g. aUSDC shows in `balances`, the Aave deposit shows in `defi_positions`; you'd double-count).
+- For wallets with 100+ tokens, the response is large — use `--min-usd 100` or higher to focus on meaningful holdings.
+
+## Pairs well with
+
+- `vike defi <addr>` — protocol positions (Aave/Uniswap LP/Lido) alongside spot balances
+- `vike wallet pnl-history <addr>` — how the wallet got to its current state
+- `vike labels <addr>` — institutional context
+- `vike wallet ens <addr>` — friendly identifier

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

@@ -0,0 +1,48 @@
+---
+name: vike-wallet-counterparties
+description: Find the top trading partners of a wallet — who it sent to and received from, ranked by combined USD volume. Use when the user asks "who does this wallet trade with" / "main counterparties of X" / "find connections between wallets".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-wallet-counterparties
+
+## Command
+
+```bash
+vike wallet counterparties <address>
+  [--chain ethereum|bsc|base]
+  [--window 24h|7d|30d|90d|180d|all]
+  [--limit N]   (max 50)
+  [--json]
+```
+
+## Example
+
+```bash
+vike wallet counterparties 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 --window 30d
+```
+
+## Output columns
+
+`wallet`, `total_volume_usd`, `sent_usd`, `received_usd`, `tx_count`, `first_seen`, `last_seen`, `entity`, `wallet_type`
+
+## Reading
+
+- **Sent + Received roughly equal** = active trading partner (DEX router, MM, regular counterparty)
+- **Sent >> Received** = wallet pays this counterparty (deposit address, contract call)
+- **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`
+
+## Anti-patterns
+
+- Don't claim two wallets are "controlled by the same person" from counterparties alone — many people deposit to the same Binance address. Pair with `vike-wallet-clustering` (deferred) or manual investigation.
+- Window matters: a 24h view captures recent activity but misses long-standing relationships. Default to 30d, expand to `all` for full history.
+- For tokens with high churn (memecoins), top counterparties will be dominated by Uniswap routers; filter mentally for non-DEX rows for human counterparties.
+
+## 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

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

@@ -0,0 +1,49 @@
+---
+name: vike-wallet-discover
+description: Rank wallets by volume / inflow / outflow / pnl / net_flow / tx_count across a time window. Use when the user asks "top wallets on X" / "best traders by PnL" / "biggest buyers last 7d".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-wallet-discover
+
+## Command
+
+```bash
+vike wallet discover
+  [--window 24h|7d|30d|90d|all]
+  [--sort volume|inflow|outflow|net_flow|tx_count|pnl]
+  [--order asc|desc]
+  [--chain ethereum|bsc]
+  [--size N]      # max 20
+  [--json]
+```
+
+## When to use
+
+| Question | Flags |
+|---|---|
+| "Top whales by volume this week" | `--sort volume --window 7d` |
+| "Biggest accumulators last 30d" | `--sort net_flow --window 30d --order desc` |
+| "Top realized-PnL traders all-time" | `--sort pnl --window all` |
+| "Wallets dumping the most this 24h" | `--sort outflow --window 24h` |
+| "Most active traders last 7d" | `--sort tx_count --window 7d` |
+
+## Output columns
+
+`address`, `label` (when known), `volume_usd`, `inflow_usd`, `outflow_usd`, `net_flow_usd`, `tx_count`, `realized_pnl_usd`.
+
+## Reading tips
+
+- 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).
+
+## Anti-patterns
+
+- `--size > 20` is silently clamped to 20. Run a second call with offset (not currently supported — limit applies hard) if you need more.
+- `--sort pnl` is only meaningful on `--window 30d` or longer; 24h PnL is noise.
+
+## Pairs well with
+
+- `vike 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

@@ -0,0 +1,41 @@
+---
+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:*)
+---
+
+# vike-wallet-ens
+
+## Command
+
+```bash
+vike wallet ens <address> [--json]
+```
+
+## Example
+
+```bash
+vike wallet ens 0xd8da6bf26964af9d7eed9e03e53415d37aa96045
+# → { "address": "0xd8da...", "ens": "vitalik.eth" }
+
+vike wallet ens 0x28c6c06298d514db089934071355e5743bf21d60
+# → { "address": "0x28c6...", "ens": null }      (most exchange wallets have no ENS)
+```
+
+## When to use
+
+- Right after any tool returns a wallet address — show ENS as a secondary label
+- When the user pastes an address and asks "who is this"
+- When you're about to display a leaderboard with addresses — enrich each row with ENS if available
+
+## Anti-patterns
+
+- Don't replace the address with the ENS name in tool output — show BOTH. The address is canonical; ENS is a display layer that can change ownership.
+- Don't ENS-lookup hundreds of addresses in a leaderboard at once — credits add up. Usually ENS-lookup only the top 5-10 rows the user is likely to act on.
+- A `null` response is normal, not an error. Most wallets don't have ENS.
+
+## Pairs well with
+
+- `vike labels <addr>` — combine ENS + labels for the fullest identity view
+- `vike wallet summary <addr>` — ENS + activity profile
+- `vike funds` — pair with ENS lookups on the top entries for richer display

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

@@ -0,0 +1,65 @@
+---
+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:*)
+---
+
+# vike-wallet-label-provenance
+
+The headline differentiator: we don't just show a label, we show **which sources agree** and how confident the consensus is.
+
+## Command
+
+```bash
+vike labels <address> [--json]
+```
+
+## Example
+
+```bash
+vike labels 0x28C6c06298d514Db089934071355E5743bf21d60     # Binance Hot Wallet 14
+```
+
+## Output shape
+
+```json
+{
+  "address": "0x...",
+  "found": true,
+  "consensus": {
+    "entity": "Binance",
+    "wallet_type": "cex",
+    "cex_product": "spot",
+    "user_subtype": "",
+    "risk_flag": "",
+    "confidence": "High"
+  },
+  "sources": [
+    { "source": "provider_a", "label": "Binance 14",        "entity": "Binance", "category": "CEX" },
+    { "source": "provider_b", "label": "Binance Hot Wallet" },
+    { "source": "provider_c", "label": "Binance: Hot Wallet 14" },
+    { "source": "provider_d", "label": "Binance" },
+    { "source": "heuristic:cold_t1", "confidence": 0.94 }
+  ],
+  "source_count": 5
+}
+```
+
+## Reading
+
+- **5+ sources agree** → very high confidence; ship the label without caveats
+- **2-3 sources agree on same entity** → high confidence
+- **Only 1 source + heuristic** → moderate; mention "labeled by X"
+- **0 sources, only heuristic** → low; mention "predicted by heuristic"
+- **0 sources, no heuristic** → genuinely unknown wallet (most retail addresses)
+
+## Anti-patterns
+
+- Don't quote any single provider's category field as "the category" — provider taxonomies vary; the `consensus.wallet_type` is the unified field.
+- A `risk_flag` of `scam` / `sanctioned` / `phishing` is high-stakes — always mention it explicitly, never bury it.
+
+## Pairs well with
+
+- `vike wallet summary <addr>` — for the flow metrics of the labeled wallet
+- `vike funds` — find all known fund wallets and their recent flows
+- `vike defi <addr>` — see what protocols this entity is using

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

@@ -0,0 +1,58 @@
+---
+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:*)
+---
+
+# vike-wallet-pnl-history
+
+## Command
+
+```bash
+vike wallet pnl-history <address>
+  [--chain ethereum|bsc|base]
+  [--days N]   (max 365, default 30)
+  [--json]
+```
+
+## Output
+
+```json
+{
+  "address": "0x...",
+  "chain": "ethereum",
+  "days": 30,
+  "total_net_flow_usd": 12345.67,
+  "series": [
+    { "date": "2026-04-25", "net_flow_usd": +120.50, "gross_volume_usd": 1500, "tx_count": 4, "unique_tokens": 2, "cumulative_net_flow_usd": 120.50 },
+    { "date": "2026-04-26", "net_flow_usd": -50.30,  "gross_volume_usd": 800,  "tx_count": 2, "unique_tokens": 1, "cumulative_net_flow_usd": 70.20 },
+    ...
+  ]
+}
+```
+
+## Important caveat
+
+**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`.
+
+## Reading
+
+- `cumulative_net_flow_usd` ramping up = wallet has been accumulating $
+- Big positive day with high `tx_count` = single large buy (deposit / acquisition / token purchase)
+- Big negative day with high `tx_count` = sell-down or large transfer out
+- `unique_tokens > 5` on a single day = farmer / spray-and-pray / airdrop claim
+- All `net_flow_usd` near zero with high `gross_volume_usd` = market-maker / churn
+
+## Anti-patterns
+
+- Don't report this as "realized PnL" — it isn't.
+- Big single-day spikes can be legitimate (token unlock, ICO buy, airdrop claim) — don't auto-flag without context
+- A `null` or empty series means the wallet has no activity on the requested chain in the window — surface that honestly
+
+## Pairs well with
+
+- `vike wallet summary <addr>` for the aggregate context
+- `vike wallet counterparties <addr>` to see WHO they traded with
+- `vike token chart <addr>` to correlate flow spikes with price action

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

@@ -0,0 +1,61 @@
+---
+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:*)
+---
+
+# vike-wallet-portfolio
+
+Multi-call playbook for a complete wallet snapshot.
+
+## Workflow (run in parallel where possible)
+
+```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 defi           $ADDR --json &     # multi-chain, ~3 credits
+vike wallet pnl-history $ADDR --days 30 --json &
+wait
+```
+
+## Report template
+
+> **`<ENS or 0x...>` — wallet snapshot**
+> - **Identity:** `<ens.eth>` · `<entity (from labels)>` · `<wallet_type>` (confidence: `<H/M/L>`)
+> - **Total ERC-20:** `$X` across `<chains>`. Top 3 by USD: `<symbol1 $X>`, `<symbol2 $Y>`, ...
+> - **DeFi positions:** `$Y` across `<protocols count>` protocols. Top: `<Aave V3 $X>`, ...
+> - **30d net flow:** `+/-$Z` (cumulative)
+> - **Activity:** `<tx_count>` txns last 30d, `<unique_tokens>` unique tokens traded
+> - **Vibe check:** `<saver / trader / farmer / institutional / inactive / fresh>`
+
+## Vibe-check rubric
+
+| Pattern | Label |
+|---|---|
+| `wallet_type = "cex"` or `"market_maker"` | **Institutional** |
+| 80%+ in stablecoins, low tx count | **Saver / dry powder** |
+| 50+ unique tokens 30d, low avg holding USD | **Airdrop farmer** |
+| High tx count, balanced sent/received | **Active trader** |
+| Big DeFi positions, low ERC-20 balance | **DeFi native** |
+| Big ERC-20 holdings, no DeFi | **HODLer** |
+| Zero activity 30d | **Inactive** |
+| First-seen < 30d ago | **Fresh wallet** |
+
+## Cost
+
+~6 parallel calls, ~12 credits total. Use sparingly — only when the user wants the FULL picture, not a single dimension.
+
+## When to use a focused skill instead
+
+- "Just labels for X" → `vike-wallet-label-provenance`
+- "What does X hold" → `vike-wallet-balances`
+- "Top counterparties of X" → `vike-wallet-counterparties`
+- "DeFi positions of X" → `vike-defi-positions`
+
+## Pairs well with
+
+- `vike-smart-money-discovery` to put the wallet in context vs the broader top-PnL cohort