Polymarket Trading Bot
WarnAudited by ClawScan on May 18, 2026.
Overview
This looks like a real Polymarket trading helper, but it asks for a raw wallet private key and supports autonomous or no-confirmation trades without documented spending limits.
Only install this if you understand the financial risk. Use a dedicated low-balance Polymarket wallet, do not provide your main wallet private key, keep autonomous mode off unless you have strict limits, and review scheduled jobs and stored memory regularly.
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 autonomous mode is enabled, the agent could place unintended or losing orders using real funds.
The skill explicitly permits financial trades without per-trade confirmation when autonomous mode is enabled, but the artifacts do not define spending caps, market scopes, or stop conditions.
Execute trades when the user approves (or autonomously if configured) ... Always confirm with user before trading unless autonomous mode is on!
Require explicit user confirmation for every order unless using a dedicated low-balance wallet with clear per-trade and daily loss limits.
A compromised or misused key could expose wallet funds or enable unauthorized trading.
The setup flow collects a raw Polygon private key and stores it in the skill's Clawdbot configuration, giving the skill high-impact wallet authority.
private_key = questionary.password("Enter your Private Key (starts with 0x...):").ask() ... success = configure_clawdbot("POLYMARKET_KEY", private_key)Use only a dedicated Polymarket wallet with limited funds, verify how Clawdbot stores secrets, and avoid using a primary wallet private key.
Future dependency changes or a compromised package could affect a tool that has access to trading credentials.
The dependency list is unpinned, so installation may fetch changing package versions. This is common for Python tools, but it matters more because the skill handles wallet credentials and trades.
py-clob-client requests rich questionary web3 typer[all]
Prefer pinned dependency versions or a lockfile, and review packages before installing.
Past trades and risk preferences could be retained and reused in later sessions, including if the memory becomes stale or inaccurate.
The skill intends to persist trading history, analysis, and risk preferences in memory. This is purpose-aligned, but it is sensitive financial context that may influence future recommendations.
Use Clawdbot's memory to: Remember user's past trades and outcomes ... Store analysis you've done before ... Remember user's risk profile and preferences
Review what is saved to memory, avoid storing secrets there, and periodically delete outdated or sensitive trading notes.
Scheduled alerts may continue running after the original task if the user forgets about them.
The skill documents scheduled monitoring jobs that can wake later sessions. This is disclosed and aligned with market alerts, but it creates persistent activity beyond the immediate chat.
clawdbot cron --name "Check BTC market" --at "2026-01-28T09:00:00Z" --session main --system-event "Check Bitcoin $150k market status and report" --wake now
Keep a list of scheduled jobs and remove alerts that are no longer needed, especially if autonomous trading is enabled.