schedulelisted

# Schedule — create a Claude Code Routine for periodic iEvo operations Set up a recurring Claude Code Routine that runs iEvo operations on a schedule — security audits, skill-update checks, or a custom iEvo command. Routines execute on Anthropic-managed infrastructure, so they run even when the local machine is off. Routines are a research preview: behavior, limits, and the surface may change. Routines are created from three surfaces that all write to the same cloud account: the web UI at claude.ai/code/routines, the Desktop app, and the in-session `/schedule` command. This skill drives the `/schedule` path and falls back to the web UI, then to a CI cron template. **Cursor v3.8+ users** have a platform-native alternative: the `/automate` command creates a Cursor Automation directly (including a GitHub "workflow run completed" trigger), no Claude subscription required — see the [Cursor changelog entry](https://cursor.com/changelog/06-18-26) for current syntax. This skill's wizard below still applies for Claude Code Routines, and the CI cron fallback (Step 1b) still applies on Codex and other platforms. ## When to use - User asks "schedule an iEvo audit", "set up weekly security scan", "automate iEvo" - User wants recurring security checks on installed skills after initial install - User wants periodic skill-update discovery so installed skills stay current - After `/ievo:init` — the natural follow-up is "keep this current automatically" - User asks "create a routine for i