schedule

Dispatch recurring jobs with interval-based and anchored cadence logic.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill schedule-kriscendobot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schedule
Source: https://github.com/kriscendobot/garden/tree/main/skills/schedule
Command: npx skills add https://github.com/kriscendobot/garden --skill schedule-kriscendobot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of managing recurring administrative or technical tasks across a distributed fleet of agents, ensuring jobs are dispatched reliably without double-execution or drift.

Core Features & Use Cases

  • Recurring Job Dispatch: Supports interval-based (daily, weekly, hourly) and wall-clock anchored scheduling to prevent drift.
  • Preflight Gating: Allows for deterministic checks before dispatching, ensuring work is only performed when necessary.
  • Carry-forward Logic: Automatically manages replies to dead-lettered jobs by injecting reports into the next scheduled tick.
  • Use Case: Use this to automate weekly status reports or daily maintenance tasks that require checking for specific conditions before execution.

Quick Start

Use the schedule skill to set a new weekly task that runs every Tuesday at 13:00 Pacific Time.

Frequently Asked Questions about schedule

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

FAQPage Schema
How do I automate recurring task dispatching across a distributed agent environment?

Recurring task dispatching is automated using interval-based and wall-clock anchored scheduling logic to ensure atomic, drift-free execution of periodic workflows across distributed agents.

How does preflight gating work for scheduled job execution?

Preflight gating performs deterministic checks before dispatching jobs to ensure work is only performed when necessary, preventing unnecessary execution and maintaining state consistency across job cycles.

What is the best way to handle dead-lettered jobs in a periodic workflow?

Dead-lettered jobs are handled through carry-forward logic, which automatically injects reports from failed jobs into the next scheduled tick to maintain state consistency across cycles.

Can I schedule weekly maintenance tasks with specific time anchors?

Weekly maintenance tasks can be scheduled using wall-clock anchored cadence logic, allowing you to set specific execution times like every Tuesday at 13:00 Pacific Time without drift.

Why does my cron-based scheduling drift in a distributed fleet of agents?

Scheduling drift occurs when interval-based logic lacks wall-clock anchoring; this skill prevents drift by implementing anchored cadence logic and atomic execution across distributed agents.

Does schedule support both hourly intervals and daily anchored task scheduling?

Hourly intervals and daily anchored scheduling are both supported through combined interval-based and wall-clock anchored cadence logic, ensuring atomic, drift-free execution for various periodic workflows.