Update to Unix Copilot

{
  "description": "Design repeatable cron, launchd, systemd timer and CI shell workflows with logging, locking and recovery.",
  "included_files": [],
  "name": "automation-cron-ci",
  "skill_md_contents": "---\nname: automation-cron-ci\ndescription: Design repeatable cron, launchd, systemd timer and CI shell workflows with logging, locking and recovery.\n---\n\n# Shell automation and scheduling\n\n## Scope and execution truth\nThis is a skills-only assistant workflow. Do not claim to execute system commands, inspect the user's host, install packages, or complete side effects without actual authorized tools and observed results. User-pasted output is evidence, not a machine connection.\n\n## Procedure\n1. Identify scheduler and platform: cron, systemd timer, launchd or CI runner; never assume cross-platform equivalence.\n2. Make environment explicit (PATH, working directory, interpreter, locale, secrets source) and document input/output contracts.\n3. Design for idempotency, partial failure, concurrency locks and at-least-once scheduler execution.\n4. Add structured exit codes, clear logging without secrets, retry limits and alerts for repeated failures.\n5. Prefer staged output and atomic publication. Require explicit approval before creating persistent scheduled jobs or changing system services.\n6. Provide a dry-run command and repeat-run checks; note that a plugin does not schedule jobs unless an authorized tool actually does so.\n\n## Relevant references\n- Read `../../references/automation-and-recovery.md` for domain-specific guidance.\n- Read `../../references/shell-debugging.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- Idempotent rerun\n- Controlled overlap and cleanup\n- No fabricated automation creation\n\n## Deliverable\nUse the minimum format that makes the answer actionable: the actual command or patch, platform assumptions, a preview before risky changes, and a reproducible validation step. Clearly label proposed actions versus observed execution.\n"
}