Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Polymarket Coffee Trader
v1.0.2Trades Polymarket coffee markets using three compounding seasonal edges unique to the global coffee market — Brazil frost window mispricing, harvest cycle aw...
⭐ 0· 104·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The SKILL.md repeatedly states the default signal 'requires no external API', yet clawhub.json lists a pip dependency (simmer-sdk) and a required env var SIMMER_API_KEY, and trader.py imports SimmerClient and will call the Simmer API to discover and execute trades. Requiring an API key is reasonable for a trading automation, but the documentation/metadata inconsistency is misleading and unacceptable for a credentialed capability.
Instruction Scope
The runtime instructions and code stay within the claimed functional scope (market discovery, conviction sizing, trade execution). The SKILL.md doesn't instruct the agent to read unrelated files or send data to third-party endpoints outside the trading client; however it omits explicit mention that an external trading API and API key are required and used.
Install Mechanism
There is no download-from-URL or archive install; the manifest declares a pip dependency 'simmer-sdk'. Installing a package from PyPI is a normal pattern for an API client but is higher risk than instruction-only skills because it writes code to disk and runs third-party code. No unsafe download URLs were present in the bundle.
Credentials
Top-level metadata in the submission said 'Required env vars: none', but clawhub.json and trader.py use multiple SIMMER_* env vars and require SIMMER_API_KEY. Requesting a single trading API key is proportionate for an automated trader, but the manifest/README inconsistency is a red flag. Before installing, you should confirm exactly which environment variables are required, and what permissions the API key must have (read-only vs trading vs withdrawal).
Persistence & Privilege
always:false and autostart:false — the skill does not demand forced global presence. It is configured as an automaton entrypoint (trader.py) and can be invoked autonomously (disable-model-invocation is false), which is expected for a trading skill. That autonomy combined with an API key increases blast radius, but autonomy alone is normal.
What to consider before installing
Do not hand over credentials or run live trades until you reconcile the contradictions: SKILL.md claims 'no external API', but the manifest and code require simmer-sdk and SIMMER_API_KEY. Ask the author (or inspect simmer-sdk) whether the API key is strictly for simulated/paper trading or can execute/settle real trades; verify minimum required permissions (avoid keys that allow withdrawals). If you proceed, run the skill in paper mode first (the code advertises a --live flag for real trades), inspect the simmer-sdk package source or vendor, and consider running in an isolated environment. Prefer skills with an identifiable source/homepage and clear docs before giving an API key to an unknown bundle.Like a lobster shell, security has layers — review code before you run it.
latestvk976eft5k2qwskz6t7756m7mh5847vdz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.