clawdbot-backup

What This Skill Does

The clawdbot-backup skill is an essential utility designed to provide data sovereignty for your OpenClaw environment. It centralizes the protection of your custom AI agent configurations, including complex skill sets, personal command structures, and MCP server integrations. By standardizing the backup process, the tool ensures that the effort you have invested in tailoring your AI assistant is never lost due to system failures or hardware migrations. The skill facilitates both ad-hoc manual backups and systematic snapshots, effectively serving as a version-control-friendly interface for your configuration files. It handles the mapping of the ~/.claude/ directory, ensuring that your global settings, project-specific overrides, and custom templates are captured in a portable, compressed format.

Installation

To add this capability to your instance, run the following command in your terminal:

clawhub install openclaw/skills/skills/sebastian-buitrag0/clawdbot-backup

Once installed, verify the configuration path matches your current system setup to ensure that the backup scripts correctly target your active environment.

Use Cases

1. Hardware Migration: Seamlessly transfer your entire AI workflow from an old machine to a new workstation without reconfiguring MCP servers or re-downloading skills.
2. Configuration Version Control: Periodically export your settings into a repository, allowing you to track changes in your agent behavior over time and roll back if a specific configuration causes performance regressions.
3. Syncing Across Environments: Maintain consistent behavior between development, testing, and production environments by deploying your verified ~/.claude directory snapshots.

Example Prompts

1. "Clawdbot, run a full backup of my configuration and save it to my external drive under the backups folder."
2. "I just finished customizing my new skills. Please create a skills-only backup and name it with today's date."
3. "Restore my configuration from the backup file created last Tuesday to reset my settings to that previous state."

Tips & Limitations

• Safety: Always verify the contents of a backup archive using the provided preview command before performing a full restore to avoid overwriting recent important changes.
• Automation: Consider adding the provided bash scripts to a cron job for automated daily or weekly backups to ensure you never lose data due to user forgetfulness.
• Storage: While the tool handles your configuration, it does not backup your actual project source code, which should be managed via Git. Ensure you follow the file structure guidelines to keep your backup archives lightweight and manageable.