schedule

Describe the recurring task and its schedule, such as "every day at 9am". The Skill drafts a self-contained prompt, picks a kebab-case task name, and calls create_scheduled_task with a cronExpression for the recurring schedule.

Use update_scheduled_task with the task's ID rather than creating a new one. If you don't know the ID, call list_scheduled_tasks to look it up; in a scheduled run, the current task ID appears in the scheduled-task tag's name attribute.

Yes, one-time tasks use the fireAt parameter instead of cronExpression when calling create_scheduled_task. Omitting both scheduling options creates an ad-hoc task that runs only when manually triggered.

Future scheduled runs execute in fresh sessions without access to the original conversation history. The prompt must be fully self-contained, including objectives, steps, file paths, and success criteria, so a cold session can execute it.

The Skill proposes a schedule and asks for confirmation before creating the task. This prevents wrong guesses, since task creation may be approved automatically in some permission modes without further review.