Openclaw Backup Optimized

Optimized OpenClaw backup skill for creating full snapshots with workspace archive splitting, change summaries, restore instructions, and Discord notifications. Use when you need to set up or run automated backups, configure backup cron jobs, or document/restore OpenClaw state. Triggers on backup automation, backup scripts, snapshot/restore, or GitHub backup repos.

This skill is what it claims to be: a backup script for your OpenClaw home. Before installing or scheduling it, review the script (scripts/backup.js) yourself and confirm you are comfortable with what will be copied. Pay special attention to BACKUP_REPO_URL: if you set it, the script will git push (force) the backup contents to that remote — only use a trusted, private repository. Also verify BACKUP_CHANNEL_ID because notifications go through the OpenClaw gateway (openclaw message send). Run the script manually once, inspect the generated backup directory (~/.openclaw-backup by default) and backup-report.json, and ensure any git credentials and remote settings are intentional before enabling the cron entry.

Type: OpenClaw Skill Name: openclaw-backup-optimized Version: 1.0.1 The skill is designed to back up the entire OpenClaw home directory (`~/.openclaw`) and push it to a user-configured Git repository (`BACKUP_REPO_URL`) using `git push --force`. While this aligns with the stated purpose of a backup skill, it involves handling highly sensitive data and exfiltrating it to an external endpoint, which, if misconfigured or pointed to a malicious repository, could lead to data theft or loss. The use of `git push --force` is a powerful and potentially destructive operation. These capabilities, though plausibly needed for a backup, are high-risk and warrant a 'suspicious' classification due to the potential for misuse or unintended consequences, as seen in `scripts/backup.js` and `SKILL.md`.