schedules

Name: schedules
Availability: InStock
Author: Istota

Manage recurring cron-based jobs for Istota automated workflows.

10|Updated Feb 17, 2026

Search Tags:#automation #workflow #toml #schedule #cron #recurring

Ready to run

npx skills add https://github.com/istota-project/istota --skill schedules-istota-project

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schedules
Source: https://github.com/istota-project/istota/tree/main/src/istota/skills/schedules
Command: npx skills add https://github.com/istota-project/istota --skill schedules-istota-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Istota's scheduling skill centralizes the management of recurring tasks for bot workflows, ensuring consistent execution and persistence of job definitions across restarts.

Core Features & Use Cases

Persistent cron-based jobs: Define recurring tasks via a TOML block in the user's CRON.md, which the scheduler reads automatically.
Flexible job definitions: Each job supports name, cron expression, prompt or command, delivery target (talk or email), and runtime controls like enabled, once, and silent_unless_action.
Use Case Examples: Schedule a daily report, periodic data synchronization, or reminder actions that run automatically and deliver results to the appropriate channel.

Quick Start

Edit the file at $NEXTCLOUD_MOUNT_PATH/Users/$ISTOTA_USER_ID/{BOT_DIR}/config/CRON.md to add or modify the [[jobs]] entries and enable the desired recurring tasks.

Frequently Asked Questions about schedules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I schedule recurring tasks using cron expressions for automated workflows?▼

To schedule recurring tasks, define cron-based job entries in a TOML-formatted CRON.md file, specifying the job name, cron expression, prompt or command, and delivery target for persistent automated execution.

What is the file format required to define cron jobs in BOT_DIR configurations?▼

The required file format is a TOML block within a CRON.md file, using [[jobs]] entries to establish recurring tasks with options like name, cron, prompt, command, target, room, enabled, once, and silent_unless_action.

Can I send automated task results to different delivery targets like email or chat?▼

Yes, you can route automated task results to different delivery targets by specifying either 'talk' or 'email' in the target option of your TOML job definition within the CRON.md file.

How do I run a scheduled task only once instead of making it a recurring cron job?▼

Set the 'once' option to true in your [[jobs]] TOML entry to execute the task a single time, overriding its default recurring cron behavior while maintaining job persistence.

Why do my scheduled cron jobs stop running after a system restart?▼

Scheduled cron jobs stop after restarts if they are not defined in the persistent CRON.md file, which the scheduler reads automatically to restore and manage recurring task definitions across restarts.

Do I need to configure anything before silent scheduled tasks can trigger notifications?▼

To receive notifications for silent tasks, configure the 'silent_unless_action' runtime control in your TOML job entry, ensuring delivery occurs only when specific actions generate output.