pi-automation
Design safe, observable scheduled and event-triggered Pi automation workflows. Use when the task concerns pi automation.
SKILL.mdpi/agent/skills/pi-automation/SKILL.md
GitHubPi automation
- Choose one trigger: systemd user timer, systemd path unit, CI webhook, or
agents-cron(optional). Avoid stacking schedulers for the same job. - Specify project cwd, input, output artifact, max runtime, budget, and retry policy.
- Use a read-only isolated invocation by default.
pi --printcan run headlessly; model tool availability/permissions must be deliberately restricted. - Validate arguments/paths. Persist run id, exit code, stdout/stderr redacted, timestamps, and a bounded report. Ensure repeated jobs are idempotent.
- Do not grant unattended write/network-mutation capabilities by default.
- Prefer
systemctl --usertimers on Arch Linux;agents-cronis an optional Pi-native scheduler requiring an external cron trigger. - Never paste provider secrets or environment contents into prompts or logs.
See ~/.pi/agent/examples/systemd/ for an opt-in sample user timer. It is disabled
until the operator installs/enables it.