polymarket
Query Polymarket: markets, prices, orderbooks, history.
What this skill does
# Polymarket — Prediction Market Data Query prediction market data from Polymarket using their public REST APIs. All endpoints are read-only and require zero authentication. See `references/api-endpoints.md` for the full endpoint reference with curl examples. ## When to Use - User asks about prediction markets, betting odds, or event probabilities - User wants to know "what are the odds of X happening?" - User asks about Polymarket specifically - User wants market prices, orderbook data, or price history - User asks to monitor or track prediction market movements ## Key Concepts - **Events** contain one or more **Markets** (1:many relationship) - **Markets** are binary outcomes with Yes/No prices between 0.00 and 1.00 - Prices ARE probabilities: price 0.65 means the market thinks 65% likely - `outcomePrices` field: JSON-encoded array like `["0.80", "0.20"]` - `clobTokenIds` field: JSON-encoded array of two token IDs [Yes, No] for price/book queries - `conditionId` field: hex string used for price history queries - Volume is in USDC (US dollars) ## Three Public APIs 1. **Gamma API** at `gamma-api.polymarket.com` — Discovery, search, browsing 2. **CLOB API** at `clob.polymarket.com` — Real-time prices, orderbooks, history 3. **Data API** at `data-api.polymarket.com` — Trades, open interest ## Typical Workflow When a user asks about prediction market odds: 1. **Search** using the Gamma API public-search endpoint with their query 2. **Parse** the response — extract events and their nested markets 3. **Present** market question, current prices as percentages, and volume 4. **Deep dive** if asked — use clobTokenIds for orderbook, conditionId for history ## Presenting Results Format prices as percentages for readability: - outcomePrices `["0.652", "0.348"]` becomes "Yes: 65.2%, No: 34.8%" - Always show the market question and probability - Include volume when available Example: `"Will X happen?" — 65.2% Yes ($1.2M volume)` ## Parsing Double-Encoded Fields The Gamma API returns `outcomePrices`, `outcomes`, and `clobTokenIds` as JSON strings inside JSON responses (double-encoded). When processing with Python, parse them with `json.loads(market['outcomePrices'])` to get the actual array. ## Rate Limits Generous — unlikely to hit for normal usage: - Gamma: 4,000 requests per 10 seconds (general) - CLOB: 9,000 requests per 10 seconds (general) - Data: 1,000 requests per 10 seconds (general) ## Limitations - This skill is read-only — it does not support placing trades - Trading requires wallet-based crypto authentication (EIP-712 signatures) - Some new markets may have empty price history - Geographic restrictions apply to trading but read-only data is globally accessible
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.