scheduling

The scheduling skill for LettaBot provides a powerful framework for time-based automation, enabling users to create persistent, recurring jobs or precise one-off reminders directly within their AI assistant. Designed for users who need to maintain daily routines, weekly workflows, or immediate follow-up tasks, this skill leverages cron syntax for complex frequency management and ISO 8601 datetime strings for absolute precision. By integrating deeply with LettaBot's core, it ensures that your agent can trigger notifications, agenda prompts, or task executions across multiple communication channels including Telegram, Slack, Discord, WhatsApp, and Signal.

• Create one-off reminders using specific future timestamps to ensure time-sensitive tasks are never missed.

• Configure recurring schedules with full support for standard cron syntax (minute, hour, day of month, month, day of week).

• Automatically deliver job outputs to your preferred communication channel, with a smart default to the last active conversation.

• Perform administrative tasks via CLI, including listing active jobs, deleting entries, and toggling job status without requiring agent restarts.

• Support for custom task messaging and flexible scheduling enables complex workflows like daily morning briefings, weekly reviews, or hourly status checks.

• Use --at with ISO datetime formats for one-off reminders; these tasks are designed to auto-delete upon completion to keep your job registry clean.

• Leverage --schedule with five-field cron expressions for reliable recurring operations.

• Ensure you calculate datetimes correctly using JavaScript or shell utilities to prevent scheduling errors.

• The system persists jobs in a local cron-jobs.json file, maintaining state across server restarts for high reliability.

• Keep in mind that job names must be unique and relevant to the task; messages should provide sufficient context for when the notification arrives on your device.

• Default communication channels are handled contextually, but you can explicitly define destinations using the channel:chatId format.