← 返回 Skills 市场

Claw Time Machine

Name: Claw Time Machine
Author: tacitlab

作者 Tacit Lab · GitHub ↗ · v1.0.4 · MIT-0

cross-platform ⚠ suspicious

130

总下载

当前安装

版本数

在 OpenClaw 中安装

/install claw-time-machine

功能描述

Backup, restore, and migrate OpenClaw installations. Preserve workspace memories, credentials, custom skills, scheduled tasks, and core configuration. Use wh...

使用说明 (SKILL.md)

Claw Time Machine

Back up, restore, and migrate the important state of an OpenClaw installation.

Run the script

Use the bundled script:

./scripts/ctm.sh \x3Ccommand> [args]

Commands:

backup [filename] — create a backup under ~/.ctm/
list — show backups, newest first
restore \x3Cindex|filename|latest> [--force] — restore a backup
migrate \x3Cuser@host> [--remote-dir \x3Cdir>] [--clean-remote-archive] [--force] — copy a backup to another machine and restore it there

What the script preserves

The script backs up only the important OpenClaw state, not the full installation binaries:

workspace/
credentials/
telegram/
skills/
cron/
openclaw.json
identity/

Each archive also includes a manifest.txt file that lists the captured paths.

Core workflow

Create a backup

Before a risky change, server migration, or major upgrade:

./scripts/ctm.sh backup

If the user asks how many backups exist or wants to inspect them:

./scripts/ctm.sh list

Report the count, filenames, sizes, and highlight the newest backup.

Restore a backup

Prefer listing backups first when the user is choosing by index:

./scripts/ctm.sh list
./scripts/ctm.sh restore 1

Use latest when the intent is obvious:

./scripts/ctm.sh restore latest

Add --force only when non-interactive restore is clearly intended.

Migrate to another machine

Use the migration command when the user wants a full move to a new server:

./scripts/ctm.sh migrate user@new-server

The script creates a fresh backup, copies it to the target host, and restores it there without requiring the skill to already exist on the target machine.

If the user wants the copied archive removed from the target machine after a successful restore, add --clean-remote-archive.

Important safety rules

Treat restore as destructive: it overwrites the preserved state paths.
Keep the automatic safety backup path shown by the script so rollback remains possible.
This skill does not stop or start Gateway automatically.
If the target environment is unusual, read references/usage.md before doing a migration.

Additional guidance

For detailed examples, migration notes, and failure handling, read references/usage.md.

安全使用建议

This skill appears to implement the advertised backup/restore/migrate functionality, but take these precautions before installing or using it: - Review the full scripts yourself. The package includes scripts/ctm.sh — inspect it end-to-end to confirm there is no hidden network exfiltration or unexpected commands. The manifest you were shown is truncated in the copy you received; request the complete file if unsure. - Understand what will be backed up: credentials/, telegram/, identity/ contain sensitive secrets. Backups include those by design; do not migrate them to untrusted hosts. - Migration uses scp and runs a restore script over ssh on the target host. Only migrate to machines you control or fully trust and ensure your SSH keys are protected. The skill does not perform remote authentication hardening. - The package metadata omits required binaries (tar, ssh, scp, cp, mktemp, du, stat, find, sort). Expect the script to fail if those tools are missing; this metadata mismatch is sloppy and reduces transparency. - Test in a disposable environment first: run backup and restore locally with --dry-run or on a throwaway VM to ensure behavior matches expectations and safety backups are created. - If you need higher assurance, ask the publisher for: (1) a full, untruncated copy of scripts/ctm.sh; (2) an explicit statement about what files inside credentials/ and identity/ are copied; (3) a signed release or source repo so you can audit history. Given the metadata inconsistencies and the sensitive nature of data being handled, proceed only after you review the script and confirm you trust the target host(s).

能力评估

ℹ Purpose & Capability

Name and description match the script behavior: it collects and archives OpenClaw state (workspace, credentials, skills, etc.), lists backups, restores them, and can migrate via scp/ssh. However the registry metadata declares no required binaries or environment variables while the script clearly depends on standard CLI tools (tar, ssh, scp, cp, mktemp, du, stat, find, sort). That metadata omission is an inconsistency (likely sloppy packaging) but reduces transparency.

✓ Instruction Scope

SKILL.md instructs the agent to run the bundled script and documents backup/list/restore/migrate flows. The script's actions (copying specific OpenClaw state paths, creating manifests, creating a safety backup, using scp/ssh to run a remote restore script) are within the stated scope. The instructions do not ask the agent to read unrelated system areas, but they do operate on sensitive OpenClaw files (credentials, telegram, identity) which is expected for this tool.

✓ Install Mechanism

No install spec is provided and the skill is delivered as an instruction plus a script file. That is the lowest install-risk category. Nothing in the package pulls arbitrary remote binaries or runs external installers.

ℹ Credentials

The skill requests no environment variables or explicit credentials in metadata, yet it archives and restores sensitive directories (credentials/, telegram/, identity/) and performs remote copy/restore over SSH. These actions legitimately require access to sensitive files and an SSH connection to the target host, but the metadata does not call this out. Users should recognize that backups will include credentials and that migration pushes those credentials to the remote host.

✓ Persistence & Privilege

The skill is not marked always:true and does not request elevated platform privileges. Autonomous invocation (disable-model-invocation=false) is default; there is no other unusual persistence or cross-skill configuration modification.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install claw-time-machine
安装完成后，直接呼叫该 Skill 的名称或使用 /claw-time-machine 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v1.0.4

Harden backup/restore flow, add manifest support, improve migration behavior, and remove service lifecycle automation.

v1.0.3

Remove unnecessary Node pairing note

v1.0.2

Fix inaccurate Telegram Bot note and clarify Node pairing

v1.0.1

Finalize ctm naming: script ctm.sh, backup dir ~/.ctm, CLI ctm

v1.0.0

Add backup count query handling

v1.0.10

Major update: Refactored and simplified backup, restore, and migration functionality. - Replaced multiple individual snapshot scripts with a single unified backup/migration script. - Now handles full workspace backup and restore, including memories, credentials, skills, configs, and more. - Updated usage: supports "backup", "list", "restore", and "migrate" commands. - Revised documentation with manual migration workflow and updated file locations. - Removed scripts for incremental snapshots and granular rollback; focuses on full state backup and transfer.

元数据

Slug claw-time-machine

版本 1.0.4

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 6

常见问题