Cron Scheduler

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill does what it says, but it gives the agent broad power to create or remove persistent scheduled shell commands without clear confirmation, scoping, or rollback safeguards.

Install only if you want your agent to manage real cron jobs on your machine. Review every scheduled command carefully, require confirmation before modifying crontab, keep a backup, and periodically audit scheduled jobs because they can continue running after the task is finished.

Findings (2)

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.

What this means

A mistaken or overly broad cron edit could schedule the wrong command, remove unrelated jobs, or repeatedly run actions the user did not intend.

Why it was flagged

The skill documents direct mutation of the user's crontab, including adding arbitrary scheduled commands and removing entries by pattern, but does not require confirmation, backups, diffs, or scoped ownership markers.

Skill content
(crontab -l 2>/dev/null; echo "SCHEDULE COMMAND") | crontab - ... crontab -l | grep -v "PATTERN_TO_REMOVE" | crontab -
Recommendation

Before allowing changes, review the exact cron line, require explicit approval, back up the existing crontab, and tag entries so only skill-created jobs are modified.

ConcernHigh Confidence
ASI10: Rogue Agents
What this means

A scheduled task can keep running after the conversation ends, continue making changes, producing network calls, or consuming resources until the user notices and removes it.

Why it was flagged

Cron jobs are persistent recurring background actions. The skill intentionally enables broad scheduled execution, but the artifact does not define lifecycle limits, expiration, review, or cleanup guarantees.

Skill content
Automate backups, health checks, cleanup scripts, API calls, notifications — anything that should run on a schedule.
Recommendation

Use this only for clearly requested jobs, prefer least-privilege commands, add comments/labels and log paths, set an expiration where possible, and periodically list and remove unwanted entries.