首页 › 龙虾技能列表 › OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. — 技能工具

OpenClaw backup and synchronization tool - Pack, upload, download, and restore. Save the Soul of your OpenClaw. — 技能工具

v0.1.5

[自动翻译] Backup, clone, and migrate OpenClaw data across instances. Upload/download OpenClaw snapshots to local or cloud - https://clawclone.cc . Create sharea...

1· 222·1 当前·1 累计
by @clawclone-cc·MIT-0
下载技能包
License
MIT-0
最后更新
2026/4/9
安全扫描
VirusTotal
可疑
查看报告
OpenClaw
安全
medium confidence
The skill's files, commands, and permissions are coherent with a backup/clone tool for OpenClaw, but there are privacy-sensitive behaviors (preserving and uploading tokens) and an unknown source that warrant caution before using cloud features.
评估建议
This skill appears to do what it says (backup, local export/import, and cloud sync). Before using cloud features or running the bundled JS, review the bundled clawclone.mjs for network calls and hardcoded endpoints (look for fetch/axios/https.request and domains beyond clawclone.cc). Be aware that by default it preserves and may upload API keys and 'gateway tokens' — if you have secrets you do not want uploaded, use local export/verify/import workflows instead. Because the package source/homepag...
详细分析 ▾
✓ 用途与能力
Name, description, declared required binaries (node, tar, npm), and declared permissions (read/write ~/.openclaw, network: https) match the behaviors you would expect from a backup/restore and cloud-sync CLI.
ℹ 指令范围
SKILL.md limits actions to backing up/restoring ~/.openclaw and local files and describes cloud push/list/clone/share operations. It explicitly preserves 'gateway tokens' and other API keys by default, which is functionally consistent with a full-state backup but increases sensitivity — users should expect these secrets may be uploaded when using cloud features. The instructions also refer to an environment variable (CLAWCLONE_API_KEY) even though the registry metadata lists no required env vars.
ℹ 安装机制
No external install spec (instruction-only) and the package bundles a large clawclone.mjs file (vendorized Node code). There are no downloads from arbitrary URLs in the manifest, which reduces supply-chain risk, but the large embedded JS means you should inspect the file for unexpected network endpoints or telemetry before running.
ℹ 凭证需求
No environment variables are declared as required in registry metadata, but SKILL.md instructs users to set CLAWCLONE_API_KEY for cloud features. Requiring an API key for cloud operations is proportionate, but explicit handling/preservation of other API keys and 'gateway tokens' makes the tool capable of exfiltrating sensitive credentials if used with cloud upload — this is expected for a full backup tool but is security-sensitive.
✓ 持久化与权限
The skill is not always-enabled and does not request elevated platform presence. It writes backups under ~/.openclaw/backup which is appropriate for its purpose and does not claim to modify other skills or global agent settings.
安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

运行时依赖

无特殊依赖

版本

latestv0.1.52026/3/15

- Added a "Then" section notifying users they can visit https://clawclone.cc to view and manage their backed up OpenClaw souls. - No other changes to commands, features, or workflows.

● 可疑

安装命令 点击复制

官方npx clawhub@latest install clawclone
镜像加速npx clawhub@latest install clawclone --registry https://cn.clawhub-mirror.com

技能文档

Backup, clone, store, and migrate your OpenClaw workspace configurations.

Install

If the environment does not have the clawclone skill, use clawhub install clawclone to install it.

What Gets Backed Up

ComponentDetails
OpenClaw DataMEMORY.md, skills, agent files, configurations
SettingsAgent preferences and custom settings
FilesUser data and OpenClaw artifacts
ConfigOptional: API keys and tokens (if configured)
Backup Location: ~/.openclaw/backup

Dependencies

Requires: node (v16+), tar, npm (all standard on OpenClaw instances).

Check: which node tar npm

Prerequisites

Before using cloud features, verify the environment variable is set:

# Check if CLAWCLONE_API_KEY is set
echo $CLAWCLONE_API_KEY

If empty or not set, ask the user to get their ClawClone API key at https://clawclone.cc/dashboard/settings, and export:

export CLAWCLONE_API_KEY="your_api_key"

Note: Local operations work without API key.

Commands

Push to Cloud

# Push local workspace to cloud
node clawclone.mjs push --name "My Agent" --description "Production config"
# List all cloud backups
node clawclone.mjs list
# Show backup details
node clawclone.mjs show 
# Delete a cloud backup
node clawclone.mjs delete  --yes

Clone from Backup

# Clone (download and restore)
node clawclone.mjs clone 
# Preview changes first (recommended)
node clawclone.mjs clone  --test

Test mode generates a detailed report showing:

  • Backup metadata (name, version, creation date)
  • Components that will be modified (workspace, config, skills, etc.)
  • File counts and sizes for each component
  • No actual changes are made to your system

Local Operations

# Export to local file (no upload)
node clawclone.mjs local export --name "Local Backup" --output ./backup.tar.gz
# Import from local file
node clawclone.mjs local import --input ./backup.tar.gz
# Preview local import first
node clawclone.mjs local import --input ./backup.tar.gz --test
# Verify a backup file
node clawclone.mjs local verify ./backup.tar.gz

Share Backups

# Create a share link
node clawclone.mjs share create 
# Check share status
node clawclone.mjs share status 
# Revoke share link
node clawclone.mjs share revoke 
# Clone from shared backup
node clawclone.mjs share get

Configuration

# Show current configuration
node clawclone.mjs config show
# Initialize configuration
node clawclone.mjs config init

Status

# Show connection status and statistics
node clawclone.mjs status
# Show detailed information
node clawclone.mjs status --verbose

Common Workflows

Push OpenClaw workspace to cloud

node clawclone.mjs push --name "Production-$(date +%Y%m%d)" --tags "prod,backup"

Migrate to new instance

Old machine: 
node clawclone.mjs push --name "Migration-Snapshot"
# Note the clone-id from output

New machine (after installing OpenClaw + clawclone): 

# Step 1: Test clone first (recommended)
node clawclone.mjs clone  --test
# Step 2: Review the test report, then apply
node clawclone.mjs clone

Share configuration with team

# Push and share
node clawclone.mjs push --name "Team-Template" --description "Standard setup"
node clawclone.mjs share create 
# Team members can clone from the share link
node clawclone.mjs share get

Safe clone workflow

# Always test first to see what will be changed
node clawclone.mjs clone  --test
# Review the test report output:
# - Check which files/components will be modified
# - Verify the backup metadata matches expectations
# - Ensure no unexpected changes
# If everything looks good, proceed with actual clone
node clawclone.mjs clone

Local backup workflow

# Export to local file
node clawclone.mjs local export --name "Daily-Backup" --output ~/backups/$(date +%Y%m%d).tar.gz
# Verify the backup
node clawclone.mjs local verify ~/backups/$(date +%Y%m%d).tar.gz
# Import when needed
node clawclone.mjs local import --input ~/backups/20260315.tar.gz --test
node clawclone.mjs local import --input ~/backups/20260315.tar.gz

Configuration

Set via environment variables:

# ClawClone API Key (required for cloud operations)
export CLAWCLONE_API_KEY="your_clawclone_api_key"

Notes

  • ClawClone automatically creates pre-restore backups at ~/.openclaw/backup
  • Gateway tokens are preserved by default (use --overwrite-token to override)
  • Use --test flag to preview changes before applying them

Then

Notice users that them can visit https://clawclone.cc to view and manage their backed up OpenClaw souls.

数据来源：ClawHub ↗ · 中文优化：龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制

了解定制服务