Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Polymarket Monitor

v1.0.1

Monitor Polymarket prediction markets and alert when odds cross a threshold. Use when a user wants to track any Polymarket market probability, set up recurri...

0· 679·5 current·5 all-time
byMeir Rosenschein@xmeir-dev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included script and SKILL.md. The skill only needs read-only access to public Polymarket APIs and the ability to send alerts — nothing requested or included is extraneous to that purpose.
Instruction Scope
SKILL.md confines actions to searching Polymarket, fetching market pages, parsing yes/no probabilities, and sending Slack DMs when thresholds are crossed. It does instruct creating a cron job for periodic checks, but does not ask the agent to read local files, other environment variables, or transmit data to unexpected endpoints.
Install Mechanism
No install spec; the only code is a small Python script included in the package. No external downloads, archives, or package installs are requested.
Credentials
The skill declares no required environment variables or credentials. It relies on the agent platform's messaging tool to send Slack DMs; that is appropriate for an alerting skill, but platform-level messaging credentials are not requested by the skill itself.
Persistence & Privilege
always:false (default). The skill's recommended behavior is to install a cron task for periodic checks — this is expected for a monitor/alerting skill and does not modify other skills or system-wide configs.
Assessment
This skill appears internally consistent and low-risk: it fetches public Polymarket endpoints and posts alerts via the agent's messaging tool. Before installing, consider: (1) the agent will create recurring cron jobs that make network requests and can send Slack DMs — confirm you trust the agent's Slack integration and that the message tool has only the permissions you expect; (2) test with a low-frequency schedule and a safe/test Slack channel or user ID; (3) you can run the included Python script locally first to verify behavior; (4) the package has no homepage and an unknown owner—if provenance matters to you, ask the publisher for more information. If you decide to proceed, ensure you know how to cancel the cron job (cron remove <id>) and verify the agent's delivery and alerting behavior on initial runs.

Like a lobster shell, security has layers — review code before you run it.

latestvk97afkcwk06vrfbe6hmdegfg2d81p9h0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

Polymarket Monitor

Set up ongoing monitoring for any Polymarket prediction market with threshold-based alerts.

Workflow

1. Find the market(s)

Search the Gamma API for active markets matching the user's topic:

curl "https://gamma-api.polymarket.com/events?search=<topic>&limit=10&active=true"

Parse the response to find relevant markets. For each, note:

  • conditionId — needed to fetch prices
  • question — market title
  • outcomePrices — current Yes/No probabilities (JSON string)

See references/api.md for full API details.

2. Check current odds

Use the bundled script to fetch current prices for one or more markets:

python3 scripts/check_markets.py <conditionId1> [conditionId2 ...]

Output: JSON with question, yes_prob (0–1 float), and url per market.

3. Report current state

Show the user the markets found and their current probabilities before setting up monitoring.

4. Set up the cron alert

Create a cron job that runs every N minutes (default: 30) with sessionTarget: "isolated" and payload.kind: "agentTurn". The agent task should:

  1. Fetch each market via web_fetch using the Gamma API (conditionId endpoint)
  2. Parse outcomePrices[0] as the Yes probability
  3. If any market exceeds the threshold: send a Slack DM alert via the message tool (channel=slack, target=<user_id>)
  4. If none exceed threshold: do nothing (no output)

Use delivery.mode: "none" to suppress default cron delivery — the agent handles its own alerting.

Template cron task message:

Check these Polymarket markets. For each, fetch:
  https://clob.polymarket.com/markets/<conditionId>
Parse tokens array: find outcome=="Yes" and use its price as probability (0–1).
If any exceeds <threshold> (e.g. 0.70):
  Send Slack DM to <user_slack_id> with: market question, current %, and Polymarket URL.
If none exceed threshold, do nothing.

Markets:
- <question>: https://clob.polymarket.com/markets/<conditionId> | https://polymarket.com/event/<slug>

5. Confirm setup

Tell the user:

  • Which markets are being monitored
  • Current odds for each
  • Alert threshold and check frequency
  • How to cancel (cron job ID + cron remove <id>)

Notes

  • Polymarket has no "today" daily markets — use the nearest deadline market for short-term signals
  • outcomePrices is always ["yes", "no"] — first value is Yes
  • Closed markets return prices of 0 or 1; skip them
  • No API key needed

Files

3 total
Select a file
Select a file to preview.

Comments

Loading comments…