Nansen Token Transfer Analysis

Where is this token moving and why? Large transfers, flow trends over time, and breakdown by wallet label.

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (calling the Nansen CLI with a Nansen API key); nothing requested appears disproportionate or unrelated.

Purpose & Capability

Name/description ask for token transfer/flow analysis and the skill requires the 'nansen' CLI and a NANSEN_API_KEY — both are appropriate and expected for interacting with Nansen data.

Instruction Scope

SKILL.md contains concrete CLI commands limited to querying token transfers/flows. It does not instruct reading unrelated files, scanning system state, or exfiltrating data outside Nansen. It uses only declared parameters (TOKEN, CHAIN) and the expected service.

Install Mechanism

Install is a node package (nansen-cli) which will create a 'nansen' binary. npm installs are common for CLIs but carry moderate supply-chain risk compared to a vetted distro package; verify the package origin (official Nansen package) before installing.

Credentials

Only a single credential (NANSEN_API_KEY) is required and it's the declared primary credential — proportional to the skill's purpose. No unrelated credentials or filesystem config paths are requested.

Persistence & Privilege

Skill is user-invocable, not forced-always; it does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed (platform default) but not elevated here.

Assessment

This skill is coherent: it runs the official-looking Nansen CLI and needs only your NANSEN_API_KEY. Before installing, confirm the 'nansen-cli' npm package is the legitimate package from Nansen (check the package page, publisher, and repository). Treat your NANSEN_API_KEY like a secret: provide a key with the minimum scope needed, avoid reusing high-privilege keys, and consider running the install in an isolated environment if you have supply-chain concerns. If you need stronger assurance, ask the publisher for a verified homepage/repository or use an audited binary distribution (e.g., an official release on the vendor's site or GitHub releases).

Token Forensics

Answers: "Where is this token moving? Who is sending it and where?"

TOKEN=<address> CHAIN=ethereum
# Examples: UNI on ethereum (0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984)
#           BONK on solana (DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263)
# Note: token flows does NOT support stablecoins (USDC, USDT, etc.) — use non-stablecoin tokens

nansen research token transfers --token $TOKEN --chain $CHAIN --days 7 --limit 20
# → from_address_label, to_address_label, transfer_amount, transfer_value_usd

nansen research token flows --token $TOKEN --chain $CHAIN --days 7 --limit 20
# → date, price_usd, holders_count, total_inflows_count, total_outflows_count
# ⚠ Returns HTTP 422 for stablecoins — skip this command if TOKEN is a stablecoin

nansen research token flow-intelligence --token $TOKEN --chain $CHAIN
# → net_flow_usd per label: smart_trader, whale, exchange, fresh_wallets, public_figure

Rising exchange_net_flow + large transfers to exchange addresses = potential sell pressure. Fresh wallet inflows may signal new interest or wash trading.