schedule

Schedule Skill

Manage cron-based scheduled tasks that deliver messages to the tinysdlc incoming queue. Each schedule fires at a cron interval and writes a routed message (@agent_id <task>) to queue/incoming/, where the queue processor picks it up and invokes the target agent.

Commands

Use the bundled CLI scripts/schedule.sh for all operations.

Create a schedule

scripts/schedule.sh create \
  --cron "EXPR" \
  --agent AGENT_ID \
  --message "Task context for the agent" \
  [--channel CHANNEL] \
  [--sender SENDER] \
  [--label LABEL]

• --cron — 5-field cron expression (required). Examples: "0 9 * * *" (daily 9am), "*/30 * * * *" (every 30 min), "0 0 * * 1" (weekly Monday midnight).
• --agent — Target agent ID (required). Must match an agent configured in settings.json.
• --message — The task context / prompt sent to the agent (required).
• --channel — Channel name in the queue message (default: schedule).
• --sender — Sender name in the queue message (default: Scheduler).
• --label — Unique label to identify this schedule (default: auto-generated). Use a descriptive label for easy management.

List schedules

scripts/schedule.sh list [--agent AGENT_ID]

Lists all tinysdlc schedules. Optionally filter by --agent to show only schedules targeting a specific agent.

Delete a schedule

scripts/schedule.sh delete --label LABEL
scripts/schedule.sh delete --all

Delete a specific schedule by label, or delete all tinysdlc schedules.

Workflow

1. Confirm the target agent ID exists (check settings.json or ask the user).
2. Determine the cron expression from the user's description (e.g., "every morning" → "0 9 * * *").
3. Compose a clear task message — this is the prompt the agent will receive.
4. Run scripts/schedule.sh create with the parameters.
5. Verify with scripts/schedule.sh list.

Cron expression quick reference

┌───────────── minute (0-59)
│ ┌───────────── hour (0-23)
│ │ ┌───────────── day of month (1-31)
│ │ │ ┌───────────── month (1-12)
│ │ │ │ ┌───────────── day of week (0-7, 0 and 7 = Sunday)
│ │ │ │ │
* * * * *

Examples

Daily report

scripts/schedule.sh create \
  --cron "0 9 * * *" \
  --agent analyst \
  --message "Generate the daily metrics report and post a summary" \
  --label daily-report

Periodic health check

scripts/schedule.sh create \
  --cron "*/30 * * * *" \
  --agent devops \
  --message "Run health checks on all services and report any issues" \
  --label health-check

Weekly code review reminder

scripts/schedule.sh create \
  --cron "0 10 * * 1" \
  --agent coder \
  --message "Review open PRs and summarize status" \
  --label weekly-pr-review

List and clean up

# See all schedules
scripts/schedule.sh list

# See only schedules for @coder
scripts/schedule.sh list --agent coder

# Remove one
scripts/schedule.sh delete --label health-check

# Remove all
scripts/schedule.sh delete --all

How it works

• Schedules are stored as system cron entries tagged with # tinysdlc-schedule:<label>.
• When a cron job fires, it writes a JSON message to queue/incoming/ with the @agent_id routing prefix.
• The queue processor picks up the message and invokes the target agent, exactly like a message from any channel.
• Responses appear in queue/outgoing/ and can be consumed by channel clients.

For queue message format details, see references/queue-format.md.