Polymarket Fast Loop

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

If enabled for live trading, the skill can spend real funds from the configured Polymarket wallet.

Why it was flagged

The skill asks for sensitive wallet authority so it can sign live Polymarket orders.

Skill content
Ask for wallet private key (required for live trading) ... Store in environment as `WALLET_PRIVATE_KEY`
Recommendation

Use a dedicated low-balance wallet, keep the private key out of chat logs, start with dry-run mode, and set strict position and daily budget limits.

What this means

Running with `--live` can place actual Polymarket trades and lose money if the strategy or market conditions are unfavorable.

Why it was flagged

The trading action is explicitly disclosed and gated by live mode, but it is still a high-impact financial operation.

Skill content
All trades execute on Polymarket with real USDC. Use `--live` for real trades, dry-run is the default.
Recommendation

Confirm each live deployment, test in dry-run first, and avoid giving the agent permission to switch to live mode without explicit user approval.

What this means

A cron or heartbeat setup could keep placing trades repeatedly until the user disables it.

Why it was flagged

The documentation shows how to schedule recurring live trading. This is user-directed and not hidden, but it can continue operating after setup.

Skill content
*/5 * * * * cd /path/to/skill && python fastloop_trader.py --live --quiet
Recommendation

Only add scheduled live trading if you understand how to stop it, and periodically verify that the schedule, budget, and wallet balance are still appropriate.

What this means

A bad signal or misconfiguration could lead to repeated losses without automated stop-loss protection.

Why it was flagged

The skill warns that normal stop-loss and take-profit monitoring will not protect these fast trades.

Skill content
Risk monitoring does not apply to sub-15-minute markets... Any risk settings you configure in the Simmer dashboard have no effect on these positions.
Recommendation

Use small position sizes, set a low daily budget, and do not rely on dashboard stop-loss settings for 5-minute or 15-minute markets.

What this means

Future SDK versions could change behavior in a component that handles trading and credentials.

Why it was flagged

The skill relies on an external SDK with a minimum version constraint rather than an exact pinned version.

Skill content
"pip": ["simmer-sdk>=0.11.1"]
Recommendation

Install from a trusted package source and consider pinning a reviewed SDK version in production.