Gateway Monitor Auto Restart

Monitors OpenClaw gateway every 3 hours, auto-restarts if unresponsive, diagnoses startup issues, and rotates logs with 7-day retention.

Security Scan

The skill's code and instructions are consistent with its stated purpose (monitor and restart the OpenClaw gateway); it modifies crontab and manipulates local services but does not appear to contact external endpoints or request unrelated credentials.

Purpose & 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.

Gateway Monitor Auto-Restart Skill

Automatically monitors the OpenClaw gateway status and restarts it if it becomes unresponsive. Features 3-hour checks, smart restart logic, issue diagnosis, and 7-day log rotation.

Description

This skill provides comprehensive monitoring for the OpenClaw gateway with automatic restart capabilities. It includes:

• Health checks every 3 hours
• Smart restart mechanism when gateway is down
• Issue diagnosis when startup fails
• 7-day log rotation system
• Fast recovery system that prioritizes quick gateway restart

Features

• Automatic Monitoring: Checks gateway status every 3 hours
• Smart Restart: Restarts gateway when it becomes unresponsive
• Issue Diagnosis: Identifies and reports startup issues
• Fast Recovery: Prioritizes quick gateway restart
• Log Management: Maintains logs with 7-day rotation
• Error Handling: Gracefully handles "already running" errors

Usage

The skill automatically sets up a cron job that runs the monitoring script every 3 hours. The monitoring system will:

1. Check if the gateway is responsive
2. If unresponsive, attempt to restart it
3. If restart fails, diagnose the issue
4. Log all activities with timestamp
5. Rotate logs older than 7 days

Requirements

• OpenClaw gateway installed and configured
• Proper permissions to manage gateway service
• Cron access for scheduling checks

Configuration

No additional configuration required. The skill automatically installs the monitoring system with optimal settings.