Nansen Holder Analysis

Is this token held by quality wallets or retail noise? SM holder ratio, flow breakdown by label, and recent buyer quality.

Security Scan

The skill's requirements and instructions match its stated purpose (running the Nansen CLI with a Nansen API key); nothing requested appears unrelated or excessive.

Purpose & Capability

Name/description describe Nansen token holder analysis and the skill requires the nansen CLI and NANSEN_API_KEY — these are coherent and expected.

Instruction Scope

SKILL.md only shows concrete nansen CLI commands (holders, flow-intelligence, who-bought-sold) operating on a TOKEN and CHAIN; it does not instruct the agent to read other files, unrelated env vars, or transmit data to unexpected endpoints.

Install Mechanism

Install uses the npm package 'nansen-cli' to provide the 'nansen' binary. This is a standard delivery for a CLI; moderate trust is appropriate but it's an expected mechanism for this purpose.

Credentials

Only NANSEN_API_KEY is required and declared as the primary credential. That is proportional to a CLI that talks to Nansen's API; no unrelated credentials or config paths are requested.

Persistence & Privilege

The skill does not request persistent/always-on presence and uses normal autonomous-invocation defaults. It does not modify other skills or system-wide configs.

Assessment

This skill appears to be what it claims: it runs the Nansen CLI and needs your NANSEN_API_KEY. Before installing, confirm you trust the 'nansen-cli' npm package (review its source and version), supply the API key with least privilege, and install in a controlled environment (or sandbox) if you are worried about npm postinstall scripts. Be aware that using the skill will send token addresses and queries to Nansen's service (normal for this tool), so do not provide sensitive secrets beyond the NANSEN_API_KEY and avoid sharing private keys.

Holder Quality

Answers: "Is this token held by quality wallets or retail noise?"

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.