CRUD management for smart alerts. Alerts are internal-only (requires Nansen internal API key).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnansen-smart-alertsExecute the skills CLI command in your project's root directory to begin installation:
Fetches nansen-smart-alerts 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-smart-alerts. Access via /nansen-smart-alerts 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
CRUD management for smart alerts. Alerts are internal-only (requires Nansen internal API key).
nansen alerts list --table
nansen alerts create --name <name> --type <type> --chains <chains> --telegram <chatId>
nansen alerts update <id> [--name <name>] [--chains <chains>]
nansen alerts toggle <id> --enabled|--disabled
nansen alerts delete <id>
| Flag | Create | Update | Toggle | Delete |
|---|---|---|---|---|
<id> (positional) |
required | required | required | |
--name |
required | optional | ||
--type |
required | required with type-specific flags | ||
--chains |
recommended | optional | ||
--telegram |
chat ID | optional | ||
--slack |
webhook URL | optional | ||
--discord |
webhook URL | optional | ||
--webhook |
endpoint URL | optional | optional | |
--webhook-secret |
optional (webhook only) | optional | ||
--description |
optional | optional | ||
--enabled |
flag | flag | ||
--disabled |
flag | flag | flag | |
--data |
optional (JSON escape hatch) | optional |
sm-token-flows — Smart Money Token FlowsTrack aggregated SM inflow/outflow. At least one flow threshold should be specified.
Type-specific flags:
--inflow-1h-min/max, --inflow-1d-min/max, --inflow-7d-min/max (USD thresholds)--outflow-1h-min/max, --outflow-1d-min/max, --outflow-7d-min/max--netflow-1h-min/max, --netflow-1d-min/max, --netflow-7d-min/max--token <address:chain> (repeatable) — include specific tokens--exclude-token <address:chain> (repeatable)--token-sector <name> / --exclude-token-sector <name> (repeatable)--token-age-max <days>--market-cap-min/max <usd>, --fdv-min/max <usd>Example:
nansen alerts create \
--name 'SM ETH Inflow >5M' \
--type sm-token-flows \
--chains ethereum \
--telegram 5238612255 \
--inflow-1h-min 5000000 \
--token 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2:ethereum
common-token-transfer — Token Transfer EventsTrack real-time transfer events matching specified criteria.
Subject types: address, entity, label, custom-label
Format: --subject type:value (e.g. --subject label:"Centralized Exchange")
Type-specific flags:
--events <buy,sell,swap,send,receive> (comma-separated)--usd-min/max <usd>, --token-amount-min/max <n>--subject <type:value> (repeatable) — addresses/entities/labels to track--counterparty <type:value> (repeatable) — requires --subject--token <address:chain> / --exclude-token <address:chain> (repeatable)--token-sector <name> / --exclude-token-sector <name> (repeatable)--token-age-min/max <days>, --market-cap-min/max <usd>--exclude-from <type:value> / --exclude-to <type:value> (repeatable)Event direction notes:
buy for counterparties = sell for subjectssend for counterparties = receive for subjects--subject with receive, not --counterparty with sendExample:
nansen alerts create \
--name 'Large USDC Transfers' \
--type common-token-transfer \
--chains ethereum \
--telegram 123456789 \
--events send,receive \
--usd-min 1000000 \
--token 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48:ethereum
smart-contract-call — Smart Contract InteractionsTrack contract calls matching specified criteria.
Type-specific flags:
--usd-min/max <usd>--signature-hash <hash> (repeatable, e.g. 0x095ea7b3 for approve)--caller <type:value> / --exclude-caller <type:value> (repeatable)--contract <type:value> / --exclude-contract <type:value> (repeatable)Example:
nansen alerts create \
--name 'Uniswap V3 Large Swaps' \
--type smart-contract-call \
--chains ethereum \
--telegram 123456789 \
--usd-min 1000000 \
--contract entity:"Uniswap V3"
hyperevm, BSC = bnb.--telegram 123 --slack https://... --webhook https://...--webhook <url> sends a POST request with the alert payload to any HTTP/HTTPS endpoint. Useful for server deployments, Zapier, n8n, or custom integrations. The endpoint must be publicly reachable and return a 2xx response.--data '<json>' merges raw JSON on top of named flags (escape hatch for fields without named flags).$ or special characters: --name 'SM >$1M'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
Useful defaults in nansen-smart-alerts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend nansen-smart-alerts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: nansen-smart-alerts is the kind of skill you can hand to a new teammate without a long onboarding doc.
nansen-smart-alerts has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for nansen-smart-alerts matched our evaluation — installs cleanly and behaves as described in the markdown.
nansen-smart-alerts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: nansen-smart-alerts is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in nansen-smart-alerts — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for nansen-smart-alerts matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: nansen-smart-alerts is focused, and the summary matches what you get after install.
showing 1-10 of 49