scheduling-skill

Schedule one-off and recurring agent tasks with cron-like expressions.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/misunders2d/ori --skill scheduling-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scheduling-skill
Source: https://github.com/misunders2d/ori/tree/main/skills/scheduling-skill
Command: npx skills add https://github.com/misunders2d/ori --skill scheduling-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scheduling and enforcing tasks across agents and channels with reliable delivery, reducing missed deadlines and manual coordination.

Core Features & Use Cases

  • Schedule one-off reminders and recurring tasks with cron-like expressions.
  • Route results to Slack or Telegram channels, with plan-enforcement to ensure consistency across fires.
  • Maintain audit trails, next_run visibility, and robust error handling for reliability.

Quick Start

Schedule a one-off reminder for tomorrow at 16:00 in Europe/Kyiv and specify the delivery channel.

Frequently Asked Questions about scheduling-skill

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

FAQPage Schema
How do I schedule recurring agent tasks with cron-like expressions?

Schedule recurring agent tasks by applying cron-like recurrence expressions to define intervals, which ensures reliable delivery and maintains next_run visibility for deterministic execution.

Can I route scheduled task results to Slack and Telegram channels?

Route scheduled task results to Slack or Telegram channels by configuring delivery endpoints, where plan enforcement ensures consistency and reliable delivery across multiple fires.

How does timezone awareness work when scheduling one-off reminders?

Timezone awareness anchors one-off reminder execution to specified timezones like Europe/Kyiv, preventing timing conflicts and missed deadlines by avoiding server default offsets.

Does scheduling require explicit user approval for every action?

Explicit user approval is enforced for every scheduling action to maintain a safe, auditable workflow, preventing unauthorized task creation and ensuring deterministic logs.

What is the best way to audit recurring tasks and check next_run visibility?

Audit recurring tasks using deterministic logs and next_run visibility, which expose an auditable workflow with robust error handling and clear tracking of upcoming executions.