菜单
Decision framework for agents to determine WHEN and WHETHER to use Claude Code's native cron scheduler (CronCreate/CronList/CronDelete) vs OS cron, GitHub Actions, or simple Task() delegation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oimiragieo/agent-studio --skill cron-decision命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cron-decision |
| version | 1.0.0 |
| description | Decision framework for agents to determine WHEN and WHETHER to use Claude Code's native cron scheduler (CronCreate/CronList/CronDelete) vs OS cron, GitHub Actions, or simple Task() delegation. |
| category | Infrastructure |
| tags | ["cron","scheduling","decision","heartbeat","github-actions","os-cron"] |
| tools | ["CronCreate","CronList","CronDelete","TaskCreate","Read","Bash"] |
| agents | ["developer","heartbeat-orchestrator","planner","architect"] |
| invoked_by | agent |
| user_invocable | false |
| model | sonnet |
| error_handling | graceful |
| verified | true |
| source | builtin |
| trust_score | 100 |
| provenance_sha | f10e877f6b0f2fb9 |
Official docs: https://code.claude.com/docs/en/scheduled-tasks
Help agents decide when and whether to use Claude Code's native cron scheduler (CronCreate/CronList/CronDelete) versus alternatives like OS cron (crontab), GitHub Actions scheduled workflows, or simple one-shot Task() delegation.
Using the wrong scheduling mechanism leads to:
Answer these 5 questions in order. The FIRST "yes" that hits a stop condition determines your tool.
Is the task a one-time operation?
TaskCreate or Task(). Stop here. CronCreate is for recurring work only.Must the task survive terminal/session close?
crontab -e) or GitHub Actions. CronCreate is session-scoped and dies when Claude Code closes.Does the task require sub-15-minute precision or hard time guarantees?
Is this a heartbeat loop or session-scoped health check?
Is this triggered by an event rather than a clock?
| Scenario | Recommended Tool | Reason |
|---|---|---|
| Periodic background monitoring during active session |
CronCreate |
| Session-scoped is fine; this is CronCreate's primary use case |
| Agent ecosystem heartbeat (health checks, memory sizes) | CronCreate via heartbeat-orchestrator | Use dedicated orchestrator, not raw CronCreate |
| One-time task (now or delayed) | Task() or TaskCreate | Cron is for recurring work only |
| Nightly backup or data pipeline | OS cron (crontab -e) | Must survive terminal close |
| CI/CD pipeline trigger | GitHub Actions schedule: | Cloud-run, no terminal dependency |
| Data refresh every 4 hours during development | CronCreate | Session-scoped is acceptable for dev workflows |
| Production scheduled job | OS cron or GitHub Actions | Never rely on session-scoped for production |
| Event-driven reaction (file change, hook trigger) | Hook (PreToolUse/PostToolUse) | Time-based scheduler is wrong tool for events |
| User-requested one-off analysis | Task() | Single execution, no recurrence needed |
| Weekly report generation (must run unattended) | GitHub Actions | Unattended, cloud-run, persistent |
| Session index rebuild during development | CronCreate | Session-scoped is fine; fires while Claude is open |
| Reflection queue drain check | CronCreate via heartbeat-orchestrator | Part of heartbeat ecosystem |
If the recurring task is agent ecosystem monitoring (health checks, memory rotation, stuck task detection, reflection queue), do not use raw CronCreate directly.
Instead, delegate to heartbeat-orchestrator or invoke the /heartbeat-start command:
// CORRECT: Delegate heartbeat ecosystem to the dedicated orchestrator
// Router: spawn heartbeat-orchestrator agent
// OR user: /heartbeat-start
// WRONG: Manually wiring raw CronCreate for ecosystem health
CronCreate({
schedule: '*/30 * * * *',
task: 'Check agent health...',
});
The heartbeat-orchestrator manages:
heartbeat-session-ping.jsonException: Use raw CronCreate only for custom, non-ecosystem recurring tasks that are not part of the standard heartbeat loops.
| Constraint | Detail |
|---|---|
| Session-scoped | Dies when terminal closes — no persistence across restarts |
| 3-day auto-expiry | Self-deletes silently after 3 days (reschedule before day 2.5) |
| Jitter | Fires up to 10% of period late (max 15 min) |
| No catch-up | Missed fires are NOT replayed |
| 50-task cap | Max 50 concurrent scheduled tasks per session |
| Fire-between-turns | Fires only when Claude is idle, not mid-response |
| No extended syntax | L, W, ?, MON-style names are NOT supported |
CronCreate whencrontab -e) whenschedule: whenTask() or TaskCreate when// Schedule a recurring task (standard 5-field cron expression)
CronCreate({ schedule: '*/30 * * * *', task: 'Heartbeat check prompt here' });
// List active cron tasks (verify what is registered)
CronList();
// Remove a scheduled task by ID
CronDelete({ id: 'abc12345' });
Common schedules:
| Expression | Meaning |
|---|---|
*/30 * * * * | Every 30 minutes |
*/5 * * * * | Every 5 minutes (minimum recommended) |
0 * * * * | Every hour on the hour |
0 2 * * * | Every day at 2am local time |
0 3 * * 0 | Every Sunday at 3am |
Skill({ skill: 'cron-decision' });
Invoke before:
Do NOT invoke for:
TaskCreate directly)heartbeat-orchestrator or /heartbeat-start)scheduled-tasks — Full CronCreate implementation reference with heartbeat patternsheartbeat — Start the full 7-loop heartbeat ecosystemheartbeat-orchestrator agent — Manages ecosystem heartbeat loopsBefore starting:
Read .claude/context/memory/learnings.md for previous scheduling decisions.
After completing:
.claude/context/memory/learnings.md.claude/context/memory/issues.md.claude/context/memory/decisions.mdASSUME INTERRUPTION: If it's not in memory, it didn't happen.