setup-cronlisted

# Setup-cron - Schedule Daily Automation A skill that wires `/daily-cycle` into the user's OS scheduler so it runs every day without manual invocation. The skill is **idempotent**: re-running it replaces any existing LeadAce schedule entry. The skill writes one of: - macOS LaunchAgent at `~/Library/LaunchAgents/ai.leadace.daily-cycle.plist` - Windows scheduled task named `LeadAceDailyCycle` - Linux user crontab line tagged `# leadace-daily-cycle` Or, if the user prefers in-Claude-Code scheduling, it explains how to use the plugin's existing `/loop` skill or Claude Code's built-in `/schedule` (Remote Trigger). ## Prerequisites - The user has already run `/setup` and has at least one project. If not, abort and ask them to run `/setup` first. - The `claude` CLI is on `PATH` (required for OS-level scheduling). The skill verifies this with `which claude`. - The user has an active Claude Code session with a valid LeadAce MCP OAuth token. **Headless `claude` invocations cannot complete OAuth interactively** — if the token expires (currently every 30 days, sliding), the next scheduled run fails until the user signs in again. ## Steps ### 1. Pick the project If `$0` is given, use it. Otherwise call `mcp__plugin_lead-ace_api__list_projects` and: - If exactly one project exists, use it. - If multiple exist, ask via `AskUserQuestion`. - If none, abort: "No projects yet. Run `/setup <project-name>` first." Hold the chosen name in `PROJECT_NAME`. ### 2. Pick the scheduling method