npm-downloads-to-leads

​

Install

npx "@opendirectory.dev/skills" install npm-downloads-to-leads --target claude

npx skills add Varnan-Tech/opendirectory --skill npm-downloads-to-leads

/plugin marketplace add Varnan-Tech/opendirectory
/plugin install opendirectory-gtm-skills@opendirectory-marketplace

​

What It Does

• Fetches 12 weeks of daily download data per package from the npm Downloads API
• Aggregates to weekly buckets and computes a velocity score: recent growth x acceleration x sweet-spot multiplier
• Classifies each package as BREAKOUT, WATCHING, steady, established, or too early
• Fetches maintainer profiles from the npm registry and GitHub API
• Extracts GitHub followers, Twitter handle, bio, and company from each maintainer’s GitHub profile
• Generates a lead brief per breakout package: growth story, contact signals, why to reach out now, and a suggested first message
• Saves output to docs/npm-leads/[date].md

​

Requirements

​

Setup

cp .env.example .env
# Add GITHUB_TOKEN (optional, recommended for larger package lists)

​

How to Use

"Find leads from these npm packages: esbuild, vite, @hono/hono, zod"
"Track download trends for competitor packages: turbo, nx, lerna"
"Who maintains these breakout npm packages? bun, oxc-parser, biome"
"Find evangelists before they are famous: @effect-ts/core, fp-ts, zod"
"Analyze npm momentum for my space: my-package, competitor-a, competitor-b"
"Map npm maintainers to Twitter for these packages: ..."

​

Why Velocity Score, Not Raw Downloads

• growth_ratio: recent 4-week average divided by prior 4-week average
• acceleration: last 2 weeks vs mid 2 weeks (is growth speeding up?)
• sweet_spot_multiplier: 1.0 for 500 to 500K weekly downloads, lower for noise floor or established giants

​

The Lead Brief

• Growth story: exact download numbers, 8-week comparison, weekly trend
• Maintainer profile: GitHub handle, Twitter, bio, company, follower count
• Why reach out now: specific to this package’s growth inflection point
• Suggested first message: names the package, its growth, and connects to your product context

​

Cost Per Run

• npm Downloads API: free, no auth, no rate limit concerns
• npm Registry API: free, no auth
• GitHub API: free (60 req/hr unauthenticated, 5000/hr with token)
• AI analysis: uses the model already running the skill; no additional cost
• Total: free

​

Standalone Script

# Basic usage
python3 scripts/fetch.py esbuild zod @hono/hono

# With product context
python3 scripts/fetch.py esbuild zod --context "We build a TypeScript DX platform"

# From a file (one package per line)
python3 scripts/fetch.py --file packages.txt --output results.json

# Print to stdout
python3 scripts/fetch.py esbuild zod --stdout | jq '.summary'

GITHUB_TOKEN=your_token python3 scripts/fetch.py esbuild zod @hono/hono

• velocity_score, growth_pct, recent_4_avg, prior_4_avg, tier
• weeks: array of 12 weekly download counts, oldest to newest
• profile.description, profile.keywords, profile.npm_maintainers
• profile.github_users: array with username, twitter_username, followers, bio, company

​

Project Structure

npm-downloads-to-leads/
├── SKILL.md
├── README.md
├── .env.example
├── scripts/
│   └── fetch.py           standalone data fetcher (Steps 3 to 5, no Claude needed)
├── evals/
│   └── evals.json
└── references/
    ├── velocity-scoring.md
    └── outreach-timing.md

​

License