SKILLEMALL.ai
GitHub ↗ RU Sign in

BC cron-backup

Set up scheduled automated backups with version tracking and cleanup. Use when users need to (1) Schedule periodic backups of directories or files, (2) Monitor version changes and backup on updates, (3) Automatically clean up old backups to save space, (4) Create backup strategies for configuration files, code repositories, or user data.

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

Set up scheduled automated backups with version tracking and cleanup.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmenttype 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
79/100
safety, quality, tests
Safety 60%
77
Quality 40%
83
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.
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 · 6

  • high Dangerous commands cmd-persistence scripts/setup-cron.sh:83
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null || echo "") | grep -v "$CRON_TAG" | { cat; echo "$CRON_ENTRY"; } | crontab -
Medium and low: 5
  • low Dangerous commands cmd-cron-mention scripts/setup-cron.sh:76
    Mentions editing / listing crontab
    if crontab -l 2>/dev/null | grep -q "$CRON_TAG"; then
  • low Dangerous commands cmd-cron-mention scripts/setup-cron.sh:78
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "Remove it first with: crontab -e"
    code literal
  • low Dangerous commands cmd-cron-mention scripts/setup-cron.sh:83
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null || echo "") | grep -v "$CRON_TAG" | { cat; echo "$CRON_ENTRY"; } | crontab -
  • low Dangerous commands cmd-cron-mention scripts/setup-cron.sh:87
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "View all cron jobs: crontab -l"
    code literal
  • low Dangerous commands cmd-cron-mention scripts/setup-cron.sh:88
    Mentions editing / listing crontab (string literal in code, not executed)
    echo "Remove this job: crontab -e (delete the line with $CRON_TAG)"
    code literal

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 53/100

  • 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. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 43 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1061 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
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +3Description length 339: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 43 items
  • +4Has examples (12 code blocks)
  • +3All 5 scripts are documented

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