Config Guard
ReviewAudited by ClawScan on May 10, 2026.
Overview
Config Guard is a local rollback helper, but its watchdog can overwrite your OpenClaw config and force-restart the Gateway on any failed status check rather than a clearly bounded 10-second edit window.
Review this carefully before installing. It is purpose-aligned as a rollback helper, but it can change your OpenClaw configuration and force-restart Gateway automatically. Prefer running it manually after making a backup, and avoid background scheduling unless you are comfortable with automatic rollbacks on Gateway status failures.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A transient status failure or mistaken invocation could replace your current OpenClaw configuration and restart the Gateway, potentially disrupting agent behavior or reverting intentional changes.
A single failed Gateway status check causes the script to overwrite the active OpenClaw configuration and force-restart the Gateway, with no shown user approval or guard tying the action to a specific 10-second post-edit rollback window.
if ! openclaw gateway status --json | grep -q '"state": "active"'; then ... cp "$LATEST_BACKUP" "$CONFIG_FILE" ... openclaw gateway restart --force
Use this only when you intentionally want rollback protection. The author should add explicit confirmation or a documented background-mode opt-in, retry/wait logic, a guard file or timestamp proving a recent edit, backup validation, and a dry-run/log-only mode.
Installation and runtime expectations are less transparent; the skill may fail or behave unexpectedly if the OpenClaw CLI is unavailable or different from expected.
The provided code is inspectable, but provenance is limited and the metadata does not declare the openclaw CLI dependency that the script uses.
Source: unknown; Homepage: none; Required binaries (all must exist): none
Declare the OpenClaw CLI and relevant ~/.openclaw paths in metadata, and provide a source repository or homepage for provenance.
If configured to run in the background, it may continue rolling back and restarting Gateway outside the immediate task unless the user stops it.
Background watchdog behavior is disclosed, but no persistence mechanism is included in the artifacts; if a user schedules it, it can keep acting autonomously.
The skill primarily runs as a background watchdog.
Keep it manual unless you explicitly want background monitoring, and ensure any scheduler has clear start/stop controls and logging.