Schedule Task
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill is meant to manage cron jobs, but its script can leave scheduled commands running after removal/disable and can overwrite unrelated scheduled jobs.
Review and back up your crontab before using this skill. After adding, disabling, or removing tasks, run `crontab -l` yourself to confirm the result. Do not rely on the documented notification, timeout, or health-check features until they are actually implemented.
Findings (4)
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.
Using remove, enable, or disable can unintentionally delete unrelated scheduled jobs such as backups, monitoring, or maintenance tasks.
The rebuild path writes only the skill's saved task lines back to the entire user crontab, without preserving or marking unrelated existing cron entries.
remove_task(): ... rebuild_crontab(tasks) ...; rebuild_crontab(): new_crontab = "\n".join(lines) + "\n"; subprocess.Popen(['crontab', '-'], ...)
Back up `crontab -l` before use. The skill should tag its own cron lines and edit only those lines while preserving all other crontab entries.
A scheduled command may continue running periodically after the user believes it has been removed or disabled.
When the managed task list becomes empty, `rebuild_crontab()` does not install an empty crontab, so a previously added cron entry can keep running even after the tool reports it was removed or disabled.
print(f"Task {task_id} removed") ... if new_crontab.strip(): proc = subprocess.Popen(['crontab', '-'], stdin=subprocess.PIPE)After any remove or disable action, manually inspect `crontab -l`. The skill should reliably remove or disable its own cron entries, including when no managed tasks remain.
Users may rely on alerts, health checks, or timeouts that are not actually implemented, especially for backups or reports.
The documentation describes safety features such as failure notifications, health monitoring, and timeouts, but the included script only stores these options or reports enabled/disabled state rather than enforcing them.
- **Health Checks**: Monitor task execution status - **Notifications**: Alert on task failure ... --timeout SECS Task timeout in seconds
Do not rely on the documented notification, health, or timeout features unless the implementation is fixed or external monitoring is used.
The skill may fail or behave unexpectedly on systems without cron, and users have limited provenance information.
The metadata does not declare provenance, Unix-only operation, or the required `crontab` binary, even though the script depends on system cron tooling.
Source: unknown; Homepage: none; OS restriction: none; Required binaries: none
Use only on systems where you understand the cron environment, and prefer metadata that declares the `crontab` dependency and supported operating systems.