Nansen Polymarket Deep Dive

Deep dive on a Polymarket market — OHLCV, orderbook, top holders, positions, trades, and PnL leaderboard. Use when analysing a specific prediction market.

Security Scan

The skill's requirements and runtime instructions match its stated purpose (running the nansen CLI against a Polymarket market) and request only the single appropriate API key; the main residual risk is installing an unpinned npm CLI package from the public registry.

Purpose & Capability

Name/description ask for a Polymarket deep dive and the skill only requires the 'nansen' CLI and a NANSEN_API_KEY, which are exactly what you would expect to query Nansen's research commands.

Instruction Scope

SKILL.md contains explicit nansen CLI commands scoped to a market_id and does not instruct reading unrelated files, other env vars, or exfiltrating data to unexpected endpoints. It references using a market_id from another skill (reasonable).

Install Mechanism

Install uses a Node package (nansen-cli) that will create a 'nansen' binary. Installing from the npm registry is a normal choice for a CLI but carries standard supply-chain/code-execution risk: the package is unpinned (no version specified) and the skill metadata lacks a homepage/source to verify the publisher.

Credentials

Only NANSEN_API_KEY is required and declared as the primary credential, which is proportionate for a CLI that queries Nansen's API. No unrelated credentials or config paths are requested.

Persistence & Privilege

always:false and no requests to modify other skills or system-wide settings. The skill does not request persistent elevated privileges.

Assessment

This skill appears to do what it claims: run the nansen CLI against a Polymarket market and requires only your NANSEN_API_KEY. Before installing, consider: (1) the npm package 'nansen-cli' will be fetched from the public registry and no version is pinned — audit or pin the package version if you need stability/trust; (2) only provide an API key with the minimum privileges necessary and be prepared to rotate it if you stop using the skill; (3) if you are cautious, inspect the nansen-cli package source (or vendor a known-good release) before installing; and (4) run installation in an isolated environment if you want to limit risk from supply-chain code execution.

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).

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).