nansen-token
All commands: nansen research token <sub> [options]
Works with
0
total installs
0
this week
115
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
115
stars
Installation Guide
How to use nansen-token on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
nansen-token
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches nansen-token from nansen-ai/nansen-cli and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nansen-token. Access via /nansen-token in your agent's command palette.
Security Notice
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.
Documentation
Token Deep Dive
All commands: nansen research token <sub> [options]
--chain required for spot endpoints. Use --token <address> for token-specific endpoints.
Info & Price
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
Holders
nansen research token holders --token <addr> --chain solana
nansen research token holders --token <addr> --chain solana --smart-money
Flows
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.
DEX Trades
nansen research token dex-trades --token <addr> --chain solana --limit 20
PnL
nansen research token pnl --token <addr> --chain solana --sort total_pnl_usd:desc
Perps (no --chain)
nansen research token perp-trades --symbol ETH --days 7
nansen research token perp-positions --symbol BTC
nansen research token perp-pnl-leaderboard --symbol SOL
Flags
| 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 |
Notes
- Perp endpoints use
--symbol(e.g. BTC), not--token. holders --smart-moneyreturns UNSUPPORTED_FILTER for tokens without SM tracking.flow-intelligencemay return all-zero flows for illiquid tokens.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
391mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- YYuki Jain★★★★★Dec 28, 2024
nansen-token reduced setup friction for our internal harness; good balance of opinion and flexibility.
- DDhruvi Jain★★★★★Dec 20, 2024
nansen-token reduced setup friction for our internal harness; good balance of opinion and flexibility.
- YYuki Zhang★★★★★Dec 20, 2024
We added nansen-token from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- YYusuf Mehta★★★★★Dec 12, 2024
nansen-token is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- BBenjamin Garcia★★★★★Nov 19, 2024
I recommend nansen-token for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- OOshnikdeep★★★★★Nov 11, 2024
I recommend nansen-token for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- NNoor Mensah★★★★★Nov 3, 2024
Solid pick for teams standardizing on skills: nansen-token is focused, and the summary matches what you get after install.
- NNoor Gill★★★★★Oct 22, 2024
nansen-token has been reliable in day-to-day use. Documentation quality is above average for community skills.
- IIsabella Rao★★★★★Oct 10, 2024
Useful defaults in nansen-token — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- GGanesh Mohane★★★★★Oct 2, 2024
Useful defaults in nansen-token — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 26
Discussion
Comments — not star reviews- No comments yet — start the thread.