nansen-wallet-profiler

All commands: nansen research profiler <sub> [options]

nansen-ai/nansen-cliUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

114

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/nansen-ai/nansen-cli --skill nansen-wallet-profiler

0

installs

0

this week

114

stars

Installation Guide

How to use nansen-wallet-profiler on Cursor

AI-first code editor with Composer

1

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-wallet-profiler
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/nansen-ai/nansen-cli --skill nansen-wallet-profiler

Fetches nansen-wallet-profiler from nansen-ai/nansen-cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/nansen-wallet-profiler

Restart Cursor to activate nansen-wallet-profiler. Access via /nansen-wallet-profiler 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

Wallet Profiler

All commands: nansen research profiler <sub> [options]

--address and --chain required for most commands.

Balance & Identity

nansen research profiler balance --address <addr> --chain ethereum
nansen research profiler labels --address <addr> --chain ethereum
nansen research profiler search --query "Vitalik"

PnL

nansen research profiler pnl --address <addr> --chain ethereum --days 30
nansen research profiler pnl-summary --address <addr> --chain ethereum

Transactions & History

nansen research profiler transactions --address <addr> --chain ethereum --limit 20
nansen research profiler historical-balances --address <addr> --chain solana --days 30

Relationships

nansen research profiler related-wallets --address <addr> --chain ethereum
nansen research profiler counterparties --address <addr> --chain ethereum --days 30

Perps (no --chain)

nansen research profiler perp-positions --address <addr>
nansen research profiler perp-trades --address <addr> --days 7

Batch, Trace & Compare

# Batch — profile multiple wallets at once
nansen research profiler batch \
  --addresses "0xabc,0xdef" --chain ethereum \
  --include labels,balance,pnl

# Trace — BFS multi-hop counterparty trace (makes N*width API calls)
nansen research profiler trace --address <addr> --chain ethereum --depth 2 --width 5

# Compare — shared counterparties and tokens between two wallets
nansen research profiler compare --addresses "0xabc,0xdef" --chain ethereum

Flags

Flag Purpose
--address Wallet address (required)
--chain Required except for perps and search
--days Lookback period (default 30)
--limit Number of results
--include Batch fields: labels,balance,pnl
--depth Trace depth 1-5 (default 2)
--width Trace width — keep low to save credits
--fields Select specific fields
--table Human-readable table output
--format csv CSV export

Notes

  • pnl-summary has no pagination support (returns aggregate stats, not a list).
  • perp-positions has no pagination support.
  • labels has no pagination support — the API ignores per_page and always returns all labels for the address. --limit is not available for this sub-command.
  • transactions caps at per_page=100 (API limit).
  • trace makes many API calls — use --width conservatively.
  • batch accepts --file <path> with one address per line as alternative to --addresses.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

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

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.642 reviews
  • C
    Chinedu MenonDec 28, 2024

    We added nansen-wallet-profiler from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • D
    Diego RaoDec 20, 2024

    nansen-wallet-profiler reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • M
    Mei DialloNov 23, 2024

    Keeps context tight: nansen-wallet-profiler is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • C
    Chinedu IyerNov 19, 2024

    Solid pick for teams standardizing on skills: nansen-wallet-profiler is focused, and the summary matches what you get after install.

  • C
    Charlotte RobinsonNov 11, 2024

    I recommend nansen-wallet-profiler for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Z
    Zara ZhangOct 14, 2024

    nansen-wallet-profiler is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • A
    Alexander RobinsonOct 10, 2024

    nansen-wallet-profiler has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • C
    Charlotte ChoiOct 2, 2024

    Useful defaults in nansen-wallet-profiler — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • C
    Chinedu AndersonSep 25, 2024

    Solid pick for teams standardizing on skills: nansen-wallet-profiler is focused, and the summary matches what you get after install.

  • S
    Sakshi PatilSep 21, 2024

    Registry listing for nansen-wallet-profiler matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 42

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.