Prediction Stack Setup

Interactive setup wizard for the OpenClaw Prediction Market Trading Stack. Detects installed skills, walks through API key configuration, creates cron jobs f...

This skill is plausible for wiring a prediction-market stack, but there are clear mismatches you should resolve before running it with real secrets: 1) The registry metadata does not declare the environment variables or credentials the SKILL.md and script expect (Kalshi private key, Anthropic key, optional Polygon key). Treat those as required sensitive inputs. 2) The README/SKILL.md promise to create cron jobs, enable heartbeat, and set up iMessage delivery, but the included script only validates configured APIs — there is no visible code that performs scheduling or delivery wiring. Ask the publisher which component creates cron jobs and what exact changes the wizard will make. 3) Inspect the validate_setup.py file yourself (or in an isolated VM) before running; it will generate ~/.openclaw/config.yaml and read files under ~/.openclaw/keys, so ensure you understand what it will write. 4) Run the validation in a Python virtualenv with the listed requirements installed, and use --verbose or --kalshi-only to limit scope while you audit it. 5) Because the source/homepage are unknown, prefer to run this in an isolated environment or review the full repository (especially any code that would add cron entries, start services, or send messages) before providing private keys. If you rely on this for real trading, verify endpoints and credentials manually (Kalshi host, Anthropic model names) and back up existing ~/.openclaw/config.yaml before proceeding.

Type: OpenClaw Skill Name: prediction-stack-setup Version: 1.1.1 The Prediction Stack Setup bundle is a legitimate configuration utility designed to orchestrate a suite of prediction market trading skills. It includes a validation script (scripts/validate_setup.py) that tests API connectivity for services like Kalshi and Anthropic, and a comprehensive SKILL.md that guides the agent through setting up cron jobs and iMessage alerts. The code and instructions are transparent, follow the stated purpose of system automation, and do not exhibit signs of data exfiltration, unauthorized persistence, or malicious prompt injection.