OpenClaw Backup

Backup OpenClaw data to desktop - quick backup (without skills, ~100MB) or full backup (with skills, ~500MB+). Supports scheduled automatic backups.

Security Scan

The skill's files and runtime instructions are consistent with a local backup/restore tool for OpenClaw; I did not find incoherent requests for unrelated credentials or hidden network exfiltration, though there are minor implementation and documentation issues you should be aware of.

Purpose & Capability

Name/description match what the files do: the scripts archive and extract ~/.openclaw data (optionally including skills). No unrelated credentials, binaries, or system paths are requested.

Instruction Scope

Runtime instructions and scripts limit actions to user home (~) and the .openclaw tree, create archives and restore them. Minor mismatches: SKILL.md / README claim 'Auto-Install' of OpenClaw but restore.sh only prompts the user and does not auto-install; Windows batch scripts are referenced in docs but are not present in the manifest; the tar size-estimation command produces inaccurate results (it will likely report 0). No instructions attempt to read or transmit unrelated system data.

Install Mechanism

No install spec — instruction-only with small shell scripts. Nothing is downloaded or extracted by the skill itself. The README suggests optional manual install steps (git/curl/npm) but those are standard and not automatically invoked by the provided scripts.

Credentials

No required env vars or credentials. The scripts optionally honor INCLUDE_SKILLS=1 to include installed skills; no other environment variables or secret access is requested or read.

Persistence & Privilege

Skill is not always-enabled and does not request elevated persistent privileges. It does not modify other skills or global agent configs. Scripts operate on user-owned files in the home directory only.

Assessment

This appears to be a straightforward local backup/restore tool — nevertheless: 1) Verify the skill's source before installing (registry shows unknown source; README references a GitHub repo — confirm that repo and checksums). 2) Inspect the scripts yourself before double-clicking or running them; they operate on ~/.openclaw and will move/replace data during restore. 3) Backups include encrypted credentials and (optionally) installed skills; store backup archives securely (encrypted at rest) and avoid placing them on untrusted cloud or shared drives. 4) Note mismatches: the README promises auto-install but the restore script only prompts (it will not automatically run npm install), and Windows batch files mentioned in docs are not included in the manifest. 5) If you rely on the size estimates, be aware the estimation code is buggy and may report 0 — do a test run. If you want higher assurance, obtain the package from a trusted upstream (official GitHub repo), verify signatures/checksums, and run the scripts in a safe environment first.

OpenClaw Backup Skill

快速使用 / Quick Start:

安装：安装 sen-openclaw-backup skill

备份：备份 OpenClaw 数据到桌面，快速备份（不含 skills，约 100MB）或完整备份（含 skills，约 500MB+），并设置每周自动备份

---

Backup and restore all OpenClaw data for migration or safekeeping.

What Gets Backed Up

Content	Description
workspace/	Project files, memory files, configurations
agents/	Conversation history and session data
memory/	Long-term memory embeddings
credentials/	Encrypted credentials
openclaw.json	Main configuration file
skills/	Installed skills (optional, large)

Quick Start

macOS / Linux

Backup:

# Quick backup (excludes skills, ~100MB)
./scripts/backup.sh /Volumes/YourSSD/backup.tar.gz

# Full backup (includes skills, ~500MB+)
INCLUDE_SKILLS=1 ./scripts/backup.sh /Volumes/YourSSD/backup.tar.gz

Restore:

./scripts/restore.sh /Volumes/YourSSD/backup.tar.gz

Windows

Backup:

# Quick backup
scripts\backup-windows.bat D:\backup.tar.gz

# Full backup with skills
set INCLUDE_SKILLS=1
scripts\backup-windows.bat D:\backup.tar.gz

Restore:

scripts\restore-windows.bat D:\backup.tar.gz

Scripts

backup.sh

Creates a compressed archive of OpenClaw data.

Environment Variables:

• INCLUDE_SKILLS=1 - Include skills directory (adds ~1.5GB)

Usage:

./scripts/backup.sh [output-path]

Examples:

# Backup to default location (Desktop with timestamp)
./scripts/backup.sh

# Backup to specific location
./scripts/backup.sh /Volumes/SSD/openclaw-backup.tar.gz

# Full backup with skills
INCLUDE_SKILLS=1 ./scripts/backup.sh /Volumes/SSD/openclaw-full.tar.gz

restore.sh (macOS/Linux)

Restores OpenClaw data from a backup archive.

Features:

• Automatically backs up existing data before overwriting
• Installs OpenClaw if not present
• Optionally syncs skills after restore

Usage:

./scripts/restore.sh <backup-file>

Examples:

./scripts/restore.sh /Volumes/SSD/openclaw-backup-20250318.tar.gz

backup-windows.bat / restore-windows.bat (Windows)

Windows batch scripts for backup and restore.

Requirements:

• Windows 10 version 17063 or later (for built-in tar support)
• Node.js and npm installed

Usage:

# Backup
scripts\backup-windows.bat D:\openclaw-backup.tar.gz

# Restore
scripts\restore-windows.bat D:\openclaw-backup.tar.gz

Migration Workflow

Old Machine

# 1. Run backup
./scripts/backup.sh /Volumes/SSD/openclaw-backup.tar.gz

# 2. Eject drive
diskutil eject /Volumes/SSD

New Machine

# 1. Install OpenClaw (if needed)
npm install -g openclaw@latest

# 2. Restore data
./scripts/restore.sh /Volumes/SSD/openclaw-backup.tar.gz

# 3. Start Gateway
openclaw gateway start

Portable Package / 便携包

For easy migration, use the portable ZIP package which includes:

• Data backup file
• One-click restore scripts for macOS and Windows
• Command-line backup/restore scripts
• Skill installation package

Changelog

v1.1.0

• Added portable ZIP package creation
• Improved Windows batch scripts
• Added bilingual README

v1.0.0

• Initial release
• Cross-platform backup and restore
• One-click restore scripts

Notes

• Backup files are gzip-compressed tar archives
• Existing data is preserved with .bak.<timestamp> suffix before restore
• Skills can be re-downloaded via clawhub sync if excluded from backup
• Configuration files may need adjustment if paths differ between machines