← Back to Skills Marketplace
Polymarket Real Time Trades Stream
by
Divyasshree
· GitHub ↗
· v1.0.5
· MIT-0
337
Downloads
0
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install polymarket-real-time-trades
Description
Real-time streaming Polymarket prediction trades on Polygon (matic) with live USD pricing. Subscribe to a live stream of Polymarket prediction market trades...
Usage Guidance
This skill appears to be internally consistent and implements exactly what it claims. Before installing: (1) verify the registry entry properly declares BITQUERY_API_KEY (the provided metadata looks malformed), (2) run the script in an isolated environment (virtualenv or container) to limit logging/monitoring exposure, (3) do not print or log the full WebSocket URL anywhere — Bitquery requires the token as ?token= which can be captured by logs or proxies, (4) store BITQUERY_API_KEY in a secure environment variable and restrict who can read it, and (5) be prepared to rotate the API key immediately if you suspect it was exposed. If you want extra assurance, review the script in your environment to confirm it never prints the URL and run network/logging tests in a sandbox to validate that your infrastructure does not inadvertently capture query-strings.
Capability Analysis
Type: OpenClaw Skill
Name: polymarket-real-time-trades
Version: 1.0.5
The skill is a legitimate tool for streaming real-time Polymarket trade data via the Bitquery GraphQL API. The Python script (scripts/stream_polymarket.py) correctly implements the WebSocket subscription and includes extensive documentation (SKILL.md) regarding the inherent security risks of the Bitquery API (which requires the API key in the connection URL). No evidence of data exfiltration, malicious execution, or prompt injection was found; the code is transparent and aligns perfectly with its stated purpose.
Capability Assessment
Purpose & Capability
Name/description, SKILL.md, requirements.txt, and scripts/stream_polymarket.py all consistently implement a Bitquery WebSocket subscription for Polymarket PredictionTrades and only require BITQUERY_API_KEY. The only mismatch is the registry metadata shown as "Required env vars: [object Object]" — SKILL.md declares BITQUERY_API_KEY but the registry entry appears malformed and should be corrected.
Instruction Scope
The runtime instructions are narrowly scoped: set BITQUERY_API_KEY, install gql[websockets], and run the streaming script. The SKILL.md explicitly warns about the token-in-URL behavior and recommends sandboxing and not logging the URL. The script only reads BITQUERY_API_KEY and prints formatted trade events; it does not access unrelated files or external endpoints other than Bitquery.
Install Mechanism
No install spec is provided (instruction-only), which reduces installation risk. A requirements.txt lists gql[websockets], which is appropriate for the script. There are no downloads from untrusted URLs or extract operations in the package.
Credentials
Only BITQUERY_API_KEY is required, which is proportionate to the skill's purpose. Note however the registry metadata appears to not properly declare environment requirements (shows [object Object]) — ensure that BITQUERY_API_KEY is actually registered as the required credential in the registry before installation so installers are prompted for the token and it isn't accidentally omitted or stored incorrectly.
Persistence & Privilege
The skill does not request persistent platform privileges; always:false and no config-paths or ability to modify other skills. The agent may invoke it autonomously by default (normal behavior) but the skill itself does not create persistent system changes.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install polymarket-real-time-trades - After installation, invoke the skill by name or use
/polymarket-real-time-trades - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.5
- Updated required credential metadata from the old `credentials` block to the new `requires.env` format in SKILL.md.
- No code or functional changes; metadata only.
- Ensures install prompt for BITQUERY_API_KEY is consistent with updated skill ecosystem standards.
v1.0.4
**Version 1.0.4 Changelog**
- Added formal credentials and trigger_phrases metadata for improved discoverability and install guidance.
- Expanded, clarified, and emphasized critical security warnings about Bitquery API token exposure via WebSocket URL.
- Introduced a detailed Security Checklist section to ensure safe usage and key protection.
- Updated installation/usage instructions for greater clarity and focus on token handling risks.
- Revised, condensed, and standardized language across prerequisites and credential guidance for consistency and security.
v1.0.3
Version 1.0.3
- Clarified that Bitquery streaming token authentication is only supported via WebSocket URL (not headers).
- Added prominent warnings about risk of token exposure in logs, shell history, or IDE history if URL is printed.
- Updated credential section to emphasize URL-only auth, environment variable storage, and key rotation if exposed.
- Reorganized guidance for credential management and security best practices.
- No code changes; documentation improvements only.
v1.0.2
- Expanded triggers and description to explicitly include sports odds, Bitcoin Up/Down, and crypto prediction markets in addition to general Polymarket trades.
- Clarified that the skill covers all Polymarket markets, including new use cases like sports odds and cryptocurrency up/down markets.
- Updated trigger phrases to include "polymarket sports odds", "bitcoin up down", and other relevant real-time Polymarket requests.
- No code or logic changes; documentation/metadata update only.
v1.0.1
No functional changes; documentation clarifications only.
- Updated SKILL.md to clarify credential requirements, especially the need for `BITQUERY_API_KEY` and implications for installers.
- Added more explicit registry guidance about the environment variable.
- Emphasized best practices for API key handling and secret management.
- Improved warnings about accidental API key exposure and added recommendations to rotate keys if exposed.
- Minor rewording and restructuring; no changes to code, dependencies, or behavior.
v1.0.0
Initial release: real-time Polymarket prediction trade streaming on Polygon.
- Streams live Polymarket trades with buyer, seller, amount, collateral in USD, price, and order ID.
- Provides full market metadata, including question title, resolution source, outcome labels, and transaction details.
- Uses Bitquery GraphQL WebSocket subscription; requires BITQUERY_API_KEY passed in the URL.
- Designed for monitoring order flow, whale trades, market activity, and trade-specific filtering.
- Includes install instructions, credential handling tips, and example scripts for quick setup.
Metadata
Frequently Asked Questions
What is Polymarket Real Time Trades Stream?
Real-time streaming Polymarket prediction trades on Polygon (matic) with live USD pricing. Subscribe to a live stream of Polymarket prediction market trades... It is an AI Agent Skill for Claude Code / OpenClaw, with 337 downloads so far.
How do I install Polymarket Real Time Trades Stream?
Run "/install polymarket-real-time-trades" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Polymarket Real Time Trades Stream free?
Yes, Polymarket Real Time Trades Stream is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Polymarket Real Time Trades Stream support?
Polymarket Real Time Trades Stream is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Polymarket Real Time Trades Stream?
It is built and maintained by Divyasshree (@divyn); the current version is v1.0.5.
More Skills