Cron Health Check Zc

Monitors OpenClaw cron job health, identifies failures, timeouts, and delivery issues.

Security Scan

The skill's code and instructions match its stated purpose (reading OpenClaw cron job config and run logs to report health); it requires no installs or credentials and doesn't attempt network access or privileged changes.

Purpose & 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.

Cron Health Check | OpenClaw Skill

Description

Monitors OpenClaw cron job health, identifies failures, timeouts, and delivery issues.

Cron Health Check | OpenClaw Skill

Monitors the health of OpenClaw cron jobs by analyzing run history and identifying patterns of failures, timeouts, and delivery issues.

Usage

• As a scheduled cron job to monitor job health proactively
• Manually to check current cron job status
• After fixing cron job errors to verify improvements

# Check health of all cron jobs (last 24 hours)
python3 /Users/ghost/.openclaw/workspace/skills/cron-health-check/scripts/check_cron_health.py

# Check last 48 hours
python3 /Users/ghost/.openclaw/workspace/skills/cron-health-check/scripts/check_cron_health.py --hours 48

# Output JSON format
python3 /Users/ghost/.openclaw/workspace/skills/cron-health-check/scripts/check_cron_health.py --json

What this skill does

• Analyzes cron job run history from the last N hours
• Identifies jobs with consecutive failures, timeouts, or delivery issues
• Reports health status (healthy/warning/critical) for each job
• Suggests fixes (e.g., adding --best-effort-deliver for delivery failures)
• Detects OpenRouter API limit issues

Integration as a Cron Job

This skill can run periodically to monitor cron job health:

{
  "payload": {
    "kind": "agentTurn",
    "message": "Run cron-health-check skill to analyze cron job health.",
    "model": "openrouter/google/gemini-2.5-flash",
    "thinking": "low",
    "timeoutSeconds": 60
  },
  "schedule": {
    "kind": "cron",
    "cron": "0 */6 * * *"
  },
  "delivery": {
    "mode": "announce",
    "bestEffort": true
  },
  "sessionTarget": "isolated",
  "name": "Cron Health Monitor"
}

Output

Health status for each job:

• healthy: No issues detected
• warning: Some issues but not critical
• critical: Multiple consecutive failures or timeouts

Issues detected:

• Consecutive errors
• Timeout patterns
• Delivery failures (suggests --best-effort-deliver)
• OpenRouter API limit exceeded

Exit Codes

• 0: All jobs healthy
• 1: Warning issues found
• 2: Critical issues found