Pilot Cron
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill is coherent for scheduling recurring Pilot tasks, but users should understand it can create persistent cron or systemd jobs that keep running after the conversation.
Use this skill only when you intentionally want recurring automation. Before allowing it to run commands, confirm the exact script, schedule, Pilot target, log location, and how to remove or disable the cron/systemd job later.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
A scheduled task could continue running, consuming resources or submitting network tasks until the user disables it.
The skill documents mechanisms for recurring background execution that can keep operating after the original interaction.
systemctl --user enable pilot-task.timer systemctl --user start pilot-task.timer ... while true; do /path/to/submit-task.sh sleep 3600
Only create scheduled jobs after the user confirms the schedule, target script, and expected duration; include clear removal steps such as deleting the cron entry or disabling the systemd timer.
A mistaken command could schedule the wrong script, duplicate jobs, or alter existing user cron entries.
The skill uses Bash to modify the user's crontab, which is necessary for scheduling but can affect the local environment if used incorrectly.
allowed-tools:
- Bash
...
crontab -l | { cat; echo "0 * * * * /path/to/submit-task.sh"; } | crontab -Preview crontab/systemd changes before applying them and limit commands to user-approved scripts and schedules.
The skill may fail or lead to ad hoc setup steps if the extra tools are missing.
The registry requirements only list pilotctl, while the skill documentation also depends on jq and cron/systemd support.
Requires `pilot-protocol` skill, `pilotctl` binary, running daemon, `jq`, and `cron` or `systemd` timer support.
Declare all required runtime tools in metadata or clearly document installation prerequisites before use.