Prediction Market Arbitrage
v1.0.0Orchestrates monitoring, market odds, and execution proxy tools to detect news-market price gaps and emit arbitrage alerts with optional trade plans.
⭐ 2· 688·2 current·2 all-time
byHagen Hoferichter@h4gen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name and description match the actions in SKILL.md: it orchestrates topic-monitor, polymarket-odds, and simmer-weather for arbitrage alerting. Requiring python3/node/npx is expected because the upstream skills are Python/Node and installation uses npx. One minor mismatch: SIMMER_API_KEY is declared as required even though the workflow explicitly supports an 'alert-only' execution_mode; making the API key mandatory is not strictly necessary for alert-only operation.
Instruction Scope
The SKILL.md confines runtime actions to invoking the three upstream skills, normalizing values, applying hard decision rules, and emitting alerts or execution plans. It does not instruct the agent to read unrelated system files, other environment variables, or external endpoints beyond the described ClawHub skills and Simmer endpoints. It explicitly warns not to auto-trade unless the user asks.
Install Mechanism
This is instruction-only (no install spec or code blobs). The recommended install uses npx clawhub@latest to install upstream skills — a reasonable, traceable approach. No downloads from arbitrary URLs or archive extractions are present in the skill itself.
Credentials
Only one env var is requested: SIMMER_API_KEY. That is expected for the simmer-weather execution proxy, but declaring it as required (rather than optional) is disproportionate if users will run in alert-only mode. SIMMER_API_KEY is a trading credential; supplying it enables live trading via the cited execution proxy if downstream components or operators invoke execution. Users should treat this key as sensitive, store it in a secrets manager, and avoid providing it unless they intend to permit trade execution.
Persistence & Privilege
The skill does not request always:true, does not modify other skills' configs, and does not demand persistent system-wide privileges. user-invocable is true and autonomous invocation is allowed (disable-model-invocation:false) — this is platform-default and acceptable here, but users should be mindful that an agent with this skill could be asked to perform repeated monitoring and, if credentials are supplied, to prepare execution plans.
Assessment
This skill appears to do what it says: orchestrate monitoring, market lookups, and optional execution guidance. Before installing, consider these steps: (1) Only provide SIMMER_API_KEY if you explicitly want the agent to be able to produce execution plans or run dry-run/live trades; otherwise keep it unset and use alert-only mode. (2) Store SIMMER_API_KEY in a secrets manager or environment that is not broadly accessible, and rotate it regularly. (3) Audit the upstream skills (topic-monitor, polymarket-odds, simmer-weather) that this meta-skill orchestrates — the meta-skill delegates behavior to them. (4) Run the workflow in dry-run mode first and verify that alerts and decision logic behave as expected. (5) Limit agent autonomy and review logs before enabling any live execution path. If you want a stricter review, provide the upstream skills' code or the Simmer SDK docs so I can check exactly how the API key is used and whether any hidden network endpoints are contacted.Like a lobster shell, security has layers — review code before you run it.
latestvk97ecj8kxp3k1mt12sh1nje6a1815da8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
chart_with_upwards_trend Clawdis
Binspython3, node, npx
EnvSIMMER_API_KEY