Polymarket Weather Scanner

Exploit NOAA/Open-Meteo forecast vs Polymarket temperature market mispricing. Uses METAR real-time observations + ECMWF + Visual Crossing for 3-source consen...

Do not run the script with --buy until you or a reviewer has inspected the full weather_scanner.py to see how it authenticates and signs trades. Specific actions to consider before installing/running: 1) Review the remainder of weather_scanner.py (missing/truncated portion) to find any code that handles Polymarket buys, especially anything that reads private keys, prompts for secrets, or posts secrets to non-Polymarket endpoints. 2) If the script requires a wallet private key or API token, prefer using an ephemeral wallet with minimal funds and never store a production private key in plaintext. 3) Run the scanner in --dry-run first and run it in a sandboxed environment (restricted network / filesystem) while you audit the code. 4) Confirm that the only external endpoints contacted are the listed services (gamma-api.polymarket.com, open-meteo, aviationweather.gov, visualcrossing) and that no unexpected domains receive POSTs containing sensitive data. 5) If you want higher assurance, ask the publisher for details on the trading/auth flow or request a security review of the full script. Additional information that would raise confidence: the full, untruncated weather_scanner.py showing exactly how buy requests are formed and signed (and where any wallet credentials are stored or provided), or explicit SKILL.md documentation on required wallet/authentication steps.

Type: OpenClaw Skill Name: polymarket-weather-scanner-pro Version: 1.0.0 The bundle is a specialized trading tool designed to identify and exploit mispriced weather markets on Polymarket using meteorological data from sources like Open-Meteo and NOAA. While the script handles sensitive information such as private keys and wallet addresses (via environment variables) and executes a sub-process (trader.py), these actions are directly aligned with its stated purpose of automated trading. No evidence of data exfiltration, malicious persistence, or prompt injection was found in weather_scanner.py or SKILL.md. The script has some functional dependencies not explicitly listed in the requirements (e.g., py_clob_client and a missing trader.py script), but these appear to be unintentional omissions rather than indicators of malice.