Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Gateway Health Monitor

v1.0.0

Monitor and auto-fix OpenClaw gateway stability issues. Diagnoses launchd throttling, plugin restart loops, hung shutdowns, and macOS power management interf...

0· 79·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jimmyclanker/gateway-health-monitor.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Gateway Health Monitor" (jimmyclanker/gateway-health-monitor) from ClawHub.
Skill page: https://clawhub.ai/jimmyclanker/gateway-health-monitor
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install gateway-health-monitor

ClawHub CLI

Package manager switcher

npx clawhub@latest install gateway-health-monitor
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (macOS gateway health fixes) aligns with the scripts' actions (diagnose, patch a gateway launchd plist, change reload mode). However the skill metadata claims no required binaries or config paths, while the scripts actually rely on launchctl, plutil, pmset (and call the openclaw CLI and python3). The omission of those required tools is an inconsistency.
!
Instruction Scope
SKILL.md directs running included shell scripts that read/writes files under $HOME (~/.openclaw/openclaw.json, ~/.openclaw/logs, ~/Library/LaunchAgents/ai.openclaw.gateway.plist), call launchctl and pmset (sudo for permanent pmset change), and will modify the gateway plist automatically. The instructions read and modify local configuration and logs beyond what the skill metadata declared — this is scope creep the user should be aware of.
Install Mechanism
There is no external install spec and all code is included in the package. No downloads from remote URLs or opaque installers are present, so nothing external will be written to disk beyond what these scripts create when run.
Credentials
The skill requests no credentials or environment variables (appropriate), but the scripts require system utilities (launchctl, plutil, pmset, python3, openclaw CLI) and will need permission to modify user LaunchAgents and to run sudo pmset. Those privilege requirements are not declared in the metadata.
!
Persistence & Privilege
Running install-patcher.sh will create and load a persistent user LaunchAgent (ai.openclaw.plist-patcher) that watches the gateway plist and automatically rewrites keys. This gives the skill ongoing, autonomous filesystem and launchctl influence in the user's account — expected for a patcher but a meaningful persistence capability that should be accepted explicitly by the user.
What to consider before installing
This skill appears to implement the described macOS fixes, but there are two issues you should consider before installing: (1) the package metadata omits required tools and the specific paths the scripts access — the scripts use launchctl, plutil, pmset, python3 and the openclaw CLI and read/write ~/.openclaw and ~/Library/LaunchAgents; (2) the installer creates a persistent per-user launchd agent that will automatically patch the gateway plist (and the instructions include a sudo pmset change). If you plan to install: review the included scripts line-by-line, back up ~/Library/LaunchAgents/ai.openclaw.gateway.plist and ~/.openclaw/openclaw.json, confirm you trust the skill source, and run the diagnostic scripts manually first (do not run install-patcher.sh until you're comfortable). If you prefer lower risk, run the scripts in a disposable account or macOS VM to observe behavior before enabling the persistent patcher.

Like a lobster shell, security has layers — review code before you run it.

latestvk977bczp66jf85w8ebrkqec1t583x98n
79downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0

Gateway Health Monitor

Diagnose and fix OpenClaw gateway stability issues on macOS. Covers the most common failure modes that cause extended downtime.

Quick Diagnosis

Run the diagnostic script:

bash scripts/diagnose.sh

This checks: process state, launchd classification, restart count, plist config, power management, and plugin resolve loops.

Common Failure Modes

1. Plugin Restart Loop (most common)

Symptoms: Gateway restarts every 5-7 minutes. Log shows restartReason=config.patch with plugins.installs.*.resolvedAt.

Cause: Plugins re-resolve on every boot → write new timestamps to openclaw.json → config watcher detects "change" → triggers deferred restart → SIGTERM → repeat.

Fix: Set gateway.reload.mode to "hot":

openclaw config set gateway.reload.mode '"hot"'

In hot mode, safe changes hot-apply instantly. Critical changes (like plugin timestamps) only log a warning — no auto-restart. This breaks the loop.

Verify: grep "reload" ~/.openclaw/logs/gateway.log | tail -5 should show config change applied (dynamic reads) instead of restart.

2. macOS Throttling ("inefficient" classification)

Symptoms: Gateway goes down and stays down for 30-60+ minutes. launchctl print shows immediate reason = inefficient.

Cause: After many restarts (10+/day), macOS marks the job as low-priority and delays restarts via App Nap / Power Nap logic.

Fix: Add these keys to the launchd plist (~/Library/LaunchAgents/ai.openclaw.gateway.plist):

<key>ProcessType</key>
<string>Interactive</string>
<key>LowPriorityBackgroundIO</key>
<false/>

Then reload:

launchctl bootout gui/$(id -u)/ai.openclaw.gateway
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist

Note: openclaw gateway start overwrites the plist. Use the patcher script (below) to auto-reapply.

3. Hung Shutdown

Symptoms: Gateway receives SIGTERM but doesn't exit. launchd can't restart because old PID still alive.

Fix: Set ExitTimeOut in the plist:

<key>ExitTimeOut</key>
<integer>10</integer>

After 10 seconds, launchd sends SIGKILL.

4. Power Nap Interference

Symptoms: Gateway goes down during Mac sleep/wake cycles.

Check: pmset -g | grep powernap

Fix: sudo pmset -a powernap 0

Plist Auto-Patcher

Since openclaw gateway start overwrites the plist, use scripts/patch-plist.sh as a launchd WatchPaths agent:

# Install the patcher
bash scripts/install-patcher.sh

This creates a launchd agent that watches the gateway plist and re-adds ExitTimeOut, ProcessType, and LowPriorityBackgroundIO within seconds of any overwrite.

Monitoring

One-liner health check

bash scripts/health-check.sh

Returns exit code 0 if healthy, 1 if issues detected. Suitable for cron or heartbeat integration.

Continuous monitoring (cron integration)

Add to your OpenClaw cron:

Check gateway health: bash ~/path/to/scripts/health-check.sh && echo "Gateway healthy" || echo "ALERT: Gateway issues detected"

Recommended Configuration

For maximum stability on macOS:

{
  gateway: {
    reload: { mode: "hot" },
  },
}

Plus plist keys: ExitTimeOut=10, ProcessType=Interactive, LowPriorityBackgroundIO=false, ThrottleInterval=1, KeepAlive=true.

Troubleshooting Reference

SymptomCheckFix
Restarts every 5-7 mingrep restartReason gateway.logreload.mode = "hot"
Down 30-60+ minlaunchctl print → "inefficient"ProcessType=Interactive
Won't exit on SIGTERMps -p PID after SIGTERMExitTimeOut=10
Down after sleeppmset -g | grep powernappmset -a powernap 0
Plugin timestamps changinggrep resolvedAt openclaw.jsonreload.mode = "hot"

Comments

Loading comments...