OpenClaw Safe Change Flow

Safe OpenClaw config change workflow with backup, minimal edits, validation, health checks, and rollback. Single-instance first; secondary instance optional.

This skill is coherent and appears to do what it says, but take these precautions before installing/using it: (1) Verify you have the OpenClaw CLI on PATH (openclaw status/gateway commands) because the script assumes it. (2) Inspect any edit scripts (edit-main.sh / edit-secondary.sh / underlying python scripts) before running — safe-change.sh will execute them with bash, so they can run arbitrary commands. (3) If you enable secondary checks, provide SECONDARY_TOKEN only when needed and keep it secret. (4) Be aware the script will restart the OpenClaw gateway and may call launchctl on macOS; run this in a maintenance window if production impact is possible. (5) Confirm backups are created in the expected path and test the rollback path in a safe environment before using in production.

Type: OpenClaw Skill Name: openclaw-safe-change-flow Version: 1.1.0 The skill bundle provides a legitimate safety-oriented workflow for managing OpenClaw configuration changes. It includes a bash script (safe-change.sh) that implements a robust backup-validate-rollback pattern and instructions (SKILL.md) that guide the AI agent to use this safer method instead of direct file edits. The code uses standard practices like 'set -euo pipefail' and timestamped backups, and there is no evidence of data exfiltration, credential theft, or malicious intent.