CF vps-bootstrap
Bootstrap a fresh VPS from zero to a fully operational OpenClaw deployment, with backup/restore and post-recovery verification. Use when setting up OpenClaw on a new VPS, recovering from a failed server, migrating between machines, or automating disaster recovery. Covers system dependencies, Node.js, Chrome, OpenClaw install, security hardening, backup to Google Drive, restore from backup, and full verification suite.
Bootstrap a fresh VPS from zero to a fully operational OpenClaw deployment, with backup/restore and post-recovery verification.
As a process F 41/100 · Will not run — References files that are not bundled: references/backup-guide.md
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 5
-
high Exfiltration
exfil-read-secret-filesscripts/restore.sh:84Reads credential / secret filescp -r "$BACKUP_ROOT/gnupg/"* "$HOME/.gnupg/" 2>/dev/null || true
Medium and low: 4
-
medium Dangerous commands
cmd-privilegescripts/bootstrap.sh:68Privilege escalation / world-writable permissionssudo tee /usr/local/bin/chrome-shim > /dev/null << 'SHIM'
-
medium Dangerous commands
cmd-privilegescripts/bootstrap.sh:72Privilege escalation / world-writable permissionssudo chmod +x /usr/local/bin/chrome-shim
-
medium Dangerous commands
cmd-privilegescripts/bootstrap.sh:102Privilege escalation / world-writable permissionssudo tee /etc/fail2ban/jail.local > /dev/null << 'F2B'
-
low Dangerous commands
cmd-background-processscripts/bootstrap.sh:112Starts a background / autostarted processsudo systemctl enable fail2ban >/dev/null 2>&1
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/backup-guide.md
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: references/backup-guide.md
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 30 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 601 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 421: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (4 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.