Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Polymarket Micro Weather Sniper Trader

v0.0.2

Trades Polymarket weather temperature markets using NOAA and Open-Meteo forecasts as an information edge. Buys YES on bins matching the forecast at discount...

0· 126·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for diagnostikon/polymarket-micro-weather-sniper-trader.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Polymarket Micro Weather Sniper Trader" (diagnostikon/polymarket-micro-weather-sniper-trader) from ClawHub.
Skill page: https://clawhub.ai/diagnostikon/polymarket-micro-weather-sniper-trader
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install polymarket-micro-weather-sniper-trader

ClawHub CLI

Package manager switcher

npx clawhub@latest install polymarket-micro-weather-sniper-trader
Security Scan
Capability signals
CryptoRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's code and SKILL.md match the stated purpose: it discovers Polymarket weather markets, fetches forecasts, and places micro trades via the Simmer SDK. Requesting an API key named SIMMER_API_KEY is proportionate for trading. However, the registry summary at the top incorrectly lists 'Required env vars: none' and 'No install spec' while clawhub.json and SKILL.md declare SIMMER_API_KEY and a pip dependency (simmer-sdk). This manifest mismatch is a coherence issue (likely sloppy packaging) that should be resolved.
Instruction Scope
Runtime instructions and the trader.py code limit actions to: market discovery via SimmerClient, HTTP calls to NOAA / Open-Meteo / wttr.in for forecasts, parsing questions, and placing/toggling trades. The instructions do not instruct the agent to read unrelated files or exfiltrate system data. Network calls are to expected public weather APIs and the Simmer API.
Install Mechanism
No arbitrary download or extractor is used. The dependency is a PyPI package (simmer-sdk), which is expected for a trading SDK and is a moderate but traceable risk. Again, SKILL.md and clawhub.json declare pip:simmer-sdk even though the top-level 'No install spec' statement contradicts this — confirm how the platform will install dependencies and verify the simmer-sdk package origin and integrity on PyPI/GitHub before installing.
Credentials
The skill requests a single high-value credential, SIMMER_API_KEY, which is necessary and proportionate for placing trades. The code will use that key to create a SimmerClient and may execute live trades when invoked with --live. Ensure you understand the privileges granted by SIMMER_API_KEY (ability to place/cancel trades, withdraw funds, etc.) and that no other secrets are required. The manifest inconsistency (registry claiming no env required) is confusing and should be clarified.
Persistence & Privilege
The skill is not always-enabled (always:false), autostart/cron are false/null, and it does not request system-wide configuration changes. The skill does call _client.apply_skill_config(SKILL_SLUG) if available, which is limited to applying its own config. Autonomous model invocation is allowed by default but not, by itself, a red flag — however, combining autonomous invocation with live-trading capability means you should restrict or test runs in paper mode first.
What to consider before installing
This skill generally does what it says: it fetches public weather forecasts and uses the Simmer SDK to place micro trades. Before installing or giving it a SIMMER_API_KEY: 1) Confirm the platform's manifest (registry) vs. the included files — the top-level registry incorrectly lists no required env/install; trust the included clawhub.json and SKILL.md which require SIMMER_API_KEY and simmer-sdk. 2) Inspect or vet the simmer-sdk PyPI package and its GitHub repo (author, releases, checksums) before pip installing. 3) Run the skill in paper mode (default) and review logs/placed simulated orders to validate behavior. 4) Only enable live trading (--live) after testing and after understanding the exact permissions of SIMMER_API_KEY; consider using a restricted/trading-only API key and set conservative tunables. 5) Because the code makes external HTTP calls, verify no hidden endpoints are present in the remaining (truncated) portions of trader.py and review the repository history if available. If you need higher assurance, ask the publisher for a signed release or audit of simmer-sdk and the full trader.py source.

Like a lobster shell, security has layers — review code before you run it.

latestvk977b432fqhnnygsyrefm8wg0x8530z3
126downloads
0stars
3versions
Updated 1w ago
v0.0.2
MIT-0

Micro Weather Sniper Trader

This is a template. The default signal uses NOAA (US) and Open-Meteo (global) weather forecasts to find mispriced temperature bins on Polymarket -- remix it with additional weather sources, ensemble model averaging, or multi-day position building. The skill handles all the plumbing (market discovery, forecast fetching, bin matching, trade execution, safeguards). Your agent provides the alpha.

Strategy Overview

Polymarket lists "highest temperature" bin markets for cities worldwide (e.g. "Will the highest temperature in Warsaw be 10°C on April 10?"). These bins are priced by market participants who often lack access to professional weather forecast data.

This skill fetches actual weather forecasts from NOAA (US cities, ~85% accuracy for 1-2 day predictions) and Open-Meteo (global cities, free API, similar accuracy). It then compares the forecast temperature against each market bin:

  • If the forecast matches the bin and the market price is low (p <= 20%): BUY YES -- the market is underpricing a likely outcome.
  • If the forecast disagrees with the bin and the market price is high (p >= 80%): SELL NO -- the market is overpricing an unlikely outcome.

Example: Open-Meteo forecasts Warsaw high = 10°C on April 10. The bin "Warsaw 10°C" is priced at p=20%. Edge = 0.85 - 0.20 = 0.65. Conviction = 0.65 / 0.85 = 0.76. Size = max($2, 0.76 * $5) = $3.82. The skill buys YES at $3.82.

Edge

Weather forecasts from NOAA and Open-Meteo are publicly available but not widely used by Polymarket participants. NOAA 1-2 day high temperature forecasts have documented accuracy of approximately 85%. This creates a structural information edge:

  • The forecast provides a probability estimate (~85%) that the temperature will fall in a specific range
  • Polymarket bins are priced by retail participants without systematic forecast data
  • When the forecast-implied probability (85%) diverges from market price (e.g. 20%), the difference is pure edge
  • Weather markets resolve daily, providing rapid feedback and capital recycling
  • Micro-sizing ($2-$5) means each trade has minimal risk while maintaining consistent exposure

Signal Logic

  1. Discover active weather markets via keyword search across all supported cities plus get_fast_markets() and get_markets(limit=200) bulk scan
  2. Parse each market question: extract city name, temperature range (bin), and resolution date
  3. Fetch NOAA forecast (US cities) or Open-Meteo forecast (global cities) for each relevant city
  4. For each market: check if the forecast temperature falls within the bin
  5. If forecast matches bin AND p <= YES_THRESHOLD (0.40): buy YES -- conviction = (0.85 - p) / 0.85, size = max($2, conviction * $5)
  6. If forecast disagrees with bin AND p >= NO_THRESHOLD (0.80): sell NO -- conviction = (p - 0.15) / 0.85, size = max($2, conviction * $5)
  7. Spread gate: skip if spread > MAX_SPREAD (15%)
  8. Place up to MAX_POSITIONS (10) micro trades per run
  9. All trades include signal_data with forecast temperature, city, and edge for backtest support

Remix Signal Ideas

  • Ensemble averaging: Combine NOAA + Open-Meteo + AccuWeather forecasts and weight by historical accuracy per city
  • Confidence scaling: NOAA is more accurate for D+1 than D+3 -- scale conviction by forecast horizon
  • Multi-bin strategy: When forecast is between two bins (e.g. 9.9°C between 9°C and 10°C bins), buy YES on both at half size
  • Exit management: Monitor positions and sell when price reaches EXIT_THRESHOLD (take profit) or forecast changes
  • Historical calibration: Track forecast accuracy per city per season to dynamically adjust NOAA_ACCURACY

Safety & Execution Mode

The skill defaults to paper trading (venue="sim"). Real trades only with --live flag.

ScenarioModeFinancial risk
python trader.pyPaper (sim)None
Cron / automatonPaper (sim)None
python trader.py --liveLive (polymarket)Real USDC

autostart: false and cron: null mean nothing runs automatically until configured in Simmer UI.

Required Credentials

VariableRequiredNotes
SIMMER_API_KEYYesTrading authority. Treat as a high-value credential.

Tunables (Risk Parameters)

All declared as tunables in clawhub.json and adjustable from the Simmer UI.

VariableDefaultPurpose
SIMMER_MAX_POSITION5Max USDC per micro trade (ceiling at 100% conviction)
SIMMER_MIN_TRADE2Floor for any trade (min USDC regardless of conviction)
SIMMER_MAX_SPREAD0.15Max bid-ask spread (15%)
SIMMER_MIN_DAYS0Min days until resolution (0 = allow same-day weather)
SIMMER_MAX_POSITIONS10Max concurrent micro positions
SIMMER_YES_THRESHOLD0.40Buy YES when forecast matches bin and p <= this
SIMMER_NO_THRESHOLD0.80Sell NO when forecast disagrees with bin and p >= this

Dependency

simmer-sdk is published on PyPI by Simmer Markets.

Comments

Loading comments...