Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Cron Scheduler
v1.0.0Create, list, modify, and remove scheduled cron jobs to automate system tasks using simplified cron syntax and manage output logging.
⭐ 2· 4k·69 current·71 all-time
by@picaye
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (manage cron jobs) matches the instructions: listing user/system crontabs, adding/removing lines, checking logs, and sample cron entries. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
The SKILL.md tells the agent to run commands that read system files (/etc/cron.*), view logs (/var/log/syslog, journalctl), modify the user crontab, and suggests service control and backup commands (systemctl, pg_dump). Those actions are expected for a cron manager, but they do allow modification of system state and access to potentially sensitive files — the user or agent should confirm actions before applying them, especially anything touching system crons or using elevated privileges.
Install Mechanism
No install spec, no code files — instruction-only. Nothing is downloaded or written by an installer, which minimizes installation risk.
Credentials
The skill declares no required environment variables or credentials. The instructions note cron's minimal PATH and show how to set PATH or MAILTO in crontab; these are appropriate and proportional to the described functionality.
Persistence & Privilege
always:false and no special persistence requested. The skill does not request to modify other skills or system-wide agent settings. It instructs operations that, if executed, change system state (crontab, systemctl) — this is expected for a cron tool but is an operational risk rather than an incoherence.
Assessment
This skill is coherent with its stated purpose, but cron jobs can run arbitrary commands and modify system state. Before installing or letting an agent apply changes automatically: review any cron lines the agent will add, avoid embedding credentials or secrets in cron commands, use absolute paths, test commands manually (as the SKILL.md advises), back up current crontab (crontab -l > crontab.bak) before changes, and be cautious with system-level edits (e.g., /etc/cron.d, systemctl) which require root. If you want to limit risk, require explicit user confirmation before the agent writes or edits crontabs or runs commands that need elevated privileges.Like a lobster shell, security has layers — review code before you run it.
latestvk975fn12fm19svpdwv88atbwxs81s1f1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.