Polymarket Screener
ReviewAudited by ClawScan on May 10, 2026.
Overview
The visible Polymarket API code is mostly purpose-aligned, but the package points to a missing screener script and includes an unrelated content-writing script that logs local history.
Review this skill before installing or running it. The Polymarket API-reading behavior appears low risk, but the package should be fixed so the documented script exists, the unrelated content assistant script is removed or explained, and local logging/cache behavior is disclosed.
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.
The agent may fail, run a different command than documented, or rely on package contents that do not match the advertised workflow.
The documented executable path is not present in the file manifest, which lists scripts/polymarket.sh and scripts/script.sh instead. The visible Polymarket script also uses different command names such as markets, odds, and value-bets.
bash scripts/polymarket-screener.sh list --limit 20 ... Run `polymarket-screener help`
Do not rely on this package until the maintainer updates SKILL.md, adds the referenced executable or corrects the path, and documents the actual CLI commands.
This mismatch makes the package provenance and intended runtime behavior unclear, and could cause the user or agent to invoke unrelated functionality under the trusted skill name.
An included runnable script names itself polymarket-screener but implements unrelated content creation commands rather than Polymarket screening.
# polymarket-screener - Content creation and optimization assistant ... Commands: draft, headline, outline, seo, schedule
Remove the unrelated script or clearly explain why it is included; keep only purpose-aligned files in the skill package.
Topics or text passed to that helper could remain on disk locally, even though no external transmission is shown.
The unrelated helper persists command arguments to a local history file under the skill's data directory.
_log() { echo "$(date '+%m-%d %H:%M') $1: $2" >> "$DATA_DIR/history.log"; }Disclose local logging, provide a cleanup or opt-out option, and avoid entering sensitive text if using the bundled scripts.