OpenClaw Healthcheck Cron
PassAudited by ClawScan on May 1, 2026.
Overview
This skill transparently sets up a twice-daily local OpenClaw healthcheck script; the main thing to notice is that it creates a recurring cron-style agent job that runs shell commands and writes reports to /tmp.
This appears safe for its stated purpose. Before installing, verify the cron schedule and timezone, review and manually run the included shell script, and make sure you know how to disable the recurring job if you no longer want automated healthchecks.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If installed as shown, the healthcheck will keep running twice a day until the cron job is disabled or removed.
The skill provides an enabled recurring agentTurn cron job that runs twice daily. This is disclosed and matches the healthcheck purpose, but it is persistent automation.
"schedule": { "kind": "cron", "expr": "0 6,19 * * *" } ... "payload": { "kind": "agentTurn" ... } ... "enabled": trueConfirm the timezone and schedule before enabling it, and keep a clear way to pause or delete the cron job.
The agent will run local shell commands for the healthcheck, including OpenClaw status checks if the CLI is available.
The scheduled task runs a local shell script. This is central to the skill's stated purpose and the included script is small and healthcheck-focused, but it is still local command execution.
Execute `bash scripts/healthcheck.sh`
Review the script before scheduling it and run it manually once, as the skill itself recommends.
The healthcheck may produce warnings or fail to run as intended if bash or the OpenClaw CLI is not available in the scheduled job environment.
The script uses bash and attempts OpenClaw CLI commands, while the registry metadata lists no required binaries. The script handles missing OpenClaw as warnings, so this is a compatibility/disclosure note rather than a security concern.
check_cmd "openclaw binary available" command -v openclaw check_cmd "gateway status command" openclaw gateway status check_cmd "openclaw status command" openclaw status
Ensure the scheduled environment has the intended shell and OpenClaw CLI path, or update the job/script to use absolute paths.