# Manage Schedules

> Manage scheduled tasks for Talon personas. Use when the user says "add schedule", "create schedule", "list schedules", "remove schedule", "scheduled task", or "cron job".

- Skill: `ivo-toby/manage-schedules` (Agent Skill)
- Install (CLI): `npx get-skill add ivo-toby/manage-schedules`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ivo-toby/manage-schedules/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: ivo-toby (https://skillmd.com/u/ivo-toby)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/ivo-toby/manage-schedules

---


# Manage Schedules

Guide the user through creating, listing, or removing scheduled tasks.
Schedules live in the database (not the config file) and require a running daemon to fire.

## Phase 1: Determine Action

Ask what they want to do:
1. **Create** a new scheduled task
2. **List** existing schedules
3. **Remove** a schedule

## Phase 2a: Create Schedule

1. Run `npx talonctl list-personas` to show available personas.
2. Ask which persona should run the task.
3. Run `npx talonctl list-channels` to show available channels.
4. Ask which channel to bind the schedule to (this creates a thread for the schedule on that channel).
5. Ask for the cron expression. Offer common presets:
   - Every hour: `0 * * * *`
   - Twice daily (9am, 9pm): `0 9,21 * * *`
   - Daily at 9am: `0 9 * * *`
   - Every Monday at 9am: `0 9 * * 1`
   - Every 30 minutes: `*/30 * * * *`
6. Ask for a label (short name like `memory-grooming` or `git-pull-notes`).
7. Ask for the prompt (what the agent should do when triggered).
8. Run: `npx talonctl add-schedule --persona <name> --channel <channel> --cron "<expr>" --label "<label>" --prompt "<prompt>" --config talond.yaml`
9. Confirm with schedule ID and next run time.

## Phase 2b: List Schedules

Run: `npx talonctl list-schedules --config talond.yaml`
Optionally filter: `--persona <name>`

## Phase 2c: Remove Schedule

1. Run `npx talonctl list-schedules` to show existing schedules.
2. Ask which schedule to remove (by ID).
3. Run: `npx talonctl remove-schedule <id> --config talond.yaml`

## Notes

- Schedules fire in system local time (CET on the VM).
- Schedule output is silent -- the agent only sends messages if it explicitly uses channel.send.
- Scheduled runs are one-shot and short-context: they do not use thread provider affinity, resume provider sessions, replay schedule-thread history, run context rotation, or store skipped final wrap-up text as outbound messages. Explicit channel.send deliveries are stored on the live recipient thread so replies have context.
- Scheduled runs created from the CLI (`talonctl add-schedule`) have no `originExternalId` in their schedule-thread metadata, so `channel_send` cannot infer a recipient chat. In that case the agent must either (a) pass `externalChatId` explicitly to `channel_send` after discovering it via `channel_list`, or (b) call `channel_broadcast` to fan out to every chat the persona is bound to. Broadcasts skip channel-default bindings (no `thread_id`) with a warning; the result includes `{ delivered, skipped, failed }` so the agent can tell the user which channels were unreachable.
- The daemon must be running for schedules to fire (they live in the DB, not the config).
- After creating schedules, remind the user: schedules require a running daemon to execute.

