nansen-cli 1.17.0 → 1.19.0

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # Changelog
 
+## 1.19.0
+
+### Minor Changes
+
+- [#306](https://github.com/nansen-ai/nansen-cli/pull/306) [`f685eb8`](https://github.com/nansen-ai/nansen-cli/commit/f685eb8b87d2915a7a94e8c1a3d92f84e4802e4a) Thanks [@0xlaveen](https://github.com/0xlaveen)! - Rename 30 skills for clarity and clawhub slug uniqueness. Abbreviations expanded (`pm` → `polymarket`, `sm` prefix added where relevant), ambiguous names made specific (`nansen-wallet` → `nansen-wallet-manager`, `nansen-profiler` → `nansen-wallet-profiler`, `nansen-search` → `nansen-general-search`, `nansen-trade` → `nansen-trading`, etc.).
+
+### Patch Changes
+
+- [#308](https://github.com/nansen-ai/nansen-cli/pull/308) [`569d7d4`](https://github.com/nansen-ai/nansen-cli/commit/569d7d43e428732d3c10b4e57368cb12ef0086c3) Thanks [@kome12](https://github.com/kome12)! - fix: include src subdirectories in npm package
+
+  The `files` field in package.json used `src/*.js` which only matched files directly in `src/`, causing `src/commands/` to be missing from the 1.18.0 publish. Changed to `src/**/*.js` to include all subdirectories recursively, and added `!src/__tests__/**` to exclude test files from the package.
+
+## 1.18.0
+
+### Minor Changes
+
+- [#265](https://github.com/nansen-ai/nansen-cli/pull/265) [`c3de691`](https://github.com/nansen-ai/nansen-cli/commit/c3de6914dcdd29f54d027f0cc415c23dd646c003) Thanks [@TimNooren](https://github.com/TimNooren)! - Add `nansen alerts` command for managing smart alerts (list, create, update, toggle, delete).
+
+  Supports three alert types: `sm-token-flows`, `common-token-transfer`, and `smart-contract-call`.
+  Named flags (`--inflow-1h-min`, `--chains`, `--telegram`, etc.) let you build alerts without raw JSON;
+  a `--data` escape hatch is available for full config overrides.
+
+  Also adds a `nansen-alerts` skill for agent integration.
+
+- [#295](https://github.com/nansen-ai/nansen-cli/pull/295) [`3ddcbde`](https://github.com/nansen-ai/nansen-cli/commit/3ddcbdec50d55e4477cd3f53c5064126dbd8580a) Thanks [@kome12](https://github.com/kome12)! - feat: add `nansen web search` and `nansen web fetch` commands (ECINT-6393)
+
+  - `nansen web search <query> [query...]` — search the web for one or more queries in parallel via `/api/v1/search/web-search`
+  - `nansen web fetch <url> [url...] --question <q>` — fetch and analyze URL content with AI via `/api/v1/search/web-fetch`
+
+### Patch Changes
+
+- [#293](https://github.com/nansen-ai/nansen-cli/pull/293) [`bcd95a8`](https://github.com/nansen-ai/nansen-cli/commit/bcd95a88942e96018337ae6b7de9f2abdbdc3464) Thanks [@TimNooren](https://github.com/TimNooren)! - Add default values for all required alert data fields to match backend schema
+
+- [#265](https://github.com/nansen-ai/nansen-cli/pull/265) [`c3de691`](https://github.com/nansen-ai/nansen-cli/commit/c3de6914dcdd29f54d027f0cc415c23dd646c003) Thanks [@TimNooren](https://github.com/TimNooren)! - Fix `alerts list` filtering (`--type`, `--enabled`, `--disabled`, `--chain`, `--token-address`, `--limit`, `--offset`).
+
+  Filters were sent as query params but silently ignored by the API. Now applied client-side after fetching all alerts.
+
+- [#301](https://github.com/nansen-ai/nansen-cli/pull/301) [`cda6796`](https://github.com/nansen-ai/nansen-cli/commit/cda6796642c588965111c53c583af2b21444d30b) Thanks [@kome12](https://github.com/kome12)! - fix: add missing openclaw metadata to 19 skills
+
+- [#294](https://github.com/nansen-ai/nansen-cli/pull/294) [`8a1cc7b`](https://github.com/nansen-ai/nansen-cli/commit/8a1cc7bdfbd9597860384dfd40fd28705e5c947c) Thanks [@yodablocks](https://github.com/yodablocks)! - fix: include skills/ directory in published npm package
+
 ## 1.17.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nansen-cli",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "description": "Command-line interface for Nansen API - designed for AI agents",
   "main": "src/index.js",
   "type": "module",
@@ -8,8 +8,10 @@
     "nansen": "./src/index.js"
   },
   "files": [
-    "src/*.js",
-    "src/*.json",
+    "src/**/*.js",
+    "src/**/*.json",
+    "!src/__tests__/**",
+    "skills/**",
     "CHANGELOG.md"
   ],
   "scripts": {

package/skills/nansen-dca-tracker/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: nansen-dca-tracker
+description: "What tokens are whales dollar-cost averaging into? Jupiter DCA strategies by smart money and target token fundamentals."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# DCA Watch
+
+**Answers:** "What tokens are whales dollar-cost averaging into on Solana?"
+
+```bash
+nansen research smart-money dcas --limit 20
+# → trader_address, trader_address_label, input/output_token_symbol, deposit_value_usd, dca_status, dca_created_at
+
+# For each top DCA target, check token fundamentals
+TARGET=<output_token_address>
+nansen research token info --token $TARGET --chain solana
+# → name, symbol, price, market_cap, token_details
+
+nansen research token flow-intelligence --token $TARGET --chain solana
+# → net_flow_usd per label: smart_trader, whale, exchange, fresh_wallets
+```
+
+To see DCA strategies targeting a specific token: `nansen research token jup-dca --token $TARGET`
+
+DCAs show long-term conviction — SM DCA targets with positive smart_trader_net_flow = high-confidence accumulation.

package/skills/nansen-defi-positions/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: nansen-defi-positions
+description: "What DeFi positions does a wallet hold? Protocol-by-protocol breakdown of assets, debts, and rewards across chains."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# DeFi Exposure
+
+**Answers:** "What DeFi positions does this wallet have across protocols?"
+
+```bash
+ADDR=<address>
+
+nansen research portfolio defi --wallet $ADDR
+# → protocol_name, chain, total_value_usd, total_assets_usd, total_debts_usd, total_rewards_usd, tokens
+
+nansen research profiler balance --address $ADDR --chain ethereum
+# → token_symbol, token_name, token_amount, value_usd per holding
+
+nansen research profiler balance --address $ADDR --chain base
+```
+
+Combine DeFi positions (lending, LPs, staking) with spot balances for a complete picture of on-chain exposure.
+
+Note: portfolio defi may return empty for wallets with no tracked DeFi positions.

package/skills/nansen-exit-signals/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: nansen-exit-signals
+description: "Is smart money exiting a token I hold? Net flow direction, seller breakdown by label, and recent SM trades."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Exit Signal
+
+**Answers:** "Is smart money exiting a token I hold? Should I be worried?"
+
+```bash
+TOKEN=<address> CHAIN=ethereum
+
+nansen research token flow-intelligence --token $TOKEN --chain $CHAIN
+# → net_flow_usd per label: smart_trader, whale, exchange, fresh_wallets (negative = selling)
+
+nansen research token who-bought-sold --token $TOKEN --chain $CHAIN --limit 20
+# → address, address_label, bought/sold_volume_usd, trade_volume_usd
+
+nansen research smart-money netflow --chain $CHAIN --limit 10
+# → token_symbol, net_flow_1h/24h/7d/30d_usd, trader_count
+
+nansen research token dex-trades --token $TOKEN --chain $CHAIN --limit 20
+# → block_timestamp, action (BUY/SELL), trader_address_label, estimated_value_usd
+```
+
+Red flag: negative smart_trader_net_flow_usd + Smart Trader labels in who-bought-sold sellers = exit signal.

package/skills/nansen-fund-tracker/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: nansen-fund-tracker
+description: "What are crypto funds and VCs holding right now? Cross-chain fund portfolios and net accumulation signals."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Fund Watch
+
+**Answers:** "What are crypto funds and VCs holding right now?"
+
+```bash
+nansen research smart-money holdings --chain ethereum --labels "Fund" --limit 20
+# → token_symbol, value_usd, holders_count, balance_24h_percent_change, share_of_holdings_percent
+
+nansen research smart-money holdings --chain solana --labels "Fund" --limit 20
+
+nansen research smart-money netflow --chain ethereum --labels "Fund" --limit 10
+# → token_symbol, net_flow_1h/24h/7d/30d_usd, market_cap_usd, trader_count
+
+nansen research smart-money netflow --chain solana --labels "Fund" --limit 10
+```
+
+Cross-reference holdings with netflow to see directional conviction. Positive net_flow_24h = active accumulation.

package/skills/nansen-general-search/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: nansen-general-search
+description: Search for tokens or entities by name. Use when you have a token name and need the full address, or want to find an entity.
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Search
+
+```bash
+nansen research search "jupiter" --type token
+nansen research search "Vitalik" --type entity --limit 5
+nansen research search "bonk" --chain solana --fields address,name,symbol,chain
+```
+
+| Flag | Purpose |
+|------|---------|
+| `--type` | `token` or `entity` |
+| `--chain` | Filter by chain |
+| `--limit` | Number of results (default 25, max 50) |
+| `--fields` | Select specific output fields |
+
+Case-insensitive. Does NOT match by address — use `profiler labels` for address lookup.

package/skills/nansen-holder-analysis/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: nansen-holder-analysis
+description: "Is this token held by quality wallets or retail noise? SM holder ratio, flow breakdown by label, and recent buyer quality."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Holder Quality
+
+**Answers:** "Is this token held by quality wallets or retail noise?"
+
+```bash
+TOKEN=<address> CHAIN=ethereum
+
+nansen research token holders --token $TOKEN --chain $CHAIN --smart-money --limit 20
+# → address, address_label, value_usd, ownership_percentage, balance_change_24h/7d/30d
+
+nansen research token flow-intelligence --token $TOKEN --chain $CHAIN
+# → net_flow_usd and wallet_count per label: smart_trader, whale, exchange, fresh_wallets
+
+nansen research token who-bought-sold --token $TOKEN --chain $CHAIN --limit 20
+# → address, address_label, bought/sold_volume_usd, bought/sold_token_volume, trade_volume_usd
+```
+
+Red flag: high fresh_wallets flow + low SM holders. Green flag: Fund/Smart Trader labels in top 20.
+
+Note: holders endpoint does not support native/wrapped tokens. Use a specific token contract address.

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

@@ -0,0 +1,32 @@
+---
+name: nansen-perp-screener
+description: "What is the state of the Hyperliquid perp market? Top contracts by volume/OI, trader leaderboard, and SM perp activity."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Perp Market Scan
+
+**Answers:** "What's the state of the Hyperliquid perp market right now?"
+
+```bash
+nansen research perp screener --sort volume:desc --limit 20
+# → token_symbol, volume, buy/sell_volume, buy_sell_pressure, open_interest, funding, mark_price
+
+nansen research perp leaderboard --days 7 --limit 20
+# → trader_address, trader_address_label, total_pnl, roi, account_value
+
+nansen research smart-money perp-trades --limit 20
+# → token_symbol, side, action (Open/Close), value_usd, price_usd, trader_address_label
+```

package/skills/nansen-perp-trader-profile/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: nansen-perp-trader-profile
+description: "Deep dive on a Hyperliquid perp trader. Identity, open positions, recent trades, and overall PnL."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Perp Trader
+
+**Answers:** "What is this perp trader doing? What are their positions and track record?"
+
+```bash
+ADDR=<address>
+
+nansen research profiler labels --address $ADDR --chain ethereum
+# → label, category (identity, SM labels)
+
+nansen research profiler perp-positions --address $ADDR
+# → asset_positions, margin_summary_account_value_usd, margin_summary_total_margin_used_usd
+
+nansen research profiler perp-trades --address $ADDR --days 7 --limit 20
+# → timestamp, token_symbol, side, action (Open/Close/Reduce), price, size, value_usd, closed_pnl, fee_usd
+
+nansen research perp leaderboard --days 7 --limit 50
+# → trader_address, total_pnl, roi, account_value (check if ADDR appears)
+```
+
+Cross-reference perp-trades with perp-positions to see if the trader is scaling in/out. Leaderboard shows relative standing.

package/skills/nansen-polymarket-deep-dive/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: nansen-polymarket-deep-dive
+description: "Deep dive on a Polymarket market — OHLCV, orderbook, top holders, positions, trades, and PnL leaderboard. Use when analysing a specific prediction market."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Prediction Market Deep Dive
+
+**Answers:** "What's happening in this specific market? Who holds it, who's trading it?"
+
+Use `market_id` from the screener (`nansen-prediction-market` skill).
+
+```bash
+MID=<market_id>
+
+nansen research pm ohlcv --market-id $MID --sort period_start:desc --limit 50
+# → period_start, open, high, low, close, volume
+
+nansen research pm orderbook --market-id $MID
+# → bids[], asks[] with price and size
+
+nansen research pm top-holders --market-id $MID --limit 20
+# → address, side, position_size, avg_entry_price, current_price, unrealized_pnl_usd
+
+nansen research pm position-detail --market-id $MID --limit 20
+# → address, side, size, avg_entry_price, current_price, pnl
+
+nansen research pm trades-by-market --market-id $MID --limit 20
+# → timestamp, buyer, seller, taker_action, side, size, price, usdc_value
+
+nansen research pm pnl-by-market --market-id $MID --limit 20
+# → address, side_held, net_buy_cost_usd, unrealized_value_usd, total_pnl_usd
+```
+
+Notes:
+- `--market-id` is a numeric ID from the screener, not a slug.
+- Works with any market ID regardless of status (active or closed/resolved).
+- All addresses are Polygon (EVM).

package/skills/nansen-polymarket-insider-scan/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: nansen-polymarket-insider-scan
+description: "Scan a resolved Polymarket market for wallets exhibiting suspicious trading patterns: fresh funding, single-market focus, extreme ROI, late entry at high prices."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# PM Suspicious Wallet Scanner
+
+**Answers:** "Are there wallets with suspicious trading patterns in this Polymarket market?"
+
+```bash
+# 1. Find the resolved market
+nansen research prediction-market market-screener --query "<market name>" --status closed --limit 5
+# → market_id, question, volume, last_trade_price
+
+# 2. Get top winners (positive PnL) — paginate if needed, keep per_page <= 10
+MID=<market_id>
+nansen research prediction-market pnl-by-market --market-id $MID --limit 10
+# → address (proxy), owner_address (wallet), side_held, net_buy_cost_usd, total_pnl_usd
+
+# 3. For each top winner, run these three calls (use proxy address for PM, owner for profiler):
+PROXY=<address_from_pnl>
+nansen research prediction-market trades-by-address --address $PROXY --limit 100
+# → market_id, market_question, side, price, size, usdc_value, taker_action, timestamp
+
+OWNER=<owner_address_from_pnl>
+nansen research profiler historical-balances --address $OWNER --chain polygon --days 365 --sort block_timestamp:asc --limit 100
+# → block_timestamp, value_usd, token_symbol — first non-zero value_usd = wallet funding date
+
+nansen research profiler labels --address $OWNER --chain polygon
+# → label, category
+```
+
+For each winner, compute ROI = total_pnl_usd / net_buy_cost_usd * 100 (skip ROI flags if net_buy_cost_usd <= 0), then score (0–13). Within each tier group, apply only the highest matching flag:
+
+| Flag | Pts | Trigger |
+|---|---|---|
+| NEW_WALLET | 3 | First funded within 7 days of now |
+| YOUNG_WALLET | 1 | First funded 8–28 days ago (skip if NEW_WALLET fires) |
+| SINGLE_MARKET | 3 | trades-by-address shows only 1 distinct market_id |
+| FEW_MARKETS | 1 | 2–3 distinct market_ids (skip if SINGLE_MARKET fires) |
+| EXTREME_ROI | 3 | ROI >= 500% |
+| HIGH_ROI | 2 | ROI 200–499% (skip if EXTREME_ROI fires) |
+| LATE_ENTRY | 2 | Any trade on this market at price >= 0.80 |
+| LARGE_POSITION | 2 | net_buy_cost_usd >= $10k |
+| KNOWN_ENTITY | -2 | Has Nansen labels |
+
+Flagged at score >= 3. High risk at >= 7. High-confidence suspicious pattern: NEW_WALLET + SINGLE_MARKET + EXTREME_ROI (score 9+).
+
+If owner_address is invalid (e.g. "0x"), use the proxy address for profiler calls too. If historical-balances returns no records with value_usd > 0, the wallet may predate the 365-day window — treat wallet age as unknown and skip NEW_WALLET / YOUNG_WALLET flags. Pause ~1.5s between wallets to avoid rate limits. Skip wallets that error and continue scanning.

package/skills/nansen-polymarket-trader-profile/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: nansen-polymarket-trader-profile
+description: "What is a Polymarket trader betting on? Trades by address, PnL breakdown, and market context. Use when analysing a specific Polymarket wallet."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Polymarket Wallet Activity
+
+**Answers:** "What is this Polymarket trader betting on? Are they profitable?"
+
+**Finding an active trader address:** Source from `trades-by-market` (guarantees trade history) rather than `top-holders` (position holders may have no recorded trades):
+
+```bash
+# Step 1: find active traders from a market
+nansen research pm trades-by-market --market-id <market_id> --limit 5
+# → seller/buyer addresses with confirmed trade history — use one as ADDR below
+```
+
+```bash
+ADDR=<polymarket_address>
+
+nansen research pm trades-by-address --address $ADDR --limit 20
+# → timestamp, market_question, event_title, taker_action, side, size, price, usdc_value
+
+nansen research pm pnl-by-address --address $ADDR --limit 20
+# → question, event_title, side_held, net_buy_cost_usd, unrealized_value_usd, total_pnl_usd, market_resolved
+```
+
+Note: addresses sourced from `top-holders` may return empty trade history — use `trades-by-market` to find addresses with confirmed activity.
+
+Look at PnL across resolved vs unresolved markets to gauge trader skill. Large positions in trending categories signal conviction.

package/skills/nansen-portfolio-tracker/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: nansen-portfolio-tracker
+description: "How has a wallet's portfolio changed over time? Historical balances, current snapshot, and per-token PnL."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Portfolio History
+
+**Answers:** "How has this wallet's portfolio evolved over the past month?"
+
+```bash
+ADDR=<address> CHAIN=ethereum
+
+nansen research profiler historical-balances --address $ADDR --chain $CHAIN --days 30 --limit 20
+# → block_timestamp, token_symbol, token_amount, value_usd, chain
+
+nansen research profiler balance --address $ADDR --chain $CHAIN
+# → token_symbol, token_name, token_amount, price_usd, value_usd
+
+nansen research profiler pnl --address $ADDR --chain $CHAIN --days 30 --limit 20
+# → token_symbol, pnl_usd_realised, roi_percent_realised, bought_usd, sold_usd, holding_usd, nof_buys, nof_sells
+```
+
+Compare historical-balances over time against current balance to see what was added/removed. PnL shows trade performance.

package/skills/nansen-prediction-markets/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: nansen-prediction-markets
+description: "Polymarket screeners — discover trending events, top markets by volume, and search for specific markets. Use when browsing what's happening on prediction markets."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+
+# Prediction Market Screeners
+
+All commands: `nansen research prediction-market <sub> [options]` (alias: `nansen research pm <sub>`)
+
+No `--chain` flag needed — Polymarket runs on Polygon.
+
+```bash
+# Top events (groups of related markets)
+nansen research pm event-screener --sort-by volume_24hr --limit 20
+# → event_title, market_count, total_volume, total_volume_24hr, total_liquidity, total_open_interest, tags
+
+# Top markets by 24h volume
+nansen research pm market-screener --sort-by volume_24hr --limit 20
+# → market_id, question, best_bid, best_ask, volume_24hr, liquidity, open_interest, unique_traders_24h
+
+# Search for specific markets
+nansen research pm market-screener --query "bitcoin" --limit 10
+
+# Find resolved/closed markets
+nansen research pm market-screener --status closed --limit 10
+
+# Browse categories
+nansen research pm categories --pretty
+# → category, active_markets, total_volume_24hr, total_open_interest
+```
+
+Sort options: `volume_24hr`, `volume`, `volume_1wk`, `volume_1mo`, `liquidity`, `open_interest`, `unique_traders_24h`, `age_hours`
+
+Screeners return active/open markets by default. Use `--status closed` for resolved markets.

package/skills/nansen-sm-cross-chain-flows/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: nansen-sm-cross-chain-flows
+description: "Is SM buying this token on one chain but selling on another? Detect capital rotation."
+metadata:
+  openclaw:
+    requires:
+      env:
+        - NANSEN_API_KEY
+      bins:
+        - nansen
+    primaryEnv: NANSEN_API_KEY
+    install:
+      - kind: node
+        package: nansen-cli
+        bins: [nansen]
+allowed-tools: Bash(nansen:*)
+---
+```bash
+TOKEN_SYMBOL=<symbol e.g. "AAVE"> CHAINS=(ethereum solana base bnb)
+for chain in "${CHAINS[@]}"; do
+  nansen research smart-money netflow --chain $chain --limit 200
+  # Filter by token_symbol; → net_flow_1h_usd, net_flow_24h_usd, net_flow_7d_usd, net_flow_30d_usd
+done
+```
+Absent from results = SM activity below threshold on that chain, not necessarily unsupported. Use --limit 200; --limit 100 silently drops mid-tier tokens.
+ETH+ & SOL− = rotating from SOL→ETH. One chain positive only = chain-specific play.
+24h/7d divergence across chains is the rotation signal, not 1h.