schedule_skill

Overview

This skill programs any recurring or one-time task with a focus on keeping simple requests simple. It handles daily reports, reminders, checks, and more complex flows only when you ask. The interface confirms actions succinctly and then executes without unnecessary setup.

How this skill works

You tell the skill what to run and when, and it creates a scheduled job with a clear confirmation including what, when (with timezone), and an ID. It supports one-shot reminders, interval jobs, cron-style schedules, conditions, and delivery options like notifications or silent logging. The skill asks follow-up questions only if the request is genuinely ambiguous and remembers answers like preferred morning time and timezone.

When to use it

• Create a recurring daily, weekly, or cron-style task (e.g., daily report at 8am).
• Set a one-time reminder (e.g., remind me Friday at 3pm).
• Schedule frequent checks or monitoring jobs (e.g., check X every hour).
• Add conditions or delivery preferences when needed (e.g., skip if empty, log silently).
• Manage existing routines: list, pause, resume, edit, or cancel by name or ID.

Best practices

• Keep initial requests simple; add conditions or chaining only when necessary.
• Provide clear time expressions or allow the skill to ask one clarifying question.
• Name schedules with meaningful IDs for easy editing and cancellation.
• Use default preferences (timezone, morning hour, notification style) to avoid repeated prompts.
• Review active jobs periodically with the built-in list command to stay organized.

Example use cases

• Every morning send me a summary of unread emails at a remembered reasonable hour.
• Remind me tomorrow at a specified hour to attend a meeting (one-shot).
• Check server status every 15 minutes and notify only on failures (conditional).
• Run a weekly report every Friday at 5pm and email the results to the team.
• Pause a recurring job for holiday periods and resume it later by ID or name.