new-schedule

Schedule recurring tasks on a fixed cadence using ScheduleRegistry helpers.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-schedule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-schedule
Source: https://github.com/weiloon1234/Forge-Starter/tree/main/.claude/skills/new-schedule
Command: npx skills add https://github.com/weiloon1234/Forge-Starter --skill new-schedule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need code that runs on a timer, independent of HTTP requests, to perform periodic maintenance or data processing.

Core Features & Use Cases

  • Lightweight cadence-based triggering using Forge's ScheduleRegistry helpers such as every_minute, hourly, daily_at, and cron.
  • Inline work for fast tasks or dispatch to a Job for slow, retryable work; schedules fire quickly and the Job handles retries.
  • Timezone: Schedules fire in UTC by default; convert in the closure or cron expression if needed.

Quick Start

Configure a daily schedule that enqueues a token-pruning job at midnight UTC.

Frequently Asked Questions about new-schedule

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

FAQPage Schema
How do I automate recurring backend tasks on a fixed schedule?

To automate recurring backend tasks, use schedule helpers like every_minute, hourly, daily_at, and cron to trigger periodic maintenance or data aggregation automatically without relying on incoming HTTP requests.

What is the best way to run a nightly pruning job without an HTTP request?

The best way to run a nightly pruning job without an HTTP request is registering a daily schedule that dispatches a Job, which allows the schedule to fire quickly while the Job handles the slow, retryable pruning work.

Should I run scheduled tasks inline or dispatch them as a Job?

Run scheduled tasks inline for fast operations, or dispatch a Job for slow and retryable work. Dispatching a Job ensures schedules fire quickly while the Job handles execution retries and heavier processing.

Can I configure a cron job to run in a specific timezone?

Cron jobs run in UTC by default. To target a specific timezone, you must convert the time either inside the closure logic or directly within the cron expression you configure.

Do I need to register a ScheduleId when setting up a cron job?

Yes, you must define and use a ScheduleId constant when registering a cron job. This enforces proper schedule management for recurring tasks like daily reports or external-service synchronization.