Pilot Cron

Scheduled recurring task submission. Use this skill when: 1. You need periodic task execution on a fixed schedule 2. You want automated recurring tasks witho...

This skill appears to do what it claims: schedule scripts that call pilotctl to submit tasks. Before you install or run the provided scripts: 1) Verify pilotctl is the official binary you expect and that the local Pilot daemon and keys are trusted (pilotctl likely uses local config for auth). 2) Ensure jq is installed and available (SKILL.md uses jq but metadata doesn't declare it). 3) Inspect and test any script ($HOME/.pilot/cron-jobs/*) so they don't perform unexpected actions. 4) Be aware that adding cron or systemd timers creates persistent jobs that will run with your user privileges and perform network calls—only allow this if you trust the scripts and the Pilot network endpoints. 5) If you don't want persistent jobs, run scripts manually or in an isolated environment first. If you want a stricter assessment, provide the pilotctl implementation details or the expected auth flow (where keys are stored), and confirm whether jq/cron/systemd should be declared as required binaries.

Type: OpenClaw Skill Name: pilot-cron Version: 1.0.0 The skill provides instructions and examples for establishing system persistence via `crontab` and `systemd` user timers in `SKILL.md`. While these capabilities are aligned with the stated purpose of 'Scheduled recurring task submission,' they represent high-risk behaviors that allow for persistent execution on the host. The workflow example also demonstrates automated task submission to remote peers using the `pilotctl` binary, which could be leveraged for unauthorized remote execution if the agent is misconfigured.