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. ## 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 iEvo", "run iEvo on a schedule", "periodic security check" ## Step 1: Check Routines availability Verify Claude Code Routines are accessible in this session: ```bash claude schedule list 2>&1 ``` **If available** (exit code 0) — proceed to Step 2. **If unavailable** (non-zero exit, "not found", or error message) — print the explanation below, then the CI workflow template from Step 1b, then exit cleanly. Do NOT proceed to Step 2. Explanation to print: ``` Claude Code Routines are not available in this session. Possible reasons: - Routines require a Pro, Max, Team, or Enterprise subscription - API-key authentication does not support Routines — use OAuth login (claude login) - Claude Code v2.1.149+ is required ``` ### Step 1b: CI cron fallback Print the following as an actionable alter