SKILLEMALL.ai
GitHub ↗ RU Sign in

BF openclaw-cron-health-monitor

主动式cron健康监控与自动修复系统：六种失败模式全覆盖（静默消失/模板展开/API耗尽/通讯静默/上下文溢出/内容腐化）+三模监控（按钉/轮询/被动）+自动修复委派。cron不会告诉你它死了——从consecutiveErrors=0时就能闻到不对劲。触发词：「cron失败」「cron健康」「定时任务监控」「cron修复」「cron检查」「consecutiveErrors」「定时任务故障」「任务监控」

ClawHub Agent Skills author: Ygq19901001 v1.0.0 MIT-0 5 files body ≈ 927 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 28/100 · Will not run — References files that are not bundled: references/cron-templates.md

IntegrationInfrastructuretype 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
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
F
28/100
Will not run
References files that are not bundled: references/cron-templates.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/cron-templates.md
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"

Process rating: all ten parameters 28/100

Will not run. References files that are not bundled: references/cron-templates.md
  • 0Tools and files. 1 referenced file(s) missing: references/cron-templates.md
  • 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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (openclaw-cron-health-monitor) differs from the folder (cron-health-monitor)
  • 100Steps. 8 steps
  • 100Execution cost. Instruction body is 927 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 204: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 8 items
  • +4Has examples (11 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

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

External checks

ClawHub: suspicious
This text-only cron monitoring skill is not malicious, but it should be reviewed because it instructs agents to automatically modify, run, reschedule, and even disable cron jobs without clear approval boundaries.
LLM: suspicious (high) · VirusTotal: · 1 Jul 2026