scheduled-jobs

Schedule recurring automated tasks using Desktop scheduled tasks or Claude Code /loop sessions.

Updated Apr 8, 2026

Search Tags:#automation #desktop #loop #recurring #personal-os #scheduled-tasks

Ready to run

npx skills add https://github.com/zm2231/personal-os-cowork --skill scheduled-jobs-zm2231

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scheduled-jobs
Source: https://github.com/zm2231/personal-os-cowork/tree/main/.claude/skills/scheduled-jobs
Command: npx skills add https://github.com/zm2231/personal-os-cowork --skill scheduled-jobs-zm2231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the need to manually initiate routine workflows by providing clear guidance to set up automated recurring tasks that run on a schedule or during an active session.

Core Features & Use Cases

Desktop scheduled tasks: Always‑on recurring jobs such as daily briefings or weekly summaries that survive restarts.
/loop sessions: Session‑scoped polling for short‑term automation like checking deployment status every few minutes.
Standard templates: Ready‑to‑use prompt outlines for morning briefings, weekly summaries, and reflection passes that read from and write to your personal-os files.
Safety guidelines: Ensures prompts are self‑contained, output destinations are defined, and tasks are tested manually before scheduling.

Quick Start

Ask Claude to schedule a daily morning briefing that reads your priorities and writes a summary to the logs folder.

Frequently Asked Questions about scheduled-jobs

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

FAQPage Schema

How do I schedule recurring tasks to run automatically without manual intervention?▼

To schedule recurring tasks, you configure self-contained prompts with defined output destinations and set a frequency using Desktop scheduled tasks for always-on jobs or Claude Code /loop sessions for short-term polling. This automates daily briefings and periodic reflections without manual initiation.

What is the difference between Desktop scheduled tasks and /loop sessions for personal workflow automation?▼

Desktop scheduled tasks are always-on recurring jobs that survive system restarts for long-term automation like daily briefings, while /loop sessions are session-scoped polling mechanisms for short-term automation such as checking deployment status every few minutes during an active session.

Can I use scheduled tasks to read and write files within my personal-os workflow?▼

Yes, scheduled tasks apply to personal workflow automation by using standard self-contained prompt templates that read from and write to personal-os files. This enables automated daily briefings, weekly summaries, and reflection passes to update your system files directly.

How do I set up a daily morning briefing that automatically summarizes priorities?▼

To set up a daily morning briefing, define a self-contained prompt that reads your priorities and writes a summary to the logs folder, then configure the daily frequency using Desktop scheduled tasks. Test the prompt manually before scheduling to ensure correct file outputs.

What safety guidelines should I follow when configuring automated recurring jobs?▼

Safety guidelines for automated recurring jobs require defining self-contained prompts, explicitly defining output destinations for generated summaries, and testing tasks manually before scheduling them to prevent unintended file overwrites within your personal-os structure.

Do I need any external dependencies to run periodic reflections and weekly summaries on a schedule?▼

No external dependencies are required. You can run periodic reflections and weekly summaries by configuring self-contained prompts within Desktop scheduled tasks or Claude Code /loop sessions, relying entirely on your existing personal-os files for reading and writing outputs.