aii-schedule-job

Use this Skill whenever work should repeat on a cadence, such as nightly syncs or weekly sweeps. It names the job by outcome, picks a hosted or local runtime, writes an opening gate that resolves tools by category, and proves the job with one real run before calling it live.

Tool addresses are facts about one installation on one day and silently change when connectors re-provision. Resolving by category and action against the client's registry returns a candidate set of live addresses, so the job keeps working when any single address goes stale.

Default to hosted, because a local job stops when the operator's machine is off and can hang silently on permission prompts. Choose local only when the job must touch operator files, and record that as reach equals operator-files with a hosted route owed.

The schedule lives as a row in the tenant's store, not inside one account, so any awake executor on any signed-in platform can claim it atomically. A lease ensures a dead executor releases the job back to the queue instead of stranding it.

Do not schedule one-off work in the current session, steps a human must run on their own machine, or polling inside an open conversation. Do the one-off work immediately and offer the schedule afterward, or route human-run steps through a run-command skill.

Without an alive stamp written at claim time, a job that dies in its opening gate is indistinguishable from one that never fired. One real run confirming tool resolution, landed work, and written state is required before the job may be reported as live.