FD cron-scheduler
Manage cron jobs on macOS/Linux - list, add, remove, backup, and schedule recurring tasks
Not recommendedcritical or high security findings · low grade F
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
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
- 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.
- 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 · 11
-
high Dangerous commands
cmd-persistencescripts/cron-helper.sh:65Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab_output=$(crontab -l 2>/dev/null) || true
-
high Dangerous commands
cmd-persistencescripts/cron-helper.sh:158Persistence mechanism (cron / launchd / scheduled task / autorun registry)current_crontab=$(crontab -l 2>/dev/null) || true
-
high Dangerous commands
cmd-persistencescripts/cron-helper.sh:203Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab_output=$(crontab -l 2>/dev/null) || true
-
high Dangerous commands
cmd-persistencescripts/cron-helper.sh:249Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab_output=$(crontab -l 2>/dev/null) || true
-
high Dangerous commands
cmd-persistencescripts/cron-helper.sh:306Persistence mechanism (cron / launchd / scheduled task / autorun registry)sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.cron.plist 2>/dev/null || \
Medium and low: 6
-
medium Dangerous commands
cmd-shell-rcSKILL.md:71Writes to a shell startup fileecho 'export PATH="$HOME/.openclaw/workspace/skills/cron-scheduler/scripts:$PATH"' >> ~/.zshrc
-
low Dangerous commands
cmd-cron-mentionscripts/cron-helper.sh:65Mentions editing / listing crontabcrontab_output=$(crontab -l 2>/dev/null) || true
-
low Dangerous commands
cmd-cron-mentionscripts/cron-helper.sh:131Mentions editing / listing crontabcrontab -l 2>/dev/null >> "$temp_file" || true
-
low Dangerous commands
cmd-cron-mentionscripts/cron-helper.sh:158Mentions editing / listing crontabcurrent_crontab=$(crontab -l 2>/dev/null) || true
-
low Dangerous commands
cmd-cron-mentionscripts/cron-helper.sh:191Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionscripts/cron-helper.sh:203Mentions editing / listing crontabcrontab_output=$(crontab -l 2>/dev/null) || true
Files scanned: 4. 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") - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "commands"
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. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (cron-scheduler) differs from the folder (openclaw-skill-cron-scheduler)
- 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 769 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 89: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (10 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
This cron-management skill is functional and mostly disclosed, but it can create persistent scheduled commands, delete cron entries, and run sudo service-control actions without enough guardrails.
LLM: suspicious (high) · VirusTotal: · 29 May 2026