Schedule in-process JavaScript agent jobs with Croner
Use Croner when a JavaScript, TypeScript, Deno, Bun, or browser-based agent service needs zero-dependency cron parsing, next-run previews, timezone-aware schedules, overrun protection, and in-process recurring jobs.
npx skills add agentskillexchange/skills --skill schedule-in-process-javascript-agent-jobs-with-croner
Croner is a zero-dependency JavaScript and TypeScript cron scheduler and cron-expression evaluator. Use it when an operator or coding agent is adding lightweight recurring work inside a custom agent service, such as periodic memory cleanup, report generation, polling, evaluation runs, or scheduled maintenance, and wants reviewable cron expressions with next-run inspection, timezone handling, pause/resume controls, async task support, and overrun protection. Invoke this instead of using a hosted scheduler or durable queue normally when the useful workflow is local in-process scheduling: install Croner, define bounded jobs in code, review the cron expressions and next-run behavior, wire error handling, and keep the scheduled task implementation inside the agent service. The scope boundary is embedded schedule evaluation and in-process recurring jobs for JavaScript runtimes, not a full job queue, distributed scheduler, monitoring platform, or generic npm library listing.
What this skill actually does
Inputs and prerequisites: Node.js 18 or newer, Deno 2 or newer, Bun 1 or newer, or a browser JavaScript runtime; Croner package; custom agent service code.
Setup notes: Install with npm install croner, bun add croner, import from jsr:@hexagon/croner in Deno, or use the documented browser bundle. Then import Cron from croner, define cron patterns and scheduled functions, and verify nextRun or nextRuns before enabling recurring agent work.
Source and verification boundary: use https://croner.56k.guru as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Custom Agents workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.