SKILLEMALL.ai
RU Sign in

CD backup-recovery

Backup & Recovery Automation for OpenClaw using rClone. Daily backups to Google Drive with 20-day rotation.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files · 1 script body ≈ 1 923 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Backup & Recovery Automation for OpenClaw using rClone.

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGoogle DriveData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
73/100
safety, quality, tests
Safety 60%
80
Quality 40%
63
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

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.

Dangerous commands
If you install

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.

For the author

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

  1. 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.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 3

  • high Dangerous commands cmd-persistence setup_rclone.sh:120
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null | grep -v "backup-recovery"; echo "${CRON_JOB}") | crontab -
Medium and low: 2
  • low Dangerous commands cmd-cron-mention setup_rclone.sh:120
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null | grep -v "backup-recovery"; echo "${CRON_JOB}") | crontab -
  • low Dangerous commands cmd-cron-mention setup_rclone.sh:159
    Mentions editing / listing crontab
    crontab -l | grep "backup-recovery"

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 40Consistency. Frontmatter name (backup-recovery) differs from the folder (rhandus-backup-recovery)
  • 100Tools and files. No external tools needed
  • 100Steps. 60 steps
  • 100Execution cost. Instruction body is 1923 tokens
  • 100Running it twice. No mutating operations
  • low 10 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)
  • +3Description length 107: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -226 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 60 items
  • +4Has examples (15 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.