setup-cron

Configures unattended daily scheduling of LeadAce outreach cycles across server, desktop, and OS schedulers.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/aitit-inc/leadace --skill setup-cron-aitit-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-cron
Source: https://github.com/aitit-inc/leadace/tree/main/plugin/skills/setup-cron
Command: npx skills add https://github.com/aitit-inc/leadace --skill setup-cron-aitit-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running a daily outbound sales cycle manually every day is repetitive and easy to forget. This Skill sets up an unattended daily run of the LeadAce daily-cycle command so prospecting, email outreach, reply checking, and evaluation happen automatically on a schedule. ## Core Features & Use Cases - Multiple scheduling methods: Chooses between a server-side schedule (no machine needed), a Claude Cowork scheduled task, a Claude Code Desktop routine, a /loop command, or an OS scheduler (LaunchAgent, cron, Task Scheduler) as a last resort. - Per-project schedules: One schedule per project, with project-slug-based naming so schedules for different projects coexist and can be replaced or removed independently. - Cross-platform templates: Generates ready-to-install plist, crontab, and Windows Task Scheduler entries with correct working directory, environment variables, and log files, then verifies installation. - Use Case: A sales founder wants their LeadAce project to email new prospects every weekday at 9 AM without lifting a finger. The Skill confirms the project and time, recommends the server-side schedule, and walks them through registering it — or installs a LaunchAgent on their Mac if they need browser channels. ## Quick Start Ask the assistant to schedule the daily cycle for your project every weekday at 9 AM, and it will guide you through picking and installing the right scheduling method.

Frequently Asked Questions about setup-cron

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule the LeadAce daily cycle to run automatically?

Run the setup-cron skill with your project name, then pick a scheduling method. The recommended option is the server-side schedule configured in the LeadAce web app under Project settings -> Scheduled runs, which needs no machine running.

How to run a Claude Code command on a cron schedule?

The skill generates a crontab line that runs claude -p with your command, --permission-mode dontAsk, and an absolute CLI path. It sets the working directory and a log file, then installs the line by replacing any existing tagged entry.

Can the scheduled daily cycle send contact form messages and SNS DMs?

Server-side schedules have no browser, so contact forms, SNS DMs, and platform channels do not run. For browser channels, use a Claude Cowork or Claude Code Desktop scheduled task with the Claude Desktop app open at run time.

Why does my headless scheduled run fail or abort?

Headless runs cannot answer permission prompts, so any tool without a stored allow rule is denied and repeated denials abort the run. Run the daily cycle interactively once, answering always allow, and note the MCP OAuth token expires after about 30 days of inactivity.

Does the scheduled task run when my computer is asleep or closed?

Claude Code Desktop routines run only while Claude Desktop is open and the computer is awake; enable Keep computer awake in settings. After missed runs, exactly one catch-up run starts on wake. Server-side schedules avoid this entirely.

Can I schedule daily cycles for multiple projects?

Yes, one schedule per project, and schedules for different projects coexist. Every installed artifact embeds the project slug in its label, file name, crontab tag, and log files so replace and remove operations touch only their own project.