SKILLEMALL.ai
GitHub ↗ RU Sign in

BD openclaw-backup-automation

Automated backup for OpenClaw instances. Backs up agents, skills, cron jobs, and memory. Supports local tar archives. Credentials, periodic scheduling, and git sync are OPT-IN only.

ClawHub Agent Skills author: jzargona v1.0.1 MIT-0 4 files body ≈ 940 tokens Open the sourceclawhub.ai↗ analyzed 12 h ago

Automated backup for OpenClaw instances.

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

IntegrationAI and agentstype 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
B
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
73
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Dangerous commands cmd-cron-mention scripts/backup.js:133
    Mentions editing / listing crontab (string literal in code, not executed)
    console.log('   crontab -e');
    code literal
  • low Dangerous commands cmd-cron-mention SKILL.md:93
    Mentions editing / listing crontab
    crontab -e

Files scanned: 4. 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 46/100

  • 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
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (openclaw-backup-automation) differs from the folder (backup-automation)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 17 steps
  • 100Execution cost. Instruction body is 940 tokens

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
  • -217 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 181: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (12 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This backup skill mostly matches its purpose, but it needs review because restore can overwrite home-directory files and optional git sync can push a whole workspace to a remote repository.
LLM: suspicious (high) · VirusTotal: · 1 Jul 2026