Polymarket Ai Divergence
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a real Polymarket trading skill, but live trading, wallet-key use, and inconsistent spend-limit documentation make it something users should review carefully before enabling.
Only use this with a small dedicated wallet, confirm the exact live-trading limits shown by the runtime config, and do a dry run before enabling `--live`. The skill is not clearly malicious, but the budget/default mismatches are important for a tool that can spend real money.
Findings (5)
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.
If live mode is used with the wrong limits, the agent may place real trades and spend more than the user expected.
The skill contains live trade execution code. That is purpose-aligned, but it is a high-impact action because it can spend real funds, so unclear or inconsistent trading limits materially affect user safety.
result = get_client().trade(
market_id=market_id,
side=side,
amount=amount,Use dry-run mode first, inspect the actual runtime config with `--config`, set explicit small limits, and require user confirmation before any live run.
A user may believe the skill is limited to smaller trades or daily spending than the managed configuration actually applies.
The managed tunables show higher defaults than the SKILL.md table, which documents `max_bet_usd` default 5.0 and `daily_budget` default 25.0. For a trading skill, conflicting spend defaults can mislead users about financial exposure.
"SIMMER_DIVERGENCE_MAX_BET_USD",
"type": "number",
"default": 50
...
"SIMMER_DIVERGENCE_DAILY_BUDGET_USD",
"type": "number",
"default": 100Align SKILL.md, code defaults, and clawhub.json tunables; prominently show the exact live-trading budget before executing trades.
User-supplied safety limits may not take effect, increasing the chance of unintended live trades or spend.
The code uses env var names with `_USD` and `_PER_RUN`, while SKILL.md documents different names such as `SIMMER_DIVERGENCE_MAX_BET`, `SIMMER_DIVERGENCE_MAX_TRADES`, and `SIMMER_DIVERGENCE_DAILY_BUDGET`. Users following the documentation may set limits that the code does not read.
"max_bet_usd": {"env": "SIMMER_DIVERGENCE_MAX_BET_USD", "default": 5.0, "type": float},
"max_trades_per_run": {"env": "SIMMER_DIVERGENCE_MAX_TRADES_PER_RUN", "default": 3, "type": int},
"daily_budget": {"env": "SIMMER_DIVERGENCE_DAILY_BUDGET_USD", "default": 25.0, "type": float}Fix the documented environment variable names or make the code accept both old and new names, especially for budget and max-trade limits.
Anyone or any process with access to that private key may be able to sign transactions or orders for the wallet.
A wallet private key grants signing authority for trades. This is expected for live trading, and the artifacts disclose it, but it is still a sensitive permission boundary.
Ask for wallet private key (required for live trading) ... Store in environment as `WALLET_PRIVATE_KEY` ... The SDK uses this to sign orders client-side automatically
Use a dedicated trading wallet with limited funds, store the key securely, and avoid reusing a wallet that holds unrelated assets.
A compromised or unexpected SDK version could affect trading behavior or credential handling.
The skill relies on an external SDK for API access and trade execution. That dependency is central to the stated purpose, but users are trusting the package and its updates.
pip install simmer-sdk
Install from the official package source, pin a reviewed version, and update deliberately.