Query and trade on Polymarket prediction markets — check odds, trending markets, search events, view order books, place trades, and manage positions. Now ava...
Security Analysis
medium confidenceThe skill's code and instructions align with its stated purpose (browsing and trading on Polymarket); the main practical risk is the remote installer the README recommends and the usual risks around storing a private key locally.
Name/description, SKILL.md, and scripts/polymarket.py are consistent: read-only features use the public Gamma API (no auth) and trading wraps the official Polymarket CLI. The skill does not request unrelated credentials or bizarre system access.
Runtime instructions stay within the trading/browsing scope. They tell the user/agent to run the included Python script and, for trading, to install and call the Polymarket CLI and to store a private key in ~/.config/polymarket/config.json. This is expected for a trading CLI, but the install step (curl|sh) and local private-key storage are sensitive operations the user should review.
There is no formal install spec in the skill bundle; SKILL.md/README recommend running a remote install script via curl -sSL https://raw.githubusercontent.com/Polymarket/polymarket-cli/main/install.sh | sh. Piping a remote script to sh is high-risk even if hosted on GitHub raw; users should inspect the install.sh (and the polymarket-cli repo/releases) before running it.
The skill declares no required env vars or credentials (proportionate). Trading requires a wallet/private key stored locally (~/.config/polymarket/config.json) which is normal for this functionality, but it is highly sensitive. The skill itself doesn't request unrelated secrets.
always:false and no special persistent privileges requested. The skill does not attempt to modify other skills or system-wide agent configuration.
Guidance
This skill appears to do what it says (browse Polymarket via the Gamma API and wrap the official Polymarket CLI for trades), but take these precautions before installing/using it: 1) Do not blindly run the recommended curl | sh installer — review the install.sh file and the polymarket-cli repository and releases on GitHub first. 2) Prefer installing polymarket-cli from a verified release or package manager if available. 3) Be careful with your private key: understand that the CLI will read ~/.config/polymarket/config.json and that any command that triggers an on-chain action will use real USDC on Polygon. 4) Use small amounts or a throwaway wallet until you trust the tool. 5) Confirm that all trades require your explicit --confirm and that your agent will not autonomously place trades without consent. 6) If possible, use a hardware wallet or manual signing to reduce exposure. If you want, provide the full remaining portion of scripts/polymarket.py so I can scan the rest of the code for unexpected behavior.
Latest Release
v1.2.1
Fix display name (remove Clawdbot prefix)
More by @mvanhorn
Published by @mvanhorn on ClawHub
