Usage instructions
Core usage
clawdbot-backup is a complete ClawdBot configuration backup solution that provides three core backup modes: full backup (skills/commands/settings/mcp/contexts/templates), skills-only backup, and settings-only backup. Users can create time-stamped local backups through tar archives, use Git for version control and cloud synchronization, and use rsync to synchronize configurations across multiple devices in real time.
Significant advantages
1. Multi-dimensional backup strategy: Support full/incremental/selective backup and flexibly respond to the needs of different scenarios
2. Official ecological integration: Deeply adapted to the ClawdBot directory structure (~/.claude/), accurately identifying key configurations and excludeable items
3. Complete automation support: Provides three timing solutions: cron, systemd timer, and launchd to achieve unattended backup
4. Smooth migration experience: The migration process of old and new devices is documented and supports dual-channel recovery from backup files or Git repositories.
5. Security confirmation mechanism: Force the user to confirm before restoring the operation to avoid accidental overwriting.
Potential Disadvantages and Limitations
1. No encryption mechanism: The backup file is stored in clear text tar, and sensitive configurations need to be encrypted by the user.
2. Git learning cost: The version control function requires users to have basic Git knowledge
3. Cross-platform differences: The Windows environment requires additional configuration of WSL or Git Bash to fully run the bash script.
4. No incremental backup optimization: Each tar backup is fully packaged and may take up more storage space for long-term operation.
5. Rely on external tools: Need to pre-install git, tar, rsync, some streamlined systems may be missing
Suitable target group
- Developers and power users using ClawdBot across multiple devices
- Technical teams who need custom skills in version management
- Users who value the security of configured assets and have regular backup habits
- Engineers who frequently reinstall systems or change working machines
Risks of use
1. storage risk: The backup directory is located in ~/clawdbot-backups/ by default. If it is in the same partition as the system disk, source data and backup may be lost at the same time when the disk fails.
2. Git leak risk: The user mistakenly pushed the configuration containing sensitive information to the public warehouse.
3. rsync misoperation: Improper configuration of the --delete parameter may cause cloud data to be overwritten by local empty directories.
4. Recovery coverage risk: Interaction confirmation may be bypassed in batch automation scripts despite confirmation prompt
5. Path hardcoded: Some paths in the script are hard-coded as /home/user and need to be manually modified to the actual user name.
Safety review
Core usage
ClawdBot Backup Skill is a complete configuration backup and migration solution that provides three main usage modes:
1. tar archive backup: Use standard Linux tools (tar, rsync) to create compressed backup packages, supporting three granularities of full volume, skills only, and settings only.
2. Git version control: Incorporate the ~/.claude/ directory into Git management to achieve change tracking, branch collaboration and remote synchronization
3. Cloud synchronization solution: Real-time synchronization of multiple devices via rsync or cloud storage folders
Key directory structure:
~/.claude/skills/— Custom skills (core assets)~/.claude/commands/— Custom slash command~/.claude/settings.json— Global configuration~/.claude/mcp/— MCP server configuration~/.claude/contexts/, templates/ — saved contexts and templates
Significant advantages
- Zero dependency pure documentation: Skill itself does not contain executable code. All operations are bash examples actively executed by users, which are completely transparent and controllable.
- Multiple backup strategies: Supports three complementary solutions: local archiving, Git versioning, and cloud synchronization to meet different security needs
- Automation integration: Provide three scheduled backup configurations: cron, systemd timer, and launchd to achieve unattended operation
- Migration friendly: Complete migration between old and new devices can be completed through a single tar command or git clone
- Backup verification mechanism: Built-in integrity check (tar -tzvf) and difference comparison (diff -rq) process
potential limitations
- No incremental backup: tar archives as full snapshots, frequent backups may produce redundant storage
- Local execution dependencies: All scripts require users to manually save and authorize them, and lack a one-click installation mechanism.
- No encryption function: Backup files are not encrypted by default, and sensitive configurations need to be handled by the user (such as git-crypt)
- T3 Source Trust: Community project maintenance, not officially endorsed by Anthropic/ClawdBot
Suitable for the crowd
- Developers using ClawdBot across multiple devices
- Technical teams who need to version manage AI configurations
- Heavy users who frequently customize skills and worry about losing configurations
- Privacy-sensitive users who pursue data sovereignty and prefer local backup
General risks
|Risk point|grade|illustrate|
|--------|------|------|
|Backup contains sensitive configuration|Low|settings.local.json may contain API keys. It is recommended that Git ignore it but tar will still package it.|
|Restoration operation overwrites existing configuration|Low|The document already requires a confirmation prompt, but user misoperation may still result in data loss.|
|Community source updates lag|Low|For T3 level projects, it is recommended to pay attention to GitHub warehouse updates|
Security Certification Key Points
The static analysis score is 88 points, the dynamic behavior score is 90 points, and the dependency audit score is 95 points. There is no third-party dependency and no network leakage behavior. The overall evaluation is A level (85 points). The only caveat is that the Skill needs to read the ~/.claude/ directory, but this is a necessary permission for the backup functionality.
devopsautomationgitproductivitydevelopment-engineering
Copyright and takedown notice: AI Islands curates this page from public information. Skills, code, documents and packages remain the property of their original authors or rights holders. This listing is provided for indexing, research and installation convenience. If you believe any listing or download link infringes your rights, contact ai-islands@streamflowintel.com with proof of ownership, relevant URLs and your request. We will review and remove or adjust the content promptly. Review package permissions, dependencies and safety risks before installing.