Gateway Auto-Fix
v2.0.0Automatically monitor OpenClaw gateway status and fix when RPC probe fails. Uses OpenClaw cron system - just install and it works!
⭐ 0· 477·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description align with what the scripts and SKILL.md do: they check 'openclaw gateway status', detect the 'RPC probe: failed' string, run 'openclaw doctor --fix' and 'openclaw gateway restart', add an OpenClaw cron job, and log to /tmp. No unrelated services, credentials, or binaries are required.
Instruction Scope
All runtime instructions and the included scripts stay within the stated purpose (monitoring and remediation). However, the skill performs automated corrective actions (doctor --fix and gateway restart) without human approval; this is functionally appropriate but can cause operational disruption if mis-triggered. The scripts write logs to /tmp and create ~/.openclaw-it/workspace/openclaw-auto-fix.sh as described.
Install Mechanism
No install spec; the package is instruction-only and includes setup.sh and the main script. setup.sh writes the script to the user's home workspace and adds an OpenClaw cron job. There are no downloads from external URLs or archive extraction steps.
Credentials
The skill requires no environment variables or external credentials. It only depends on the presence of the OpenClaw CLI and its cron subsystem, which is consistent with the stated goal.
Persistence & Privilege
The skill installs an OpenClaw cron job that runs every 1 minute — this gives it frequent, persistent execution but not 'always: true' or elevated system-wide privileges. Frequent automatic remediation is expected for the use case but could be aggressive; the skill does not alter other skills' configs or request broader privileges.
Assessment
This skill appears to do what it says: monitor the OpenClaw gateway and run fixes automatically. Before installing, review the included scripts yourself and consider: (1) the scripts run 'openclaw doctor --fix' and 'openclaw gateway restart' automatically — this can change configuration and cause service restarts, so test in staging first; (2) the cron runs every minute (adjust if too aggressive); (3) logs are written to /tmp (a world-writable directory) — if the cron runs as a privileged account, consider changing the log path or ensuring permissions to avoid symlink attacks; (4) ensure the OpenClaw CLI is the expected binary on PATH and that you trust it; (5) you can install manually by copying the script and adding the cron, or run setup.sh and inspect its actions. If any of these are concerning, do not install until you can validate behavior in a safe environment.Like a lobster shell, security has layers — review code before you run it.
auto-fixvk973ym5sdvrp0qtva1rac275a1821f4bcronvk973ym5sdvrp0qtva1rac275a1821f4bgatewayvk973ym5sdvrp0qtva1rac275a1821f4blatestvk973ym5sdvrp0qtva1rac275a1821f4bopenclawvk973ym5sdvrp0qtva1rac275a1821f4b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.