All commands: nansen research token <sub> [options]
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnansen-token-researchExecute the skills CLI command in your project's root directory to begin installation:
Fetches nansen-token-research from nansen-ai/nansen-cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nansen-token-research. Access via /nansen-token-research in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
115
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
115
stars
All commands: nansen research token <sub> [options]
--chain required for spot endpoints. Use --token <address> for token-specific endpoints.
nansen research token info --token <addr> --chain solana
nansen research token ohlcv --token <addr> --chain solana --timeframe 1h
Timeframes: 1m, 5m, 15m, 30m, 1h, 2h, 4h, 1d, 1w, 1M
nansen research token holders --token <addr> --chain solana
nansen research token holders --token <addr> --chain solana --smart-money
nansen research token flows --token <addr> --chain solana --days 7
nansen research token flow-intelligence --token <addr> --chain solana
nansen research token who-bought-sold --token <addr> --chain solana
flow-intelligence breaks down by label: whales, smart traders, exchanges, fresh wallets, public figures.
nansen research token dex-trades --token <addr> --chain solana --limit 20
nansen research token pnl --token <addr> --chain solana --sort total_pnl_usd:desc
nansen research token perp-trades --symbol ETH --days 7
nansen research token perp-positions --symbol BTC
nansen research token perp-pnl-leaderboard --symbol SOL
| Flag | Purpose |
|---|---|
--chain |
Required for spot endpoints (ethereum, solana, base, etc.) |
--token |
Token address (alias: --token-address) |
--symbol |
Token symbol for perp endpoints (e.g. BTC) |
--timeframe |
OHLCV interval |
--smart-money |
Filter to SM wallets only (holders) |
--days |
Lookback period (default 30) |
--sort |
Sort field:direction (e.g. total_pnl_usd:desc) |
--fields |
Select specific fields |
--table |
Human-readable table output |
--format csv |
CSV export |
--symbol (e.g. BTC), not --token.holders --smart-money returns UNSUPPORTED_FILTER for tokens without SM tracking.flow-intelligence may return all-zero flows for illiquid tokens.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
nansen-token-research has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: nansen-token-research is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for nansen-token-research matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend nansen-token-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: nansen-token-research is focused, and the summary matches what you get after install.
nansen-token-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
nansen-token-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
nansen-token-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
nansen-token-research reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added nansen-token-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 36