Clawdbot Backup
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only backup skill, but it handles and can overwrite sensitive ClawdBot configuration, so backups and restores should be treated carefully.
Use this skill if you intentionally want to back up or restore ClawdBot state. Keep backup archives private, consider encryption, avoid public git remotes for backups that may include contexts or settings, and restore only archives you trust after previewing their contents.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Restoring an incorrect or untrusted backup could replace your skills, commands, MCP settings, or other ClawdBot behavior.
The documented restore command can replace existing files under the user's home directory, including ClawdBot skills and settings. This is disclosed and purpose-aligned, but it is a high-impact operation if the wrong archive is restored.
# Restore (will overwrite existing) ... tar -xzvf "$BACKUP_FILE" -C "$HOME"
Preview archive contents, restore only backups you trust, keep a separate current backup before restoring, and manually review changed skills/settings afterward.
Backup archives or git repositories may contain private conversation context, local settings, or integration configuration.
The backup scope includes persistent contexts, MCP configuration, and machine-specific settings. These are expected for a backup tool, but they may contain private data, tool configuration, or instructions that will later be restored and reused.
✓ ~/.claude/mcp/ # MCP configurations ... ✓ ~/.claude/contexts/ # Saved contexts ... .claude/settings.local.json
Store backups in a private location, consider encryption, avoid pushing sensitive backups to public repositories, and exclude machine-specific or secret-bearing files when they are not needed.
A problematic skill, setting, or MCP configuration could be copied across devices if included in a synced backup.
The skill is designed to propagate ClawdBot configuration across machines. This is core to the stated purpose, but a bad configuration or unsafe skill in a backup could be spread to other environments.
- Sync between multiple machines - Version control your configuration - Migrate to new devices
Review backups before syncing or restoring them on new machines, and test restored configurations in a low-risk environment when possible.