Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Gateway Monitor Auto Restart
v1.0.1Monitors OpenClaw gateway every 3 hours, auto-restarts if unresponsive, diagnoses startup issues, and rotates logs with 7-day retention.
⭐ 1· 1.7k·3 current·3 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/description (monitor + auto-restart gateway) matches the included scripts: gateway_monitor.sh performs health checks, restart attempts, diagnosis, and log rotation; setup.sh installs a cron job. The requested capabilities (managing gateway service, cron access) are proportionate to the purpose.
Instruction Scope
SKILL.md and setup.sh instruct the agent/user to create a cron job and run gateway_monitor.sh which runs openclaw CLI commands, pgrep/pkill, lsof, and launchctl. These operations are appropriate for restarting/diagnosing a local gateway, but they do require permission to manage services and will inspect/kill local processes and ports — this is scope-appropriate but intrusive for a monitoring script.
Install Mechanism
There is no remote install/download; the package is instruction- and script-based. setup.sh makes the monitor executable, creates a log directory, and writes a cron entry. No external URLs or extracted archives are used.
Credentials
The skill requests no environment variables or external credentials (good). However it does require system permissions to manage the gateway service and install cron jobs. Those privileges are necessary for its function but worth noting because the scripts run commands that affect local services and processes.
Persistence & Privilege
The skill persists by adding a cron job (runs every 3 hours) and writes logs under $HOME/.openclaw/logs. It does not set always: true. The cron entry is persistent across reboots and will continue to run until removed; that persistent presence is expected for a monitor but is a notable permission/persistence action.
Assessment
This skill appears to do what it claims, but it makes persistent, local changes and performs intrusive actions on local processes. Before installing: 1) Inspect the scripts (gateway_monitor.sh and setup.sh) yourself; 2) Run setup.sh from the directory where the scripts will remain (setup embeds the current working directory into the cron job); 3) Backup your current crontab (crontab -l > crontab.bak) so you can revert; 4) Ensure you have the OpenClaw CLI available and understand the permissions required — the script uses pkill, launchctl and other commands that will affect local processes and ports; 5) If you later uninstall, remove the cron entry and the created log files. If you are uncomfortable granting those local privileges or want more control, consider running the monitor manually or converting it to a systemd/managed service with explicit paths and privileges.Like a lobster shell, security has layers — review code before you run it.
latestvk97fkjpr78yqpx6js5h03tnphs80jvqj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.