Cron Retry
v1.0.0Auto-retry failed cron jobs on connection recovery. Use when cron jobs fail due to network errors and should be retried when connectivity is restored. Integrates with heartbeat to detect failed jobs and re-run them automatically.
⭐ 3· 4.2k·11 current·13 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the SKILL.md describes detecting 'error' cron jobs, matching network-related error patterns, and re-running them via the cron tool (examples show 'clawdbot cron list' and 'clawdbot cron run'). No unrelated credentials, binaries, or system paths are requested.
Instruction Scope
Instructions are narrowly focused on listing cron jobs, filtering by enabled + lastStatus == 'error', matching network error patterns, and invoking cron run. This stays within the stated purpose. Caution: the error-pattern matching is broad and could produce false positives (leading to re-running jobs whose failures are not truly transient). The doc mentions checks to avoid loops (lastRunAtMs) but leaves implementation details unspecified; agents must ensure idempotency and safeguards to avoid harmful re-execution of side-effectful jobs.
Install Mechanism
No install spec and no code files — instruction-only skill — so nothing will be downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. Declared requirements align with the described behavior (it operates by invoking the cron tool available to the agent).
Persistence & Privilege
always is false and the skill is user-invocable with normal autonomous invocation allowed; this is appropriate for an automation that runs on heartbeat. The skill does not ask for persistent system-level configuration or to modify other skills.
Assessment
This skill is coherent with its purpose, but review before enabling: ensure the agent has a safe, testable cron tool (e.g., clawdbot cron commands exist); run in staging first. Make error-pattern matching conservative to avoid re-running non-transient failures; require job metadata or idempotency guarantees for jobs that perform side-effectful actions; enforce backoff and max-retry counts and log/audit every retry. Don't enable always:true; restrict which jobs are eligible (tags or a retryable flag) if possible.Like a lobster shell, security has layers — review code before you run it.
latestvk977qreh37h46w4vn2qbtsmmf1802d57
License
MIT-0
Free to use, modify, and redistribute. No attribution required.