polymarket▌
2025emma/vibe-coding-cn · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Complete Polymarket integration covering prediction markets, REST API, trading, and real-time WebSocket data streaming.
- ›Supports six WebSocket topic categories: activity (trades, orders), comments (with reactions), RFQ events, crypto price feeds, authenticated user order/trade updates, and market-level price and orderbook data
- ›Includes TypeScript client library with topic-based subscriptions, dynamic filter support, and initial data dumps on connection
- ›Covers REST API for market disc
Polymarket Comprehensive Skill
Complete assistance with Polymarket development - covering the full platform (API, trading, market data) and the real-time data streaming client (WebSocket subscriptions for live market activity).
When to Use This Skill
This skill should be triggered when:
Platform & API:
- Working with Polymarket prediction markets
- Using Polymarket API for market data
- Implementing trading strategies
- Building applications with Polymarket services
- Learning Polymarket best practices
Real-Time Data Streaming:
- Connecting to Polymarket's WebSocket service
- Building prediction market monitoring tools
- Processing live trades, orders, and market updates
- Monitoring market comments and social reactions
- Tracking RFQ (Request for Quote) activity
- Integrating crypto price feeds
Quick Reference
Real-Time Data Client Setup
Installation:
npm install @polymarket/real-time-data-client
Basic Usage:
import { RealTimeDataClient } from "@polymarket/real-time-data-client";
const onMessage = (message: Message): void => {
console.log(message.topic, message.type, message.payload);
};
const onConnect = (client: RealTimeDataClient): void => {
client.subscribe({
subscriptions: [{
topic: "activity",
type: "trades"
}]
});
};
new RealTimeDataClient({ onMessage, onConnect }).connect();
Supported WebSocket Topics
1. Activity (activity)
trades- Completed tradesorders_matched- Order matching events- Filters:
{"event_slug":"string"}OR{"market_slug":"string"}
2. Comments (comments)
comment_created,comment_removedreaction_created,reaction_removed- Filters:
{"parentEntityID":number,"parentEntityType":"Event"}
3. RFQ (rfq)
- Request/Quote lifecycle events
- No filters, no auth required
4. Crypto Prices (crypto_prices, crypto_prices_chainlink)
update- Real-time price feeds- Filters:
{"symbol":"BTC"}(optional)
5. CLOB User (clob_user) ⚠️ Requires Auth
order- User's order updatestrade- User's trade executions
6. CLOB Market (clob_market)
price_change- Price movementsagg_orderbook- Aggregated order booklast_trade_price- Latest pricesmarket_created,market_resolved
Authentication for User Data
client.subscribe({
subscriptions: [{
topic: "clob_user",
type: "*",
clob_auth: {
key: "your-api-key",
secret: "your-api-secret",
passphrase: "your-passphrase"
}
}]
});
Common Use Cases
Monitor Specific Market:
client.subscribe({
subscriptions: [{
topic: "activity",
type: "trades",
filters: `{"market_slug":"btc-above-100k-2024"}`
}]
});
Track Multiple Markets:
client.subscribe({
subscriptions: [{
topic: "clob_market",
type: "price_change",
filters: `["100","101","102"]`
}]
});
Monitor Event Comments:
client.subscribe({
subscriptions: [{
topic: "comments",
type: "*",
filters: `{"parentEntityID":12345,"parentEntityType":"Event"}`
}]
});
Reference Files
This skill includes comprehensive documentation in references/:
Platform Documentation:
- api.md - Polymarket API documentation
- getting_started.md - Getting started guide
- guides.md - Development guides
- learn.md - Learning resources
- trading.md - Trading documentation
- other.md - Additional resources
Real-Time Client:
- README.md - WebSocket client API and examples
- llms.md - LLM integration guide
- llms-full.md - Complete LLM documentation
Use view to read specific reference files for detailed information.
Key Features
Platform Capabilities: ✅ Prediction market creation and resolution ✅ Trading API (REST & WebSocket) ✅ Market data queries ✅ User portfolio management ✅ Event and market discovery
Real-Time Streaming: ✅ WebSocket-based persistent connections ✅ Topic-based subscriptions ✅ Dynamic subscription management ✅ Filter support for targeted data ✅ User authentication for private data ✅ TypeScript with full type safety ✅ Initial data dumps on connection
Best Practices
WebSocket Connection Management
- Use
onConnectcallback for subscriptions - Implement reconnection logic for production
- Clean up with
disconnect()when done - Handle authentication errors gracefully
Subscription Strategy
- Use wildcards (
"*") sparingly - Apply filters to reduce data volume
- Unsubscribe from unused streams
- Process messages asynchronously
Performance
- Consider batching high-frequency data
- Use filters to minimize client processing
- Validate message payloads before use
Requirements
- Node.js: 14+ recommended
- TypeScript: Optional but recommended
- Package Manager: npm or yarn
Resources
Official Links
- Polymarket Platform: https://polymarket.com
- Real-Time Client Repo: https://github.com/Polymarket/real-time-data-client
- API Documentation: See references/api.md
Working with This Skill
For Beginners:
Start with getting_started.md for foundational concepts.
For API Integration:
Use api.md and trading.md for REST API details.
For Real-Time Data:
Use README.md for WebSocket client implementation.
For LLM Integration:
Use llms.md and llms-full.md for AI/ML use cases.
Notes
- Real-Time Client is TypeScript/JavaScript (not Python)
- Some WebSocket topics require authentication
- Use filters to manage message volume effectively
- All timestamps are Unix timestamps
- Market IDs are strings (e.g., "100", "101")
- Platform documentation covers both REST API and WebSocket usage
This comprehensive skill combines Polymarket platform expertise with real-time data streaming capabilities!
How to use polymarket on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add polymarket
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches polymarket from GitHub repository 2025emma/vibe-coding-cn and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate polymarket. Access the skill through slash commands (e.g., /polymarket) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★59 reviews- ★★★★★Kofi Ramirez· Dec 24, 2024
polymarket has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kofi Gonzalez· Dec 16, 2024
polymarket reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chaitanya Patil· Dec 8, 2024
I recommend polymarket for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Evelyn Jackson· Dec 8, 2024
polymarket fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ishan Jain· Dec 4, 2024
Useful defaults in polymarket — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ishan Liu· Dec 4, 2024
I recommend polymarket for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Nov 27, 2024
polymarket fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Maya Rahman· Nov 27, 2024
I recommend polymarket for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Maya Li· Nov 23, 2024
polymarket fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Nov 19, 2024
Useful defaults in polymarket — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 59