scheduler

Manage recurring msgcode schedules within the current workspace.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/42atom/msgcode --skill scheduler-42atom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scheduler
Source: https://github.com/42atom/msgcode/tree/main/src/skills/runtime/scheduler
Command: npx skills add https://github.com/42atom/msgcode --skill scheduler-42atom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node.

What problem does it solve?

Manage recurring schedules in msgcode by providing a safe, centralized interface to create, view, enable, disable, and remove cron-like tasks, and to diagnose their state within the current workspace.

Core Features & Use Cases

  • Unified entry point for scheduling tasks in msgcode.
  • Enforces correct templates for add/list/remove/enable/disable operations.
  • Provides visibility into schedule files, job projections, and run logs for troubleshooting.
  • Prevents inventing unsupported tools such as cron_add or schedule_add.

Quick Start

Use the scheduler’s main entry at ~/.config/msgcode/skills/scheduler/main.sh to add, list, enable, or disable schedules in your current workspace.

Frequently Asked Questions about scheduler

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

FAQPage Schema
How do I schedule recurring cron-based tasks in msgcode?

You can schedule recurring tasks in msgcode by invoking the scheduler entry point to add, enable, or disable cron-like jobs within your current workspace. It enforces correct templates and validates the absolute workspace path for safe task creation.

What is the best way to manage periodic reminders and automation in msgcode workspaces?

The best way to manage periodic reminders and automation in msgcode workspaces is using a centralized scheduling interface. It provides a unified entry point to safely create, inspect, and remove recurring schedules while preventing the use of unsupported tools.

Can I use Node to run cron-based schedules in msgcode?

Yes, Node is a required dependency for running cron-based schedules in msgcode. The scheduler operates through a shell entry point that manages recurring tasks and enforces strict wrapper workflows within the current workspace.

Why is my msgcode schedule not working across different workspaces?

Your msgcode schedule may not work if the absolute workspace path is invalid. The scheduler validates the workspace path strictly and references schedule files, job projections, and run logs to help diagnose and troubleshoot schedule state issues.

How do I troubleshoot schedule state and inspect run logs in msgcode?

To troubleshoot schedule state in msgcode, use the scheduler to inspect schedule files, job projections, and run logs. This provides visibility into recurring task execution and helps diagnose issues within the current workspace.