Before writing queries, consult references/api-reference.md for sport codes, command parameters, and price format.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpolymarketExecute the skills CLI command in your project's root directory to begin installation:
Fetches polymarket from machina-sports/sports-skills 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 polymarket. Access via /polymarket 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
65
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
65
stars
Before writing queries, consult references/api-reference.md for sport codes, command parameters, and price format.
Prefer the CLI — it avoids Python import path issues:
sports-skills polymarket search_markets --sport=nba --sports_market_types=moneyline
sports-skills polymarket get_todays_events --sport=epl
sports-skills polymarket search_markets --sport=epl --query="Leeds" --sports_market_types=moneyline
sports-skills polymarket get_sports_config
Python SDK (alternative):
from sports_skills import polymarket
polymarket.search_markets(sport='nba', sports_market_types='moneyline')
polymarket.get_todays_events(sport='epl')
polymarket.search_markets(sport='epl', query='Leeds')
polymarket.get_sports_config()
CRITICAL: Before calling any market endpoint, verify:
sport parameter is always passed to search_markets and get_todays_events for single-game markets.token_id (CLOB), not market_id (Gamma). Call get_market_details first to get clobTokenIds.Without the sport parameter:
WRONG: search_markets(query="Leeds") → 0 results
RIGHT: search_markets(sport='epl', query='Leeds') → returns all Leeds markets
Core commands (no dependencies, no API keys): All read commands work out of the box.
Trading commands require py_clob_client:
pip install sports-skills[polymarket]
Additionally requires a configured wallet:
export POLYMARKET_PRIVATE_KEY=0x...
search_markets --sport=nba (or epl, nfl, bun, etc.)get_market_prices --token_id=<clob_token_id>.get_todays_events --sport=epl — returns events sorted by start date.clob_token_id from outcomes, then get_market_prices.search_markets --sport=nba --query="Lakers" --sports_market_types=moneylineget_market_prices --token_id=<id> for live CLOB prices.search_markets --sport=nba.clob_token_id from the outcomes.get_price_history --token_id=<id> --interval=1w| Command | Description |
|---|---|
get_sports_config |
Available sport codes |
get_todays_events |
Today's events for a league |
search_markets |
Find markets by sport, keyword, and type |
get_sports_markets |
Browse all sports markets |
get_sports_events |
Browse sports events |
get_series |
List series (leagues) |
get_market_details |
Single market details |
get_event_details |
Single event details |
get_market_prices |
Current CLOB prices |
get_order_book |
Full order book |
get_price_history |
Historical prices |
get_last_trade_price |
Most recent trade |
See references/api-reference.md for full parameter lists and return shapes.
Example 1: Tonight's NBA favorites User says: "Who's favored in tonight's NBA games?" Actions:
search_markets(sport='nba', sports_market_types='moneyline')
Result: Each matchup with implied win probabilities (price = probability)Example 2: Team-specific odds User says: "Show me Leeds vs Man City odds" Actions:
search_markets(sport='epl', query='Leeds', sports_market_types='moneyline')
Result: Leeds moneyline market with outcome pricesExample 3: Today's EPL events User says: "What EPL matches are on today?" Actions:
get_todays_events(sport='epl')
Result: Today's EPL events with nested markets (moneyline, spreads, totals, props)Example 4: League winner futures User says: "Who will win the Premier League?" Actions:
search_markets(query='Premier League') — returns futuresExample 5: Bundesliga odds User says: "Show me Bundesliga odds for Dortmund vs Bayern" Actions:
search_markets(sport='bun', query='Dortmund', sports_market_types='moneyline')
Result: Dortmund/Bayern moneyline market with outcome pricescli_search_marketssearch_markets instead.cli_sports_listget_sports_config instead.get_market_oddsget_oddsget_current_oddsget_market_prices(token_id=...).get_implied_probabilityget_marketsget_sports_markets (browse) or search_markets (search).get_team_scheduleIf a command is not listed in references/api-reference.md, it does not exist.
Error: search_markets returns 0 results
Cause: The sport parameter is missing — without it, search only checks high-volume markets and misses single-game events
Solution: Always pass sport='<code>' to search_markets. Check references/api-reference.md for valid sport codes
Error: get_market_prices fails or returns wrong data
Cause: market_id (Gamma) was used instead of token_id (CLOB)
Solution: Call get_market_details(market_id=<id>) first to get the CLOB clobTokenIds, then use those with get_market_prices
Error: Prices seem stale or unchanged
Cause: Low-liquidity market — may have wide spreads and infrequent trades
Solution: Check get_last_trade_price(token_id=<id>) for the most recent actual trade price
Error: Trading commands fail
Cause: py_clob_client is not installed or wallet is not configured
Solution: Run pip install sports-skills[polymarket] and set POLYMARKET_PRIVATE_KEY environment variable
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
polymarket is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in polymarket — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in polymarket — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
polymarket is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in polymarket — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
polymarket is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: polymarket is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend polymarket for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: polymarket is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added polymarket from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 38