cron-worker-guardrails
von phenomenoner
Coding Agents & IDEsKurzbeschreibung
Use when hardening OpenClaw cron workers (especially isolated agentTurn jobs) against quoting failures, brittle.
Beschreibung
Was dieser Skill macht
A hardening checklist for cron and background workers running in POSIX shells (bash/sh). Covers the most common failure modes: brittle quoting in one-liners, working directory and environment drift, and false pipeline errors from pipefail combined with SIGPIPE. Outputs safe patterns for scripts-first structure, deterministic execution, and silent-on-success behavior.
Cron failures are usually wrapper problems, not logic bugs, and this skill targets exactly that layer with concrete fix patterns rather than general shell advice.
Wann du ihn einsetzt
- Fixing a cron job that works locally but fails in production
- Eliminating false failures from pipefail and head in shell pipelines
- Standardizing unattended automation to emit nothing on success
- Recovering from non-fast-forward git push rejections in automated jobs
- Auditing shell one-liners for quoting and escaping bugs before scheduling
Beispiel-Workflow
User asks: my cron job keeps failing with 'unexpected EOF while looking for matching )' but the script runs fine manually
- 1
Identify the inline bash -lc '...' block as the likely source of nested quote breakage
- 2
Extract the shell logic into a standalone script at tools/<job>.sh or tools/<job>.py
- 3
Replace the cron entry with a single short command: python3 tools/<job>.py
- 4
Add a cd to the repo root at the top of the script to fix cwd drift
- 5
Ensure the script prints nothing on success, or exactly NO_REPLY
A cron entry that calls one script, with deterministic working directory, no quoting issues, and silent-on-success behavior
Installation
clawhub install phenomenoner/cron-worker-guardrailsFühre den CLI-Befehl aus oder füge den Prompt in Claude Code, Cursor, Codex oder deinen Coding-Agenten ein.