Openclaw Backup Skill

Run and schedule local OpenClaw backup operations with a bundled Bash script. Use when the user wants to create, prune, or automate local OpenClaw backups, i...

This skill appears to be a straightforward local backup/prune script for OpenClaw. Before installing or running it, review and consider the following: - The script will archive workspace contents including assistant identity/continuity files (SOUL.md, AGENTS.md, USER.md). Those files can contain sensitive context — ensure you are comfortable storing them in the chosen backup directory and that the directory has appropriate filesystem permissions and backups are stored securely. - Ensure the target host has the OpenClaw CLI, python3, tar, and other standard utilities the script expects; the registry metadata did not list these requirements, so verify them manually (SKILL.md and the script list the required commands). - The skill is local-only (no uploader) based on the provided files, but you should still scan the full script for any network or external command usage if you have security requirements; the provided content shows no network calls, but the script was truncated in the listing—review the entire script before running it. - When automating (cron/systemd), ask the user for explicit permission before creating or modifying scheduled jobs or automated runs, and choose a secure output directory (default is next to the resolved OpenClaw state dir, e.g., ~/backups/openclaw). - If you need to avoid including identity/continuity files in backups, either modify the script (or ask the user) to exclude them or test dry-run modes first to verify the manifest contents.

Type: OpenClaw Skill Name: openclaw-backup-skill Version: 0.2.2 The skill bundle provides a legitimate utility for creating and managing local OpenClaw backups. The primary script, `scripts/openclaw-backup.sh`, follows security best practices by setting a restrictive umask (077), failing on errors, and explicitly excluding sensitive environment variables and system override files from the backup archives. The logic for retention and pruning is transparently implemented using localized Python helpers for safe date and JSON processing, and there is no evidence of data exfiltration, obfuscation, or unauthorized persistence.