Polymarket Analysis
v2.1.0Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
⭐ 15· 6.2k·52 current·53 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Polymarket analysis, arbitrage, whale tracking, sentiment, momentum) align with included scripts and reference docs. The code calls public Polymarket Gamma/Data/CLOB endpoints and implements only read-only analysis and local state management — no trading/execution or unrelated cloud credentials are requested.
Instruction Scope
SKILL.md and references describe 1-off analysis and a 24/7 monitor using cron jobs. The monitor and profile scripts only fetch public endpoints and read/write a local state file. The monitoring instructions include creating cron jobs that can deliver alerts to external channels (WhatsApp/Telegram/Discord/last). This is expected for an alerting monitor, but users should understand that alerts will be delivered via whatever channel the cron/agent is configured to use.
Install Mechanism
No install spec; the skill is instruction-plus-scripts only. There is no external archive download or package installation. Scripts are plain Python and use standard library network calls (urllib). Low install risk.
Credentials
No required environment variables, no credentials, and no config paths beyond the skill's own state directory. The skill only needs network egress to public Polymarket endpoints; requested resources are proportionate to market monitoring and profile fetching.
Persistence & Privilege
The monitor writes per-market state files under the skill's state directory (state/*.json) and the docs instruct creating persistent cron jobs. always:true is not set. Persistent monitoring and autonomous invocation are expected for this use case; users should be aware monitors may run continuously and produce network traffic and alerts.
Assessment
This skill appears to do what it says: read public Polymarket APIs, analyze markets, track wallets, and optionally run a persistent monitor. Before installing, consider: 1) Where alerts will be delivered — cron examples show external channels (WhatsApp/Telegram/Discord); confirm you control the configured delivery target. 2) The monitor will create and update local state files under the skill's state directory (used to compare prior checks). 3) The skill performs network requests to public Polymarket endpoints (rate limits may apply). 4) No credentials are requested, and there is no code that executes trades, spawns shell commands, or reaches out to unknown third-party servers — but if you adapt the cron delivery or copy-trade logic, review any additions that add outbound destinations or require keys. If you want extra assurance, run the scripts locally with a test market/wallet and inspect the alerts and created state files before enabling 24/7 monitoring.Like a lobster shell, security has layers — review code before you run it.
latestvk972ddf6e04hbzwznrf8f0rtts805vd8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.