BC cron-health-cron
Create portable OpenClaw cron health checks with deterministic scripts, config, validation, and reports.
Create portable OpenClaw cron health checks with deterministic scripts, config, validation, and reports.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
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
- 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
✓ No critical or high findings
Medium and low: 10
-
medium Dangerous commands
cmd-persistencereferences/setup-manual.md:37Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)- `crontab_files`: files that contain crontab syntax, such as `/etc/crontab` and `/etc/cron.d/*`
detector -
medium Dangerous commands
cmd-persistencereferences/setup-manual.md:38Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- `run_parts_dirs`: directories containing executable scripts, such as `/etc/cron.daily`
quoted -
medium Dangerous commands
cmd-persistencereferences/setup-manual.md:40Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)Never parse scripts inside `/etc/cron.daily` or similar directories as if their contents were crontab lines.
quoted -
medium Dangerous commands
cmd-persistencetemplates/cron-health-config.json:55Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed){"path": "/etc/cron.hourly", "frequency": "hourly", "expected_log_freshness_minutes": 180},code literal -
low Dangerous commands
cmd-cron-mentionSKILL.md:4Mentions editing / listing crontab (detector / deny-list definition)metadata: { "openclaw": { "requires": { "bins": ["python3", "openclaw", "crontab", "systemctl"] }, "permissions": { "filesystem": ["read configured cron files, scheduler metadata files, registry notesdetector -
low Dangerous commands
cmd-cron-mentionSKILL.md:55Mentions editing / listing crontab (detector / deny-list definition)- Command probes: only the fixed argv forms enforced by the bundled script: `openclaw cron list --json`, `crontab -l`, `systemctl --failed --no-pager --plain`, `systemctl list-timers --all --no-pager
detector -
low Risky intent
intent-offensive-securitySKILL.md:88Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Keep the health-check run non-mutating: no scheduler edits, service edits, registry writes, callback writes, network calls, shell expansion, privilege escalation, or arbitrary command strings.
-
low Dangerous commands
cmd-persistencetemplates/cron-health-config.json:53Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)"crontab_files": ["/etc/crontab", "/etc/cron.d/*"],
detectorcode literal -
low Dangerous commands
cmd-persistencetemplates/cron-health-config.json:56Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed){"path": "/etc/cron.daily", "frequency": "daily", "expected_log_freshness_minutes": 1800},detectorcode literal -
low Dangerous commands
cmd-persistencetemplates/cron-health-config.json:57Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed){"path": "/etc/cron.weekly", "frequency": "weekly", "expected_log_freshness_minutes": 11520},detectorcode literal
Files scanned: 7. 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 62/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
- 30Running it twice. 8 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 86 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2803 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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
- +3Description length 104: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 14 headings
- +3Step-by-step instructions: 86 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.