Answers: "What's happening in this specific market? Who holds it, who's trading it?"
Works with
Answers: "What's happening in this specific market? Who holds it, who's trading it?"
Use market_id from the screener (nansen-prediction-market skill).
MID=<market_id>
nansen research pm ohlcv --market-id $MID --sort period_start:desc --limit 50
# → period_start, open, high, low, close, volume
nansen research pm orderbook --market-id $MID
# → bids[], asks[] with price and size
nansen research pm top-holders --market-id $MID --limit 20
# → address, side, position_size, avg_entry_price, current_price, unrealized_pnl_usd
nansen research pm position-detail --market-id $MID --limit 20
# → address, side, size, avg_entry_price, current_price, pnl
nansen research pm trades-by-market --market-id $MID --limit 20
# → timestamp, buyer, seller, taker_action, side, size, price, usdc_value
nansen research pm pnl-by-market --market-id $MID --limit 20
# → address, side_held, net_buy_cost_usd, unrealized_value_usd, total_pnl_usd
Notes:
--market-id is a numeric ID from the screener, not a slug.AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnansen-polymarket-deep-diveExecute the skills CLI command in your project's root directory to begin installation:
Fetches nansen-polymarket-deep-dive 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-polymarket-deep-dive. Access via /nansen-polymarket-deep-dive 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
114
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
114
stars
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
Useful defaults in nansen-polymarket-deep-dive — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nansen-polymarket-deep-dive fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for nansen-polymarket-deep-dive matched our evaluation — installs cleanly and behaves as described in the markdown.
We added nansen-polymarket-deep-dive from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
nansen-polymarket-deep-dive reduced setup friction for our internal harness; good balance of opinion and flexibility.
nansen-polymarket-deep-dive fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added nansen-polymarket-deep-dive from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
nansen-polymarket-deep-dive reduced setup friction for our internal harness; good balance of opinion and flexibility.
nansen-polymarket-deep-dive reduced setup friction for our internal harness; good balance of opinion and flexibility.
nansen-polymarket-deep-dive is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 39