Clawdbot Backup

**Judgement:** A robust, well-documented backup and sync toolkit for ClawdBot power users on Unix-like systems, suitable as a primary backup solution for most non-Windows setups. **Strengths:** - Covers full and partial backups, restore, sync (git/rsync/cloud), and migration in depth. - Provides concrete Bash scripts and scheduler integrations (cron, systemd, launchd) rather than vague instructions. - Includes verification, integrity checks, and troubleshooting guidance, which many backup tools omit. **Key Risks / Limitations:** - Unix-centric: assumes a POSIX shell with tools like `tar`, `rsync`, `cron`, etc.; Windows users will need WSL or equivalent. - Restore operations overwrite existing configs and rely on user confirmation; misuse could cause configuration loss if pointed at the wrong target. - Git-based backup can unintentionally expose sensitive config if users store secret material under `~/.claude` and don’t refine `.gitignore`. - Some `tar` calls use `|| true`, which can hide non-critical errors and may lead to partially incomplete backups without obvious failure signals. **Recommended Scenarios:** - You heavily customize ClawdBot (skills, MCP servers, commands) and want reliable, scriptable backups. - You work across multiple Unix-like machines and need a repeatable way to sync or migrate your ClawdBot environment. - You want to integrate ClawdBot config backups into an existing devops/tooling setup using cron, systemd, or git-based workflows. - You need shareable skill bundles (for collaborators or open-source) while keeping personal settings out of the shared artifacts.