Run recurring checks with /loop and /schedule

The problem

You want Claude to re-check a flaky deploy, watch logs, or nudge a migration every N minutes, but glueing external cron to interactive sessions is brittle.

The hack

Invoke the bundled `/loop` or `/schedule` skill to describe the cadence and the check. Claude re-runs the workflow on the interval inside the product’s scheduling model.

Why it works

Official power-user tips list /loop and /schedule as first-party recurring-task tools — prefer them before inventing shell cron wrappers around `claude -p`.

Setup

1. Run `/help` and confirm `/loop` and `/schedule` are available (org policy may disable cloud scheduling). 2. Start with `/loop` and describe: interval, success criteria, and what to do on failure. 3. For cloud/recurring jobs, use `/schedule` when enabled for your plan. 4. Keep checks idempotent and permission-safe (pair with auto mode or allowlists).

Source

Related

• → Schedule a morning repo-health brief with headless Claude
• → Run Claude headless in CI with --print and JSON output