OpenClaw Backup

Backup OpenClaw workspace, config, and state using the built-in `openclaw backup create` command. Also handles cleanup of old backups and health verification...

This skill appears to do exactly what it says, but review these points before installing: - Confirm you trust the installed OpenClaw CLI binary on the machine: the scripts call only 'openclaw' — if that binary is malicious, any skill using it inherits that risk. - Backups include credentials, session history, and workspace files. Even if OpenClaw encrypts credentials, store the ~/openclaw_backups/ directory securely and consider additional encryption if you will copy archives off-machine. - The skill supports overriding the backup directory via OPENCLAW_BACKUP_DIR (not listed in registry metadata). If you want backups elsewhere, set that env var before running. - Cron creation is expected behavior, but verify the cron entry after setup (openclaw cron list) so you know what was added and can remove it if unwanted. - Run the scripts manually first (use --dry-run and --verify) to inspect outputs before enabling automated scheduling. - Small implementation quirks exist (e.g., cleanup script argument handling is confusing), but they look like bugs rather than malicious behavior. If you want additional assurance, inspect the 'openclaw' CLI on your system, run the scripts in dry-run mode, and verify archives are created and stored where you expect before enabling the cron job.