spell-schedulelisted

Schedule a moflo spell to run on the local machine via the moflo daemon (cron, interval, or one-time). Use when the user wants to schedule, automate, or recurringly run one of THEIR spells locally — e.g. "schedule the oap spell every hour", "run my audit spell every weekday at 9am", "fire X once tomorrow morning". This is the LOCAL daemon path. For remote Anthropic-cloud agents, use /schedule instead.
eric-cielo/moflo · ★ 18 · AI & Automation · score 81

Install: claude install-skill eric-cielo/moflo

# /spell-schedule — Schedule a Local Spell This skill walks the user through scheduling a moflo spell on the **local** moflo daemon. Schedules live in moflo's memory store and are evaluated once per minute by the daemon's poll loop. Execution goes through the same engine path as `flo spell cast`. > Not the same as `/schedule`. `/schedule` creates **remote** Anthropic-cloud routines; this skill drives the **local** daemon scheduler. **Arguments:** `$ARGUMENTS` (optional spell name/alias to pre-select) ## When to use The user says any of: - "schedule the X spell" - "run X every <interval>" - "fire X once at <time>" - "set up a recurring run for X" - "I want X to run every morning" If the user wants a **cloud** agent (mentions "remote", "GitHub Actions", "Anthropic cloud", or specifies a repo to clone), redirect them to `/schedule`. ## Workflow ### Step 1 — Verify the daemon is running ```bash npx flo doctor 2>&1 | grep -i daemon ``` If the daemon is not running, prompt the user: - "The moflo daemon isn't running. Schedules only fire while the daemon is up. Start it now?" - If yes: `npx flo daemon start`. - If they decline, warn the user that the schedule will be created but won't fire until the daemon is started. OS-native autostart (launchd / systemd / Task Scheduler) is **automatic**: the first `flo spell schedule create` registers the daemon as a login service so schedules survive reboot, and the cancel that takes the enabled-schedule count to 0 unregisters it. Us