self-scheduler

Schedule autonomous agent runs via Markdown frontmatter files in TeamDay spaces.

2|1|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/TeamDay-AI/agents --skill self-scheduler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-scheduler
Source: https://github.com/TeamDay-AI/agents/tree/main/skills/teamday/self-scheduler
Command: npx skills add https://github.com/TeamDay-AI/agents --skill self-scheduler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scheduling autonomous agent runs across TeamDay spaces to ensure long-term objectives progress without manual intervention.

Core Features & Use Cases

  • Create, view, update, and disable/enable scheduled jobs stored as Markdown frontmatter.
  • Persist schedules across session restarts and support cron-based triggers.
  • Terminate or adjust prompts mid-flight and notify users when needed.

Quick Start

Write a frontmatter Markdown file under .claude/scheduled/ describing the job, including name, schedule, and system prompt.

Frequently Asked Questions about self-scheduler

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

FAQPage Schema
How do I schedule autonomous agents to run periodically without manual intervention?

Scheduling autonomous agents is done by writing Markdown frontmatter files under .claude/scheduled/ that specify the job name, cron schedule, and system prompt, enabling periodic execution without manual intervention.

What is cron-based scheduling for agent workflows and when do I need it?

Cron-based scheduling for agent workflows triggers autonomous runs at specified intervals like hourly, daily, or weekly. You need it for long-term objectives requiring periodic monitoring or maintenance within TeamDay spaces.

Can I update or disable a scheduled agent job mid-flight?

Yes, you can update, enable, or disable scheduled agent jobs mid-flight. The self-scheduler supports terminating or adjusting prompts during execution and can notify users when needed.

How do I persist agent schedules across session restarts?

Agent schedules persist across session restarts by storing them as Markdown frontmatter files. This file-based approach ensures cron-based triggers and job definitions survive even after session terminations.

Does the self-scheduler inject credentials at runtime for automated workflows?

Yes, the self-scheduler injects credentials at runtime when executing scheduled jobs. System prompts are preserved and credentials are securely provided to agents during their automated periodic runs.