Polymarket Monitor
PassAudited by ClawScan on May 1, 2026.
Overview
The skill matches its stated purpose of monitoring public Polymarket odds, with the main thing to notice being a recurring cron task that can send Slack alerts until removed.
Before using this skill, confirm the market condition IDs, alert threshold, check frequency, and Slack recipient. Keep the cron job ID so you can remove the recurring monitor when it is no longer needed.
Findings (2)
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.
The monitor may keep running and checking markets on a schedule after setup.
This creates recurring autonomous agent execution. It is aligned with the stated monitoring purpose, but it will continue until cancelled.
Create a cron job that runs every N minutes (default: 30) with `sessionTarget: "isolated"` and `payload.kind: "agentTurn"`.
Confirm the exact markets, threshold, frequency, and cron job ID; remove the cron job when monitoring is no longer wanted.
The monitored market name, probability, and URL may be shared in Slack; a wrong target could disclose the alert to the wrong recipient.
Alerts are sent through an external messaging channel to a user-supplied Slack target.
send a Slack DM alert via the `message` tool (channel=slack, target=<user_id>)
Verify the Slack user ID or channel before enabling alerts, and avoid including sensitive context in alert messages.