SKILLEMALL.ai
GitHub ↗ RU Sign in

DD Cron Scheduler

Manage scheduled tasks and automation on your system using cron.

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 018 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Manage scheduled tasks and automation on your system using cron.

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

ProcedureAI and agentsPersonal productivitytype 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
D
50/100
safety, quality, tests
Safety 60%
44
Quality 40%
60
Run on models
none yet
Process rating
D
41/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 · 10

  • high Dangerous commands cmd-persistence SKILL.md:25
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    ls /etc/cron.d/ 2>/dev/null
  • high Dangerous commands cmd-persistence SKILL.md:37
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    (crontab -l 2>/dev/null; echo "SCHEDULE COMMAND") | crontab -
Medium and low: 8
  • medium Dangerous commands cmd-persistence SKILL.md:28
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    echo "Hourly:  $(ls /etc/cron.hourly/ 2>/dev/null | wc -l) jobs"
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:29
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    echo "Daily:   $(ls /etc/cron.daily/ 2>/dev/null | wc -l) jobs"
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:30
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    echo "Weekly:  $(ls /etc/cron.weekly/ 2>/dev/null | wc -l) jobs"
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:22
    Mentions editing / listing crontab
    crontab -l 2>/dev/null || echo "(empty)"
  • low Dangerous commands cmd-cron-mention SKILL.md:37
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "SCHEDULE COMMAND") | crontab -
  • low Dangerous commands cmd-cron-mention SKILL.md:52
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention SKILL.md:55
    Mentions editing / listing crontab
    crontab -l | grep -v "PATTERN_TO_REMOVE" | crontab -
  • low Dangerous commands cmd-cron-mention SKILL.md:109
    Mentions editing / listing crontab
    (crontab -l 2>/dev/null; echo "PATH=/usr/local/bin:/usr/bin:/bin

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 41/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (Cron Scheduler) differs from the folder (cron-scheduler)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 6 steps
  • 100Execution cost. Instruction body is 1018 tokens
  • 100Progress reporting. Reports progress

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 64: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (9 code blocks)

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