agent-self-scheduling

Automate AI agent task scheduling with cron, systemd timers, or Hermes.

61|11|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/Matymatyk-business/david-skills --skill agent-self-scheduling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-self-scheduling
Source: https://github.com/Matymatyk-business/david-skills/tree/main/skills/autonomous-ai-agents/agent-self-scheduling
Command: npx skills add https://github.com/Matymatyk-business/david-skills --skill agent-self-scheduling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scheduling AI agents to run tasks on a timer or loop, so they operate without manual launching.

Core Features & Use Cases

  • Camp A: external clocks (cron, systemd timers, dumb loops) for one-shot invocations.
  • Camp B: Hermes-based built-in scheduler for recurring jobs, isolation, chaining, and self-terminating loops.
  • Heartbeat patterns enable proactive checks at different cadences with safe, token-efficient runs.

Quick Start

Ask your AI to schedule a recurring task with Hermes using a cadence like every 5 minutes or a cron expression.

Frequently Asked Questions about agent-self-scheduling

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

FAQPage Schema
How do I schedule an AI agent to run tasks on a recurring loop?

You can schedule an AI agent to run recurring loops by defining a cadence like "every 5m" or a cron expression, which automates task execution without manual launching.

What is the difference between using external cron and built-in scheduling for AI agents?

External cron and systemd timers handle one-shot invocations, whereas built-in Hermes scheduling manages recurring jobs, session isolation, chaining, and self-terminating heartbeat loops.

Can I use systemd timers for one-shot AI agent invocations?

Yes, systemd timers support one-shot AI agent invocations. The Skill treats external clocks like systemd timers and dumb loops as triggers for single-run agent executions.

How do I prevent an AI agent from self-scheduling duplicate tasks?

Built-in guardrails prevent an AI agent from self-scheduling, ensuring agents cannot autonomously create new or duplicate timer-based runs during their automated sessions.

Does scheduling AI agents guarantee isolated sessions for each run?

Yes, scheduling AI agents guarantees isolated, fresh sessions for each run, ensuring every automated task executes in a clean environment without state from previous executions.