Cron

Scheduled Task Skill

Manage scheduled tasks for the current conversation with the bundled agent-facing config CLI.

Rules

1. Each conversation can have at most one scheduled task.
2. Always query existing tasks before creating or updating.
3. Do not ask for extra confirmation after the user has already requested the scheduling change.
4. Never pass, inline, export, echo, or set any AIONUI_... environment variable.
5. Commands must directly call "$AIONUI_HELPER_BIN" config cron current ....
6. Pass create and update payloads through stdin heredocs attached to the command. Do not write payload JSON files to disk.
7. Put job_id in the update JSON payload, not in a command flag.
8. After a successful create or update, send one short final confirmation that a normal user can understand. Include the task name and schedule description. Do not show internal ids such as cron_....
9. If the CLI fails, report the failure from stderr/stdout in normal prose and do not claim the task was created.

Workflow

1. Run "$AIONUI_HELPER_BIN" config cron current list.
2. If the returned data array is empty, create the task with "$AIONUI_HELPER_BIN" config cron current create <<'JSON'.
3. If one task exists and the user wants to change it, update that task with "$AIONUI_HELPER_BIN" config cron current update <<'JSON'.
4. If a task already exists and the user is asking for a different additional task, ask how they want to handle the existing task.
5. Report success or failure from the CLI output in normal prose, following the final confirmation rule above.

Payload

Create payload:

• name: Short descriptive name.
• schedule: Standard 5-field cron expression.
• schedule_description: Human-readable schedule.
• message: Complete, self-contained instruction sent to the AI when the task runs.

Update payload uses the same fields and also requires:

• job_id: The id from the existing task returned by the list command.

The message must tell the AI exactly what to do when the task fires. It should not merely restate the user's scheduling request.

Examples

Examples use English sample text. For real tasks, write the task name, schedule description, and message in the user's language.

Query:

"$AIONUI_HELPER_BIN" config cron current list

Create:

"$AIONUI_HELPER_BIN" config cron current create <<'JSON'
{
  "name": "Weekly Meeting Reminder",
  "schedule": "0 9 * * MON",
  "schedule_description": "Every Monday at 9:00 AM",
  "message": "Reply with a short weekly meeting reminder that includes the current date and time."
}
JSON

Update:

"$AIONUI_HELPER_BIN" config cron current update <<'JSON'
{
  "job_id": "cron_123",
  "name": "Daily Summary",
  "schedule": "0 18 * * MON-FRI",
  "schedule_description": "Weekdays at 6:00 PM",
  "message": "Review today's conversation context and produce a concise end-of-day summary."
}
JSON

Multiline message example:

{
  "name": "Daily Summary",
  "schedule": "0 9 * * *",
  "schedule_description": "Every day at 9:00 AM",
  "message": "First paragraph.\nSecond paragraph.\nThird paragraph."
}

Cron Expression

Format: minute hour day-of-month month day-of-week.

Example: 0 9 * * MON-FRI means weekdays at 9:00 AM.

Use only standard cron fields and ranges supported by the backend parser. Do not use Quartz-style extensions such as L, L-N, W, LW, #, or ?.