BF hermes-backup
Multi-platform backup and restore for Hermes Agent and OpenClaw. Backs up configuration, memories, skills, sessions, and workspace. Features: optional encryption, optional cloud storage (S3/Google Drive), incremental or full backups, flexible retention, integrity verification, and web-based management UI. Free and open source.
As a process F 38/100 · Will not run — References files that are not bundled: scripts/serve.sh, scripts/verify.sh, scripts/cloud-upload.sh
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-privilegeSKILL.md:304Privilege escalation / world-writable permissions (negated — the text forbids it)- Never `chmod 777` a backup
negated
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/serve.sh - warning
missing-refreference to a missing file: scripts/verify.sh - warning
missing-refreference to a missing file: scripts/cloud-upload.sh
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: scripts/serve.sh, scripts/verify.sh, scripts/cloud-upload.sh
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (hermes-backup) differs from the folder (complete-agent-backup)
- 100Steps. 46 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2437 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 328: enough signal without eating the budget
- +4Structure: 52 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (25 code blocks)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.