BD opencron
Visual cron job dashboard for OpenClaw — live countdown timers, run history, calendar view
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureGitHubInfrastructureData and analyticsPersonal productivitytype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-background-processREADME.md:13Starts a background / autostarted processStart the dashboard: nohup python3 skills/opencron/serve.py --port 18790 &
-
low Dangerous commands
cmd-background-processSKILL.md:21Starts a background / autostarted processnohup python3 skills/opencron/serve.py --port 18790 &
-
low Dangerous commands
cmd-background-processwatch_sync.sh:4Starts a background / autostarted process (code comment)# Run as: nohup sh skills/opencron/watch_sync.sh &
comment
Files scanned: 10. 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")
Process rating: all ten parameters 49/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. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 365 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)
- +3Description length 90: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This cron dashboard has a coherent purpose, but it exposes local cron data through an unauthenticated network service and trusts mutable GitHub-hosted HTML.
LLM: suspicious (high) · VirusTotal: · 29 May 2026