Polymarket Geopolitics Trader
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Polymarket trading skill, but its documented safety limits do not match the actual defaults and live mode can use a high-value trading key for real USDC trades.
Use this skill only if you understand automated prediction-market trading risk. Leave it in paper mode until you have reviewed the code, reconciled the documented versus actual tunables, pinned or verified the dependency, and set strict position limits before supplying a live trading key.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user may believe the bot will avoid lower-liquidity, wider-spread, near-resolution, or higher-count positions when the actual defaults allow them.
The user-facing safety table describes more conservative defaults than the provided code/config: trader.py and clawhub.json default to MIN_VOLUME 1000, MAX_SPREAD 0.12, MIN_DAYS 0, and MAX_POSITIONS 8. For a financial trading bot, overstating these safeguards can materially change user expectations.
`SIMMER_MIN_VOLUME` | `20000`; `SIMMER_MAX_SPREAD` | `0.08`; `SIMMER_MIN_DAYS` | `5`; `SIMMER_MAX_POSITIONS` | `6`
Align SKILL.md, trader.py, and clawhub.json defaults before live use, and manually verify all tunables in the Simmer UI.
If enabled in live mode, the agent may commit real USDC according to automated strategy logic and the actual configured limits.
When live mode is enabled, the skill switches from paper trading to a real Polymarket venue using the SIMMER_API_KEY. The visible artifacts show a live-mode gate and tunables, but not a per-trade confirmation mechanism, and the documented safety limits conflict with actual defaults.
venue = "polymarket" if live else "sim" ... api_key=os.environ["SIMMER_API_KEY"] ... if live: _client.live = True
Keep the skill in paper mode until reviewed, require explicit approval for live runs or individual trades, and set conservative caps before providing a trading key.
Anyone or any code with this key may be able to perform trading actions through the configured Simmer/Polymarket integration.
The credential requirement is disclosed and purpose-aligned, but it grants trading authority and should be treated as sensitive. The registry summary also under-declares this by listing no required env vars or primary credential.
`SIMMER_API_KEY` | Yes | Trading authority. Treat as high-value credential.
Use the least-privileged key available, avoid sharing it with unrelated skills, monitor account activity, and revoke or rotate it if no longer needed.
Future or unexpected dependency versions could change trading behavior or credential handling.
The required Python dependency is unpinned. This is expected for a Simmer trading integration, but package provenance and version changes affect a skill that handles financial trading credentials.
"pip": [ "simmer-sdk" ]
Pin a reviewed simmer-sdk version and verify the package source before enabling live trading.