CF openclaw-checkpoint
Backup and restore OpenClaw workspace state and agents across machines using git. Enables disaster recovery by syncing SOUL.md, MEMORY.md, memory files, cron jobs, agents (~/.openclaw/agents/), and configuration to a remote repository. Use when user wants to checkpoint their OpenClaw state, restore on a new machine, migrate between computers, or protect against data loss. Provides commands checkpoint (help overview), checkpoint-setup (interactive onboarding), checkpoint-backup, checkpoint-restore (with interactive checkpoint selection or --latest for most recent), checkpoint-schedule (auto-backup), checkpoint-stop, checkpoint-status, checkpoint-init, and checkpoint-reset. Supports multi-agent backup with flags --workspace-only, --agents-only, and --agent <name>. Automatically backs up cron jobs to memory/cron-jobs-backup.json on each checkpoint-backup.
As a process F 43/100 · Will not run — References files that are not bundled: references/setup.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 11
✓ No critical or high findings
Medium and low: 11
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostINSTALL.md:22Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:51Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:89Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-persistenceREADME.md:156Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- **macOS**: Creates a launchd plist at `~/Library/LaunchAgents/com.openclaw.checkpoint.plist`
quoted -
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:48Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:342Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:508Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/AnthonyFrancis/openclaw-checkpoint/main/scripts/install-openclaw-checkpoint.sh | bash
-
medium Dangerous commands
cmd-persistenceSKILL.md:570Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- **macOS**: Creates a launchd plist at `~/Library/LaunchAgents/com.openclaw.checkpoint.plist`
quoted -
low Dangerous commands
cmd-cron-mentionREADME.md:157Mentions editing / listing crontab (quoted — discussed, not commanded)- **Linux**: Adds a user-level cron job (visible via `crontab -l`)
quoted -
low Dangerous commands
cmd-cron-mentionSKILL.md:491Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionSKILL.md:571Mentions editing / listing crontab (quoted — discussed, not commanded)- **Linux**: Adds a user-level cron job (visible via `crontab -l`)
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5643 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/setup.md
Process rating: all ten parameters 43/100
- 0Tools and files. 1 referenced file(s) missing: references/setup.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 25 mutating operations with no state check
- 70Execution cost. Instruction body is 5643 tokens
- 100Steps. 161 steps
- 100Failures and branches. 8 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (4 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 864: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 55 headings
- +3Step-by-step instructions: 161 items
- +4Has examples (28 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.