Skip to content

feat: add nansen-dca-tracker — smart money DCA tracking on Solana#31

Open
tonyagents wants to merge 2 commits intomoonpay:mainfrom
tonyagents:add-nansen-dca-tracker
Open

feat: add nansen-dca-tracker — smart money DCA tracking on Solana#31
tonyagents wants to merge 2 commits intomoonpay:mainfrom
tonyagents:add-nansen-dca-tracker

Conversation

@tonyagents
Copy link
Contributor

Skill name

nansen-dca-tracker

Description

Answers "what tokens are whales DCA-ing into on Solana?" — queries smart money Jupiter DCA strategies via the Nansen CLI, then pulls token fundamentals and flow intelligence for each target.

Primary chain

Solana

Primary token

SOL / SPL tokens

Checklist

  • Frontmatter (name, description) present
  • Registered in .claude-plugin/marketplace.json under nansen-skills plugin
  • Naming convention: nansen-{name}/
  • Uses nansen-cli (npm: nansen-cli) — real package
  • No Python/TypeScript code — pure CLI commands
  • NANSEN_API_KEY env var documented

MoonPay Integration

Fund a Solana wallet to act on DCA signals discovered via Nansen:

mp buy --token sol_solana --amount 0.5 --wallet <solana-address> --email <email>

Example Usage

export NANSEN_API_KEY=your_key

# Find top smart money DCA targets
nansen research smart-money dcas --limit 20

# Check fundamentals + flow for the top target
nansen research token info --token <output_token_address> --chain solana
nansen research token flow-intelligence --token <output_token_address> --chain solana

Copy link
Contributor

@kevarifin14 kevarifin14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: nansen-dca-tracker

Grade: B — Close, but not mergeable. The CLI commands are all real and verified, and the concept is solid. A few structural items need fixing before merge.

Verification Results

All CLI commands verified against nansen-cli@1.21.0 (npm package is real, published by asvanevik <alex@nansen.ai>):

Command Status
nansen research smart-money dcas --limit 20 Verified — subcommand exists
nansen research token info --token ... --chain solana Verified
nansen research token flow-intelligence --token ... --chain solana Verified
nansen research token jup-dca --token ... Verified
npm i -g nansen-cli → installs nansen binary Verified

Issues to Fix

1. Missing Prerequisites section (required by rubric)

The skill has no Prerequisites section. The metadata.openclaw block captures this for machines, but agents reading the SKILL.md need explicit human-readable setup instructions. Add a section like:

## Prerequisites

- Nansen CLI installed: `npm i -g nansen-cli`
- Nansen API key set: `export NANSEN_API_KEY=<your-key>` (get one at https://app.nansen.ai)

2. Missing structured Workflow section (required by rubric)

The current body is a command reference block. The template and rubric require a numbered step-by-step workflow an agent can follow without ambiguity. Restructure into:

## Workflow

1. Fetch the latest smart money DCA strategies on Solana:
   ```bash
   nansen research smart-money dcas --limit 20
  1. Identify the top DCA targets by deposit_value_usd ...
  2. For each target, pull token fundamentals: ...
  3. Check flow intelligence to confirm accumulation: ...

**3. Missing `tags` in frontmatter**

The template specifies `tags` as a frontmatter field. Add something like:
```yaml
tags: [nansen, smart-money, dca, solana, jupiter]

Nice to Have

  • Cross-references: Consider linking to moonpay-buy-crypto for users who want to act on DCA signals (e.g., "Fund a Solana wallet to buy tokens smart money is accumulating").
  • Error Handling: A brief table for common errors (invalid API key, rate limits) would match the template.

What's Good

  • All commands are real and verified — no hallucinations
  • Clean diff, no unrelated changes
  • marketplace.json placement is correct (separate nansen-skills plugin block)
  • Naming convention followed
  • The metadata.openclaw block with install instructions is a nice addition
  • Concise, focused skill with a clear use case

Fix the Prerequisites and Workflow sections, add tags, and this is ready to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants