Polymarket Verify

Verify Polymarket MR-V4 trading system deployment health. Use when asked to check trader processes, verify deployment, audit 韭菜王's changes, or after any stra...

Security Scan

The skill's code and instructions align with its stated purpose (local deployment health checks); it reads local process state and files but does not contact external endpoints or request credentials.

Purpose & Capability

The name/description match the actual behavior: the script checks processes, lock files, config, logs, and a PID file to verify a local MR-V4 deployment. The checks (ps, lsof, config.json, trades.jsonl, collector.pid) are coherent with verifying deployment health.

Instruction Scope

SKILL.md instructs running a local script at an absolute user-specific path (/Users/0xbobby/...). The script reads local files and process metadata (uses ps, lsof, stat, python3, kill -0) which is expected for this purpose. It does not perform network calls or exfiltrate data, but it does access potentially sensitive local config/log files and process information.

Install Mechanism

Instruction-only skill with a bundled script and no install spec. Nothing is downloaded or written by an installer, so install risk is minimal.

Credentials

No environment variables or credentials are requested. However the script assumes access to the user's workspace path and standard system tooling (lsof, ps, python3, flock/stat utilities). It also reads config.json, logs, and a collector.pid — access to these local files is necessary for the checks but may expose sensitive deployment data.

Persistence & Privilege

always is false and the skill does not attempt to modify other skills or system-wide configs. It only reads local state and exits with a non-zero code on failures.

Assessment

This skill appears to do exactly what it says: run a local health-check script for the MR-V4 deployment. Before installing or running it, be aware that it will read local deployment files (config.json, logs, lock and pid files) and query process state (ps, lsof). It does not request credentials or call external services, but those local files can contain sensitive data — review the script yourself and confirm the BASE path matches your environment (the SKILL.md and script use a hardcoded /Users/0xbobby/... path). If you intend to run this on a different host/user, update BASE or run it in a safe/test environment first. If you don't trust the origin, inspect the script for any modifications before execution.

Polymarket Deployment Verification

One-command verification of the MR-V4 trading system.

Usage

Run the check script:

bash /Users/0xbobby/.openclaw/workspace/skills/polymarket-verify/scripts/verify.sh

What It Checks

1. Process count — exactly 3 trader processes (V4 LIVE + 2 sims)
2. No duplicate processes — each directory has at most 1 trader
3. V4 flock protection — lock file is held by running process
4. Config validation — dry_run, max_entries, hedge_size match expected values
5. Trade activity — trades.jsonl has recent writes (within 2 hours)
6. Sim-trader isolation — sim processes running from sim-trader/ directory, not CLI
7. Cron health — guardian cron (980acb62) and hourly report (4ddfd61a) have no consecutive errors
8. Data collector — DC process alive and writing tick data

Output Format

✅ PASS: [check name] — [detail]
❌ FAIL: [check name] — [detail]
⚠️ WARN: [check name] — [detail]

Summary: X/Y checks passed

When to Use

• After any strategy deployment or config change
• When Bobby asks to verify 韭菜王's work
• Automatically from guardian cron (optional)
• After process restarts or Gateway restarts