SKILLEMALL.ai
GitHub ↗ RU Sign in

BC cron-doctor

Diagnose and validate cron expressions before they ship. Catches the five silent death-traps: impossible dates that never fire, OR-semantics that fire too often, midnight spikes, uneven step drift, and leap-year February 29.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 3 files body ≈ 2 209 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Diagnose and validate cron expressions before they ship.

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

AnalyzerKubernetesGitHubInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
93
Quality 40%
79
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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
  • medium Dangerous commands cmd-persistence SKILL.md:226
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    non-standard `@reboot` / `L` / `#` extensions without a note.
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:75
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    These are the bugs that pass `crontab -l` validation but break in production.
    quoted
  • low Dangerous commands cmd-cron-mention SKILL.md:199
    Mentions editing / listing crontab (quoted — discussed, not commanded)
    - ❌ Don't trust `crontab -l` validation — it only checks syntax, not semantics.
    quoted

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

Against the Agent Skills spec

  • warning description-long-hermes description is 224 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "license_source"

Process rating: all ten parameters 58/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 22 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2209 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 11 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 224: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 22 items
  • +4Has examples (8 code blocks)
  • +3All 2 scripts are documented
  • +1License stated

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