القائمة
Schedule agents to run on a cron schedule or one-shot at a specific time. The scheduler auto-starts on first add. Triggers on: 'schedule an agent', 'recurring job', 'cron', 'daily', 'every weekday', 'run at 2pm'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Gotchas for the agents-cli headless release. The macOS home base signs, notarizes, and npm-publishes over SSH with no GUI and no Touch ID — three things must be primed or the release stalls. Triggers on: release stuck at sign/publish, errSecInternalComponent, "no npmjs.com bundle", "Missing embedded.provisionprofile", making the release autonomous.
Search, browse, and read agent conversation transcripts across Claude, Codex, Gemini, and OpenCode. Use this skill to find previous sessions, recover context, or inspect what agents have done.
Organize AI coding agents into teams that collaborate on a shared task. Create teams, add teammates, start them, monitor progress, and collect results. Use this skill when you need parallel agent execution. For single-agent dispatch, use `agents run` instead.
Use FIRST for any question about THIS codebase's structure, symbols, or relationships — where a function/class/file is defined, what calls or imports it, what breaks if you change it, how two parts connect, or to load focused source context before editing or reviewing. Routes to the cgraph MCP tools (graph_query / graph_explain / graph_impact / graph_path / graph_context), which serve ranked file:line results, node neighborhoods, transitive blast radius, and token-budgeted source bundles from a resident per-project graph daemon in ~10ms — far cheaper than grepping and reading files. Prefer over blind grep/read for code navigation, dependency tracing, and impact analysis.
Register and connect to your machines over Tailscale SSH with agents-cli. Use this skill to sync devices from the tailnet, list them, open a shell on another machine, or see agent sessions running across your whole fleet.
Execute a single agent headlessly or interactively. Supports plan/edit/auto/skip modes, secrets bundle injection, version pinning, fallback chains, balanced rotation, profile dispatch (Kimi/DeepSeek/etc.), and workflow dispatch by name. Triggers on: 'run claude', 'run codex', 'agents run', 'dispatch an agent', 'headless agent', 'one-off agent task'.
| name | routines |
| description | Schedule agents to run on a cron schedule or one-shot at a specific time. The scheduler auto-starts on first add. Triggers on: 'schedule an agent', 'recurring job', 'cron', 'daily', 'every weekday', 'run at 2pm'. |
| argument-hint | [add|list|run|logs|report|pause|resume|remove] |
| allowed-tools | Bash(agents routines*) |
| user-invocable | true |
Schedule agents to run on a cron schedule or one-shot at a specific time. Routines are YAML jobs that specify which agent runs, when, what task, and execution constraints.
A YAML job with four parts:
The background scheduler auto-starts the first time you add a routine.
# Every weekday at 9 AM
agents routines add daily-standup \
--schedule "0 9 * * 1-5" \
--agent claude \
--prompt "Draft standup from git log"
Cron format is standard 5-field (minute hour day month weekday).
Runs once at a specific time, then disables itself.
# Tomorrow at 2:30 PM
agents routines add hotfix-review \
--at "14:30" \
--agent codex \
--prompt "Review hotfix PR #42"
# Exact date + time
agents routines add launch-check \
--at "2026-06-01 09:00" \
--agent claude \
--prompt "Run launch readiness audit"
For complex routines with multiple settings, author a YAML and reference its path.
agents routines add ./weekly-report.yml
Example weekly-report.yml:
name: weekly-report
schedule: "0 17 * * 5"
agent: claude
mode: edit
effort: high
timeout: 1h
timezone: America/Los_Angeles
prompt: |
Summarize this week's shipped PRs and open issues.
Post the summary to #engineering.
agents routines add backup-job \
--schedule "0 2 * * *" \
--agent claude \
--prompt "Run nightly backup verification" \
--mode edit \
--effort high \
--timeout 1h
| Flag | Default | Values |
|---|---|---|
--mode | plan | plan (read-only), edit (can write files) |
--effort | auto | low | medium | high | xhigh | max | auto |
--timeout | 30m | Duration string (e.g., 30m, 2h) |
Interpret the cron schedule in a specific timezone.
agents routines add london-update \
--schedule "0 9 * * *" \
--timezone Europe/London \
--agent claude \
--prompt "Post morning update to #london"
agents routines add experimental --schedule "0 * * * *" --agent claude --prompt "..." --disabled
agents routines resume experimental
The scheduler auto-starts on first add. Manage manually:
agents routines status # is the scheduler running?
agents routines start # start it
agents routines stop # stop all routines
agents routines scheduler-logs # tail scheduler stdout
agents routines scheduler-logs --follow -n 200
agents routines list # all routines + next run + last status
agents routines view daily-standup
Run in the foreground, ignoring the schedule. Use this to validate prompts before letting them fire on schedule.
agents routines run daily-standup
--run-on <name> places the job body on a host/device over SSH (placement);
--devices restricts which machine's scheduler may fire it (eligibility).
--run-on without --devices auto-pins firing to the adding machine so a
fleet of schedulers can't dispatch duplicates.
agents routines add nightly -s "0 2 * * *" -a claude -p "run the sweep" \
--run-on gpu-box --run-cwd ~/proj
The dispatched run tracks in agents hosts ps (named after the routine) and
the run history finalizes from the remote exit code. Workflow-bundle and
loop: routines can't cross SSH yet and refuse --run-on at add time.
agents routines pause daily-standup
agents routines resume daily-standup
Each fire is recorded as a run. Inspect them:
agents routines runs daily-standup # list recent runs
agents routines logs daily-standup # latest run's stdout
agents routines logs daily-standup --run <id>
agents routines report daily-standup # extract markdown the agent produced
agents routines report daily-standup --run <id>
agents routines edit daily-standup # opens the YAML in $EDITOR
agents routines remove daily-standup
Routines run with the permissions you grant them. Agents only see directories and tools you allow — same model as agents run --mode plan/edit/full. Use --mode plan for routines that should never write.
| Command | Purpose |
|---|---|
add <name> --schedule ... --agent ... --prompt ... | Create cron routine |
add <name> --at "14:30" --agent ... --prompt ... | Create one-shot routine |
add ./file.yml | Create from YAML |
list | All routines + next run |
view <name> | Show routine YAML |
edit <name> | Open routine in $EDITOR |
run <name> | Foreground run (ignores schedule) |
runs <name> | Recent run history |
logs <name> [--run <id>] | Stdout of a run |
report <name> [--run <id>] | Extract markdown output |
pause <name> / resume <name> | Disable / re-enable |
remove <name> | Delete routine |
start / stop / status | Scheduler lifecycle |
scheduler-logs [--follow] [-n N] | Tail scheduler logs |
For everything else, run agents routines --help.