Polymarket Candle Volume Spike Trader
v1.0.1Cross-coin volume spike detection for crypto Up or Down markets on Polymarket. When 3+ coins (BTC, ETH, SOL, XRP) simultaneously show strong same-direction c...
⭐ 0· 55·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
Benign
high confidencePurpose & Capability
Name/description match the code and metadata: the skill targets Polymarket 5-minute Up/Down markets for BTC/ETH/SOL/XRP and requires the Simmer SDK and SIMMER_API_KEY to execute trades, which is proportionate to the stated purpose.
Instruction Scope
SKILL.md and trader.py focus on market discovery, parsing, spike detection, sizing, and execution. The runtime instructions and code only reference Simmer APIs and environment tunables; they do not instruct reading unrelated files or sending data to external endpoints beyond the Simmer client.
Install Mechanism
No install spec is present; clawhub.json declares a pip dependency on 'simmer-sdk', which is expected for interacting with the Simmer runtime but is a third-party package (moderate supply-chain risk). This is appropriate for the skill's purpose but you may want to vet the simmer-sdk package before running live.
Credentials
Only SIMMER_API_KEY is required (declared in SKILL.md and clawhub.json) and is necessary for trading. The skill documents that this is a high-value credential and defaults to paper trading unless '--live' is used; no other unrelated secrets or environment paths are requested.
Persistence & Privilege
The skill is not forced-always; autostart is false and automaton autostart is disabled. It will not run automatically without explicit configuration. It doesn't request system-wide privileges or modify other skills' configurations.
Assessment
This skill appears coherent and limited to Polymarket trading via the Simmer SDK. Before installing or running live: (1) keep the default paper mode for testing; (2) treat SIMMER_API_KEY as a high-value secret—use a key with minimal permissions and rotate it if needed; (3) review the simmer-sdk package source or pin a known-safe version to reduce supply-chain risk; (4) test behavior in a controlled/simulated environment to confirm sizing and safeguards; (5) do not run with --live until you are comfortable with the strategy and limits.Like a lobster shell, security has layers — review code before you run it.
latestvk970vg5m4kjdyaygfnfafhvyzs8478rx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
