Polymarket Biotech Trader
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a transparent automated trading bot, but live mode can spend real funds and some documented safeguards and credential declarations do not match the reviewed code/configuration.
Treat this as a financial trading bot. Start only in paper mode, do not provide a live-capable SIMMER_API_KEY or use --live until you have reviewed the strategy and code, and verify that minimum volume, days-to-resolution, and position limits are actually enforced.
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 run with --live, the skill can place multiple real-money Polymarket orders based on its own thresholds without asking the user to approve each order.
The code has an explicit live-trading path that submits orders in a loop. In the reviewed file, MIN_VOLUME is read/printed but not checked before client.trade, so live execution is less bounded than the documented risk controls imply.
ap.add_argument("--live", action="store_true", help="Real trades on Polymarket. Default is paper (sim) mode.") ... r = client.trade( market_id=m.id, side=side, amount=size,Use paper mode first, require manual confirmation before live orders, and enforce volume/min-days/position checks directly before client.trade.
A user may believe live trading is more conservatively constrained than it actually is, increasing financial risk.
The documentation advertises conservative safeguards, but clawhub.json/trader.py use different defaults, such as lower or zero min-days/min-volume values, and the code does not enforce market volume before trading.
| Min market volume | $5,000 | FDA markets attract informed traders | ... | Min days to resolution | 7 | Don't enter days before PDUFA |
Align SKILL.md, clawhub.json, and trader.py defaults, and document exactly which safeguards are enforced.
Anyone who can run the skill with a live-capable key and --live can cause trades against the connected account.
The script uses SIMMER_API_KEY to access the Simmer/Polymarket trading venue. This is expected for the stated purpose, but it is sensitive financial authority.
api_key=os.environ["SIMMER_API_KEY"], venue=venue,
Use a paper-only or least-privilege key where possible, keep the key private, and only provide a live-capable key when intentionally enabling live trading.
Dependency or provenance issues could affect code that has access to a trading API key.
The runtime depends on an unpinned third-party SDK, and the registry summary also reports an unknown source/homepage. The dependency is purpose-aligned but should be reviewed because it handles trading credentials.
"pip": [ "simmer-sdk" ]
Pin the SDK version, verify the package provenance, and review updates before using live credentials.
If the user later enables scheduling, the trading logic may run repeatedly and place repeated paper or live orders depending on configuration.
The skill can run as a managed automaton, but the provided configuration does not auto-start it or schedule it by default.
"cron": null, "autostart": false, "automaton": { "managed": true, "entrypoint": "trader.py" }Keep cron/autostart disabled until the strategy and safeguards are reviewed, especially before enabling live mode.