Agent Scheduled Tasks

Use when creating, changing, debugging, or proving an agent-owned scheduled task, automation, cron, reminder, or heartbeat.

adsagents Updated

File contents

Agent Scheduled Tasks

  1. Classify the job as reminder/heartbeat, auditable execution, or consequential execution.
  2. Resolve timezone, cadence, destination, stable scope, allowed tools, evidence, retry budget, and stop conditions before creating it.
  3. Use the actual scheduler interface once, then read back its stored contract.
  4. Run now only when supported and record the scheduler plus downstream evidence separately.
  5. Never put credentials in the prompt, guess permissions, or treat schedule creation as execution proof.
  6. Treat a matching delivery prepare as the live preflight. Consume inline verification first and use the advertised native operation fallback only when recovery remains pending; a missing optional selector before mutation does not disable read-only schedule evaluation.
  7. For explicit Meta candidates, batch up to 50 exact IDs with overview_get_live_configs; correlate only by entity_type and entity_id.

Read scheduled-task-contract.md only when designing, creating, updating, debugging, pausing, deleting, or proving a scheduled task.

adsagents/adsagent-ai-skills commit 5edff4a24a

Frequently asked questions

npx get-skill add adsagents/agent-scheduled-tasks