Cron Health Check Zc
v1.0.0Monitors OpenClaw cron job health, identifies failures, timeouts, and delivery issues.
⭐ 0· 74·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description describe monitoring cron job health; the included Python script reads cron job definitions and run history under an OpenClaw workspace (.openclaw/cron) and computes health metrics. The requested resources (local files under OpenClaw home) are consistent with this purpose.
Instruction Scope
SKILL.md instructs running the shipped script and provides example cron payloads. The examples include hard-coded example paths (/Users/ghost/.openclaw/...), but the script uses a configurable --openclaw-home (defaulting to ~/.openclaw). The script only reads jobs.json and per-job .jsonl run logs; it does not call external services or read unrelated system paths. Review jobs.json/run logs before running if they contain sensitive data.
Install Mechanism
No install spec; this is an instruction-only skill with a single Python script. Nothing will be downloaded or written by an installer during skill installation.
Credentials
The skill declares no environment variables or credentials and the code does not access environment secrets. It inspects local OpenClaw cron config and logs only. The SKILL.md mentions OpenRouter limits in diagnostic text but the script only looks for 'limit exceeded' text in stored error messages; it does not use or require any OpenRouter credentials.
Persistence & Privilege
The skill does not request permanent presence, does not modify other skills or global agent configuration, and has normal user-invocable/autonomous invocation defaults. Running it as a scheduled job will only cause the script to read local OpenClaw cron files and emit reports/exit codes.
Assessment
This skill appears coherent and limited to reading OpenClaw cron configuration and run logs to produce health reports; it does not require credentials or network access. Before installing or scheduling it: (1) inspect your ~/.openclaw/cron/jobs.json and run log files for sensitive content you don't want read by a third-party script, (2) note the SKILL.md examples use a hard-coded /Users/ghost path—confirm the script will be run with the correct --openclaw-home or placed in the expected workspace, (3) verify the owner/source is trustworthy (ownerId in _meta.json differs slightly from registry metadata), and (4) run the script in a safe/isolated environment first to confirm its behavior. If you need the skill to report externally, modify it to add explicit, auditable network calls rather than relying on ad-hoc behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97d0xgn1rz8vxcnkjkchd9zss83nz3h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.