Polymarket Analysis
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a read-only Polymarket analysis skill, with the main user-noticeable risk being optional 24/7 monitoring that creates recurring agent jobs and local state.
This skill is reasonable for read-only Polymarket research. Before installing, note that Monitor mode can create a recurring background cron job and store market state locally; disable or remove monitors when done. Treat wallet profile lookups and alert delivery channels as public/intentional data flows, and verify Python 3 is available if you plan to run the included scripts.
Findings (3)
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 enabled, a monitor can keep running every few minutes and send alerts until the user pauses or removes the cron job.
The skill documents creating recurring autonomous agent turns for market monitoring. This is aligned with the Monitor mode and includes management commands, but it is persistent background behavior.
24/7 monitoring via clawdbot cron jobs ... "schedule": { "kind": "every", "everyMs": 300000 }, ... "payload": { "kind": "agentTurn"Only create monitors for markets you intend to track, periodically list active cron jobs, and remove or disable monitors when they are no longer needed.
Local state files may retain which markets were monitored and stale or manually changed state can produce misleading alerts.
The monitor keeps local market state and reuses it to compare later runs. The stored data appears to be public market data, but it can affect future alert calculations.
STATE_DIR = SCRIPT_DIR.parent / "state" ... previous = load_state(market_id) ... save_state(market_id, current)
Review or clear the state directory when stopping monitors, changing thresholds, or investigating unexpected alerts.
The helper commands may not work unless Python 3 is available, and users should be aware they are running local scripts.
The skill uses included Python helper scripts even though the registry requirements declare no required binaries. The scripts are visible and no package installation is requested, so this is a disclosure/metadata note rather than a behavioral concern.
python3 scripts/monitor-polymarket-market.py <market_url_or_id> python3 scripts/fetch-polymarket-user-profile.py <wallet_address> [--trades] [--pnl]
Confirm Python 3 is available before using the scripts; maintainers should declare Python as a required binary for clearer installation expectations.