skills.rest
patleeman
patleemanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

scheduled-tasks

Schedule and manage durable cron or one-time tasks for Neon Pilot.

22|2|Updated Feb 28, 2026
Search Tags:#automation#callbacks#cron#web-ui#daemon#thread-management#scheduled-tasks
One-click install
npx skills add https://github.com/patleeman/neon-pilot --skill scheduled-tasks-patleeman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scheduled-tasks
Source: https://github.com/patleeman/neon-pilot/tree/main/extensions/system-automations/skills/scheduled-tasks
Command: npx skills add https://github.com/patleeman/neon-pilot --skill scheduled-tasks-patleeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Neon Pilot users need a reliable way to run long-lived, scheduled tasks that wake up threads or conversations without direct interaction, while persisting across restarts and supporting callbacks and retries.

Core Features & Use Cases

  • Define recurring cron or one-time tasks for background automation and durable prompts.
  • Bind task results to a specific thread or conversation, with heartbeat support and resumption after downtime.
  • Inspect, run, validate, and monitor automations via the web UI or CLI, including status and history.

Quick Start

Create a recurring daily status check task that runs at 09:00 and posts the results to its owning thread.

Frequently Asked Questions about scheduled-tasks

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

FAQPage Schema
How do I schedule a recurring cron task that runs in the background without an open conversation?▼

You can schedule durable, daemon-backed cron tasks using frontmatter configuration to define recurring intervals, ensuring automations run without direct interaction and persist across restarts.

Can I bind a scheduled task result to a specific thread or conversation?▼

Yes, scheduled tasks support binding results to a specific thread or conversation, with heartbeat support and automatic resumption after downtime to maintain context continuity.

What's the best way to monitor and validate background automations for status and history?▼

You can inspect, run, validate, and monitor automations via the web UI or CLI, which provides status tracking, execution history, and durable run logging for all scheduled tasks.

Does this scheduled tasks system support one-time tasks or only recurring cron jobs?▼

The scheduled tasks system supports both recurring cron jobs and one-time tasks, allowing you to handle durable background prompts and single-execution automations within the same framework.

Why do I need a daemon-backed approach for scheduled automations instead of simple cron?▼

A daemon-backed approach provides durability by persisting tasks across restarts, supporting callbacks and retries, and enabling heartbeat support for thread resumption after unexpected downtime.

Are there limitations on using scheduled tasks for long-lived automations with callbacks?▼

Scheduled tasks enforce frontmatter fields and require daemon infrastructure, meaning automations must adhere to structured configuration rules and cannot run as stateless, isolated scripts without the backing daemon.

Related Skills

Explore More Software Engineering Skills→
awood45awood45
11

capture-skill

Convert a conversation workflow into a structured Claude skill specification.

Community
Advanced
majedsiefalnasrmajedsiefalnasr

gh-fix-ci

Diagnose and fix failing GitHub Actions PR checks using gh CLI commands.

Community
Intermediate
waynesuttonwaynesutton
401

convex-agents

Build persistent AI agents with Convex components for stateful conversations.

Community
Advanced
steipetesteipete
385.7k

clawdis-cron

Automate recurring task scheduling, notifications, and system checks.

Community
Basic