Fox Cron Health Check

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

Security Scan

The skill's code and runtime instructions are coherent with its stated purpose: it analyzes local OpenClaw cron job config and run logs and does not request credentials or make network calls.

Purpose & Capability

The skill claims to monitor OpenClaw cron jobs and the included Python script reads ~/.openclaw/cron/jobs.json and ~/.openclaw/cron/runs/*.jsonl to analyze runs — this is consistent with the stated purpose. Minor packaging inconsistencies exist: registry metadata shows slug 'fox-cron-health-check' while _meta.json uses 'cron-health-check', the ownerId values differ between registry metadata and _meta.json, and SKILL.md usage examples reference a /Users/ghost path. These look like sloppy packaging but do not change the core capability.

Instruction Scope

SKILL.md instructs running the provided Python script (examples point at a local skill workspace path). The script only reads job configuration and run history files under the OpenClaw home directory and prints or emits JSON results/exit codes. The instructions do not direct the agent to read other system files, environment variables, or send data to external endpoints. The SKILL.md references an OpenRouter settings link only in output text; the code does not perform network calls.

Install Mechanism

There is no install spec (instruction-only skill with a bundled Python script). No external downloads or package installs are specified. The only risk is running the bundled Python script locally; the file contents are readable and not obfuscated.

Credentials

The skill requires no environment variables, binaries, or credentials. It reads local OpenClaw data (jobs.json and run logs) which is appropriate for a cron-health checker. No secret-exposing env vars are requested.

Persistence & Privilege

The skill does not request persistent/global privileges, always=false, and does not modify other skills or system-wide configuration. It only runs when invoked or scheduled by the agent.

Assessment

This skill appears to do exactly what it says: analyze local OpenClaw cron job configs and run logs and report issues. Before installing or scheduling it: 1) verify the skill source/owner (registry ownerId vs _meta.json ownerId mismatch suggests sloppy packaging); 2) review the included script yourself (it's bundled and human-readable) and confirm your logs live under ~/.openclaw/cron or run with --openclaw-home to point to a test directory; 3) be aware the script will read job configs and run logs (these may contain sensitive data or error messages); 4) run it manually first to see output and exit codes before adding as a cron/scheduled agent task. If you don't trust the publisher, do not schedule it to run automatically.

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