create-system-routine

Create System Routine

When to use this skill

Use this skill when the user wants to create or manage time-based routines (scheduled tasks) at the OS level (e.g., running a shell script, a binary, or a specific command).

• Linux → use cron (crontab -e, system/user crontabs)
• macOS → use launchd (LaunchAgents / LaunchDaemons with plist files)
• Windows → this skill should not create routines; instead, explain that Windows Task Scheduler must be configured manually.

Security

A scheduled routine runs unattended, in the invoking user's context, with no terminal and no chance to answer a prompt.

• Never inline secrets (API keys, tokens, passwords) in the cron line or plist. Load them from a file with restricted permissions (e.g. chmod 600) inside the wrapped script, or from the environment.
• Prefer wrapping the real work in a script and calling that script. This keeps PATH, environment, and error handling in one auditable place.
• The routines this skill creates are user-level and run with the user's privileges. Do not schedule commands that escalate privileges or mutate system state without explicit confirmation.
• Always explain what will change and keep a backup (e.g. crontab -l > /tmp/crontab.bak) before any destructive edit.

Workflow

1. Detect the operating system

   Use standard OS detection via shell commands:

   uname_s=$(uname -s 2>/dev/null || echo unknown)
   case "$uname_s" in
     Linux)   os=linux ;;
     Darwin)  os=macos ;;
     MINGW*|MSYS*|CYGWIN*|Windows_NT) os=windows ;;
     *)       os=unknown ;;
   esac
   

   • If os=linux → follow the Linux / cron workflow.
   • If os=macos → follow the macOS / launchd workflow.
   • If os=windows or os=unknown → explain that this skill does not create routines on this OS and suggest Windows Task Scheduler or another platform-specific mechanism.

2. Gather routine parameters from the user (questionnaire if needed)

   Do not create the cron entry or plist until you have enough information. If the user's request is vague (e.g. "schedule something", "run a script daily") or missing any of the items below, guide them through a short questionnaire instead of guessing.