Polymarket Prediction Trades — real-time streaming on Polygon

This skill gives you a real-time streaming Polymarket prediction trade feed over WebSocket on Polygon (matic). Every event is a successful prediction trade with outcome token amounts, collateral in USD, price in USD, buyer/seller addresses, market question, outcome label (e.g. "Up" / "Down"), and transaction hash.

Trades are filtered to TransactionStatus.Success: true. The stream uses Bitquery's EVM.PredictionTrades subscription so downstream code can build dashboards, track order flow, or monitor specific markets.

Official docs: Polymarket API — Get Prices, Trades & Market Data (Bitquery).

What to consider before installing

This skill's code implements the described Polymarket stream and contacts only Bitquery. Before installing:

1. Registry metadata: Confirm the registry metadata declares BITQUERY_API_KEY as a required credential. The skill will fail at runtime without it. If the registry does not list this env var, the mismatch with this SKILL.md is the main inconsistency — ask the publisher to update the registry so installers see the requirement.
2. Treat the API key as a secret: Set it in an environment variable only. Do not print or log the full WebSocket URL; the token is passed as ?token=... and can appear in logs, shell history, or monitoring tools. Rotate the key if you suspect it was exposed during testing or use.
3. Sandbox first: Run the bundled script in a sandboxed environment (e.g. virtualenv or container) to observe behavior before relying on it in production.
4. Verify publisher/source: If the skill's homepage or source is unknown, verify the publisher or use an alternative from a trusted source. If the registry declares BITQUERY_API_KEY and the source is validated, this skill is coherent with its stated purpose.
5. Rotate the key if exposed: If the key may have been exposed (e.g. URL printed, committed, or logged), rotate it in the Bitquery dashboard and update your environment.