The CLI supports two wallet providers:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnansen-wallet-managerExecute the skills CLI command in your project's root directory to begin installation:
Fetches nansen-wallet-manager 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-wallet-manager. Access via /nansen-wallet-manager 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
# Save API key (non-interactive)
nansen login --api-key <key>
# Or via env var:
NANSEN_API_KEY=<key> nansen login
# Verify
nansen research profiler labels --address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chain ethereum
The CLI supports two wallet providers:
| Local (default) | Privy (server-side) | |
|---|---|---|
| Key storage | Encrypted on disk | Server-side via Privy API |
| Password required | Yes (min 12 chars) | No |
| Export private keys | Yes (wallet export) |
No — keys are managed by Privy |
| Best for | Human users, manual trading | Agents, automated workflows |
| Flag | --provider local (default) |
--provider privy |
| Required env vars | NANSEN_WALLET_PASSWORD |
PRIVY_APP_ID + PRIVY_APP_SECRET |
Privy wallets are server-side wallets managed by the Privy API. No password is needed — keys never touch the local machine.
The following environment variables must be set:
| Var | Purpose |
|---|---|
PRIVY_APP_ID |
Privy application ID |
PRIVY_APP_SECRET |
Privy application secret |
nansen wallet create --provider privy
# Or with a custom name:
nansen wallet create --name agent-wallet --provider privy
wallet export only works for local walletslist, show, send, delete, default) work identically for both providersThis section covers local wallet creation. For Privy server-side wallets, see the Privy Wallet Creation section above — no password is needed.
Wallet creation requires a password from the human user. The agent must NOT generate or store the password itself.
Step 1 (Agent → Human): Ask the user to provide a wallet password (minimum 12 characters).
Step 2 (Agent executes): Run the create command with the password the user gave you.
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet create
After creation, the CLI automatically saves the password:
All future wallet operations retrieve the password automatically — no env var or human input needed.
If the .credentials file fallback is used, the CLI prints a warning on every operation. To migrate to secure storage later, run nansen wallet secure.
NANSEN_WALLET_PASSWORD env var (if set)~/.nansen/wallets/.credentials file (insecure fallback, with warning)--human flag — that enables interactive prompts which agents cannot handlePASSWORD_REQUIRED error, ask the user to provide their password againnansen wallet create --provider privy
# Or with a custom name:
nansen wallet create --name trading --provider privy
Requires PRIVY_APP_ID + PRIVY_APP_SECRET env vars. No password needed.
# Ask the user for a password first, then:
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet create
# Or with a custom name:
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet create --name trading
nansen wallet list
nansen wallet show <name>
nansen wallet default <name>
# Send native token (SOL, ETH) — password auto-resolved from keychain
nansen wallet send --to <addr> --amount 1.5 --chain solana
# Send entire balance
nansen wallet send --to <addr> --chain evm --max
# Dry run (preview, no broadcast)
nansen wallet send --to <addr> --amount 1.0 --chain evm --dry-run
# Password auto-resolved from keychain
nansen wallet export <name>
nansen wallet delete <name>
# Remove saved password from all stores (keychain + .credentials file)
nansen wallet forget-password
nansen wallet secure
For detailed migration steps (from ~/.nansen/.env, .credentials, or env-var-only setups), see the nansen-wallet-migration skill.
| Flag | Purpose |
|---|---|
--to |
Recipient address |
--amount |
Amount to send |
--chain |
evm or solana |
--max |
Send entire balance |
--dry-run |
Preview without broadcasting |
--provider |
Wallet provider: local (default, encrypted on disk) or privy (server-side via Privy API) |
--human |
Enable interactive prompts (human terminal use only — agents must NOT use this) |
--unsafe-no-password |
Skip encryption (keys stored in plaintext — NOT recommended) |
| Var | Purpose |
|---|---|
NANSEN_WALLET_PASSWORD |
Wallet encryption password — only needed for initial wallet create. After that, the OS keychain handles it. |
NANSEN_API_KEY |
API key (also set via nansen login --api-key <key>) |
PRIVY_APP_ID |
Privy application ID (required for --provider privy) |
PRIVY_APP_SECRET |
Privy application secret (required for --provider privy) |
NANSEN_WALLET_PROVIDER |
Default provider for wallet create — local or privy |
NANSEN_EVM_RPC |
Custom EVM RPC endpoint |
NANSEN_SOLANA_RPC |
Custom Solana RPC endpoint |
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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
nansen-wallet-manager is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
nansen-wallet-manager has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: nansen-wallet-manager is the kind of skill you can hand to a new teammate without a long onboarding doc.
nansen-wallet-manager is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: nansen-wallet-manager is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in nansen-wallet-manager — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nansen-wallet-manager is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in nansen-wallet-manager — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nansen-wallet-manager has been reliable in day-to-day use. Documentation quality is above average for community skills.
nansen-wallet-manager fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 30