ClawHub

Cron Watchdog

v1.0.0

Monitor all OpenClaw cron jobs for failures and auto-fix common errors (model-not-allowed, timeouts). Posts to Slack only when issues are found. Runs every 6...

⭐ 0· 132·0 current·0 all-time
by@mpbshhx
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the instructions: it enumerates cron jobs, updates job payloads (model, timeout), and posts to Slack only for issues. Declared tool usage (cron and message) aligns with the stated purpose.
ℹ
Instruction Scope
Instructions include modifying cron jobs (via cron(action: "update")) and force-running them, which is within scope for an auto-healing watchdog. Note: the skill will perform write actions (model/timeouts) — users should be aware of automatic changes and verify the target model/timeout policy is acceptable.
✓
Install Mechanism
Instruction-only skill with no install spec or code files — nothing is written to disk and no external downloads occur.
✓
Credentials
No environment variables, credentials, or config paths are requested. The only external interaction is Slack via the message tool (channel and target ID are hard-coded in instructions), which is proportional to the described alerting behavior.
✓
Persistence & Privilege
always is false (not force-included). The skill will be capable of autonomous invocation by default (platform normal), and it performs modifications only through the cron tool; it does not claim to change other skills or global agent configs.
Assessment
This skill appears coherent for automated cron health monitoring, but note it will (when invoked) automatically update job payloads and force-run jobs. Before installing, verify: the hard-coded Slack target/channel are correct for your workspace; the chosen fallback model (anthropic/claude-sonnet-4-6) and timeout increments match your policies; and you have backups or a staging environment to test the auto-fixes. If you want tighter control, ask for a confirmation step before applying updates or restrict the skill to a test project first.

Like a lobster shell, security has layers — review code before you run it.

latestvk97916fkptdrqksktg065xp0m1835w0b

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🐺 Clawdis

Comments