OpenClaw Configuration Management & Emergency Recovery

OpenClaw Configuration Management & Emergency Recovery — configuration, skills, and projects snapshot &recovery for OpenClaw. Use this skill whenever the use...

This skill appears to do exactly what it claims: local snapshots and restores of OpenClaw config, skills, and projects with a config-only dead-man's-switch. Before installing or running it, do the following: - Manually review the restore.mjs and the startup hook (hooks/watchdog-recovery/handler.ts) to confirm they only restore the config subsystem automatically (skills and projects are manual). The SKILL.md asserts only config is auto-restored — verify the code matches that. - Run the included 'recovery-test.mjs preflight' to ensure the environment is ready and that the restart command was detected correctly. The detect-restart-command.mjs prints PID 1 cmdline fragments when probing containers; inspect its output to avoid accidentally committing sensitive command-line details to logs. - Be aware restores extract tar.gz archives using absolute paths (archives are extracted to /). That is necessary for restoration but can overwrite files; take an independent manual backup of critical data before testing destructive operations (the tool provides save-recovery for this purpose). - The 'sabotage' test intentionally poisons openclaw.json (but keeps JSON valid) to simulate logical failures — run it only in a controlled/test environment after saving a recovery copy. - Confirm you trust the skill's source and review the scripts that spawn detached processes (watchdog-timer) and run exec/pgrep/pkill; these actions require filesystem and process privileges and will be local-only in the code you provided. If you are not comfortable with automated local restores that run at startup, do not arm the watchdog or avoid installing the startup hook until you have audited the hook code and practiced manual restores.

Type: OpenClaw Skill Name: openclaw-recovery-manager Version: 1.0.1 The skill implements a comprehensive recovery and 'dead-man's-switch' watchdog system for OpenClaw. It employs high-risk operations, specifically extracting tar archives to the root directory (`tar -xzf ... -C /`) in `scripts/restore.mjs` and `scripts/skills-restore.mjs` to restore files to their absolute paths. It also installs a persistence mechanism via a native OpenClaw startup hook (`hooks/watchdog-recovery/handler.ts`) to automate restoration or timer re-arming upon gateway restart. While these capabilities are logically consistent with the stated goal of emergency system recovery and the code explicitly avoids backing up sensitive credential files (e.g., `auth-profiles.json`), the combination of root-level file system writes and automated execution on startup represents a significant security risk.