SeeSaw Claw

Integrates SeeSaw prediction market APIs into OpenClaw, enabling market listing, balance checking, and position management via CLI.

Before installing or enabling automation, review these points: - Metadata mismatch: The registry summary here claimed no required env vars, but the SKILL.md and code require SEESAW_BASE_URL, SEESAW_API_KEY, and SEESAW_API_SECRET. In addition, automation scripts need OPENAI_API_KEY, SLACK_BOT_TOKEN (and channel ID), and BRAVE_API_KEY. Ask the publisher to correct registry metadata so required secrets are explicit. - Sensitive actions: The scripts can automatically create markets, assert resolutions, claim rewards, and buy/sell positions using your SeeSaw credentials. If you supply SEESAW API keys you are giving the skill permission to perform financial operations. Only provide those keys if you fully trust the code and the publisher. - Optional automation: If you only want read-only capabilities (list markets, check balances), run the CLI scripts manually and avoid providing the extra automation keys (OPENAI/Slack/Brave). Use the config dry_run=true to simulate actions while evaluating behavior. - Inspect utils.py and networking: The skill calls helper functions (search_web, call_llm, send_slack_message, search_image). Review utils.py to confirm those helpers do not exfiltrate credentials or post data to unexpected endpoints. Ensure SLACK and LLM interactions are to endpoints you expect. - Limit exposure: 1) Run first in an isolated account with minimal funds or sandbox API keys. 2) Do not enable autonomous invocation if you don’t want the agent to trade or create markets automatically. 3) Consider running on a machine/account where you can control /tmp and the skill workspace and review any files it writes. - Trust and provenance: The skill's source is listed as "unknown" and there is no homepage in the registry metadata. Confirm the publisher identity and, if possible, prefer installing from a verified repository (or clone and manually audit the code) before adding your credentials. If you want, I can: 1) summarize which exact files reference each sensitive env var, 2) highlight the lines where remote write operations (trade/claim/assert/create_market) occur, or 3) inspect utils.py for network/callback behavior — tell me which you'd like to see.

Type: OpenClaw Skill Name: seesaw-claw Version: 1.0.0 The skill bundle is a legitimate automation suite for the SeeSaw prediction market, providing a CLI client (`seesaw.py`) and several scripts for automated trading and market management. It utilizes external APIs for web searching (Brave), LLM analysis (Gemini), and notifications (Slack) to perform tasks like generating new market topics, adjusting positions based on news, and asserting market results. While it contains some hardcoded identifiers (e.g., `MY_CREATOR_ID` in `auto_assert.py`) and stores session tokens in `/tmp/seesaw_token.json`, these appear to be functional choices or minor security flaws rather than evidence of malicious intent.