The workflow runs in a Cloudflare Workers application and needs stateful scheduled or durable agent work.
It explicitly provides persistent state, recurring and cron scheduling, and durable workflows.
Editorial confidence: highSchedule recurring agent workflows
Compare schedulers and recurring-work patterns by hosting, permissions, monitoring, retries, state, and failure recovery.
Last meaningful review July 20, 2026
The job
You already have a bounded agent workflow and need it to run on a recurring schedule with visible state and safe failure handling.
Includedcron-like recurring agent jobs · local or hosted scheduling · logging, retries, alerts, and run state
Not this pagedesigning the underlying business workflow · general multi-agent orchestration · unattended irreversible actions
30-second route
Consider Agents Sdk ↗
The workflow is a Claude Code operation and memory-backed state plus consent boundaries are required.
It supplies scheduled-task setup, memory and task-queue patterns, and completion/error-handling guidance.
Editorial confidence: highThe workflow must run locally after agent sessions end and leave project-readable logs and state.
It documents external schedulers, persistent timers, and a file-based state/log architecture.
Editorial confidence: highA managed platform with documented retries, alert delivery, and run monitoring is mandatory.
The selected sources support scheduling and state, but do not document a complete managed retry-and-alert solution.
Editorial confidence: highBefore you install
Install Agents Sdk for a Cloudflare Workers implementation; adapt either Claude Code-oriented skill for a Claude/local workflow; build the retry and alert layer when those controls are required.
The sources explicitly cover schedules and state, while complete retry/alert operations are not documented by the selected skills.
Read the intervention guide →Source-led comparison
What changes the choice
Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.
SkillBest forActionEdits?Setup
Agents SdkCloudflare Workers applications that need recurring or cron-triggered agent work with persistent state and durable multi-step workflows.InstallDefine the Agent class, configure Durable Objects and SQLite migration, then schedule the bounded task with cron or an interval.Install the `agents` package and configure the Durable Object binding and migration. ↗Autonomous Agent HarnessA Claude Code-based recurring workflow that needs scheduled tasks, persistent memory or queue state, explicit consent boundaries, and completion checks.AdaptKeep the workflow bounded; use the scheduled-task prompt to record its result to memory and include error handling and a completion check.Configure the listed `memory` and `scheduled-tasks` MCP servers, then create the scheduled task for the project directory. ↗Agentic OsA local, persistent Claude Code project that needs an inspectable file-based state and log layer plus a scheduler that survives session restarts.AdaptUse the supplied `data/` layout for run state and append-only logs; invoke a bounded command through the shown external scheduler and add your own failure-notification policy.Create the kernel, command, scripts, and data directories; choose LaunchAgent, a systemd user timer, or pm2. ↗Source notes
Inspect evidence and candidate limits 3 candidates
Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.
What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.
Use it forCloudflare Workers applications that need recurring or cron-triggered agent work with persistent state and durable multi-step workflows.
Avoid ifYou need a local scheduler or a workflow that is not being built on Cloudflare Workers.
ActionInstall
EditsDefine the Agent class, configure Durable Objects and SQLite migration, then schedule the bounded task with cron or an interval.
SetupInstall the `agents` package and configure the Durable Object binding and migration.
Inspect workflow and compatibility details
ContextCloudflare-hosted agent runtime.
OutputAn Agent class with scheduled handlers, persistent state, and optional `AgentWorkflow` processing.
ControlCode-first SDK configuration.
Invocationnpm install agents
Install scopeproject dependency
Agent fitDirect fit for a hosted recurring agent workflow with state.
Watch outThe source directs users to retrieve current Agents SDK documentation before implementation.
Source-visible capabilitiesRecurring schedulingOne-time, recurring `scheduleEvery`, and cron tasks.explicit sourcePersistent stateSQLite-backed state that auto-syncs to clients.explicit sourceDurable workflowsMulti-step background processing via `AgentWorkflow`.explicit source
CompatibilityCloudflare Workersdeclarednot runtime-tested
Evidence
The skill explicitly covers scheduled tasks and its documentation map includes scheduling for `schedule()`, `scheduleEvery()`, and cron.SKILL.md:3, 20 · inspected 2026-07-20 · high confidence
It provides SQLite-backed persistent state, recurring/cron scheduling, and durable multi-step workflows.SKILL.md:34-40 · inspected 2026-07-20 · high confidence
Its API examples show cron and interval scheduling plus starting a workflow.SKILL.md:111-123 · inspected 2026-07-20 · high confidence
Setup includes installing `agents` and configuring a Durable Object with a SQLite migration.SKILL.md:45-65 · inspected 2026-07-20 · high confidence
Public signal1084 /SkillsMP source-specifichostedpersistent-statedurable-workflowsexplicit source
Use it forA Claude Code-based recurring workflow that needs scheduled tasks, persistent memory or queue state, explicit consent boundaries, and completion checks.
Avoid ifYou only need a minimal scheduler and do not want MCP memory or scheduled-task setup.
ActionAdapt
EditsKeep the workflow bounded; use the scheduled-task prompt to record its result to memory and include error handling and a completion check.
SetupConfigure the listed `memory` and `scheduled-tasks` MCP servers, then create the scheduled task for the project directory.
Inspect workflow and compatibility details
ContextClaude Code with MCP servers for memory and scheduled tasks.
OutputA scheduled isolated agent session that writes workflow state to memory.
ControlPrompt-and-MCP configuration with explicit approval boundaries.
Invocationmcp__scheduled-tasks__create_scheduled_task(...)
Install scopeClaude Code configuration and MCP servers
Agent fitDirect fit for recurring Claude Code operations with state carried through memory.
Watch outScheduled tasks run in isolated sessions, so context must be shared through memory; the source says to verify completion and add error handling.
Source-visible capabilitiesRecurring cron operationsCreates recurring agent operations through Claude Code scheduled tasks.explicit sourcePersistent workflow stateUses built-in memory and an MCP memory server; includes a persistent task queue pattern.explicit sourceFailure handling guidanceRequires verifying scheduled-task completion and adding error handling to cron prompts.explicit source
CompatibilityClaude Codedeclarednot runtime-tested
Evidence
The skill is for scheduled and continuous agent operation and says users should explicitly scope autonomous operation.SKILL.md:10-25 · inspected 2026-07-20 · high confidence
It defines cron-based scheduled operations and gives recurring task examples.SKILL.md:86-113 · inspected 2026-07-20 · high confidence
It describes persistent memory and a task queue that survives session boundaries.SKILL.md:57-84, 149-173 · inspected 2026-07-20 · high confidence
It supplies MCP-server configuration for memory and scheduled tasks.SKILL.md:187-220 · inspected 2026-07-20 · high confidence
It warns that cron tasks are isolated and directs users to verify completion and add error handling.SKILL.md:268-275 · inspected 2026-07-20 · high confidence
Public signal1300 /SkillsMP source-specificclaude-codepersistent-memorysafety-boundariesexplicit source
Use it forA local, persistent Claude Code project that needs an inspectable file-based state and log layer plus a scheduler that survives session restarts.
Avoid ifYou want a managed hosted scheduler or built-in retry and alert handling.
ActionAdapt
EditsUse the supplied `data/` layout for run state and append-only logs; invoke a bounded command through the shown external scheduler and add your own failure-notification policy.
SetupCreate the kernel, command, scripts, and data directories; choose LaunchAgent, a systemd user timer, or pm2.
Inspect workflow and compatibility details
ContextProject-local Claude Code operating model with external scheduling.
OutputScheduled command execution with project-local JSON/Markdown state and logs.
ControlFilesystem-first architecture plus external OS/process scheduler.
InvocationNot yet mapped from the source.
Install scopeproject files plus selected external scheduler
Agent fitDirect fit where recurring jobs must survive session restarts and leave inspectable state.
Watch outThe skill explicitly recommends an external scheduler because Claude Code’s built-in cron ends with the session; it does not document retries or alerts.
Source-visible capabilitiesSession-resilient schedulingUses external cron, LaunchAgent, systemd timers, or pm2 for scheduled automation.explicit sourceVisible run stateStores append-only logs, project state, and decision records in a `data/` filesystem layer.explicit sourceRunnable recurring commandShows a Linux systemd oneshot service and persistent daily timer invoking `/daily-sync`.explicit source
CompatibilitymacOSdeclarednot runtime-testedLinuxdeclarednot runtime-testedCross-platform via pm2declarednot runtime-tested
Evidence
The architecture assigns scripts to scheduled or event-driven tasks and the data layer to append-only logs and project state.SKILL.md:20-41 · inspected 2026-07-20 · high confidence
It states scheduled automation uses external cron because Claude Code built-in cron dies when the session ends.SKILL.md:212-215 · inspected 2026-07-20 · high confidence
It provides macOS LaunchAgent, Linux systemd timer with `Persistent=true`, and pm2 scheduling examples.SKILL.md:216-285 · inspected 2026-07-20 · high confidence
It defines JSON and Markdown as the filesystem data layer.SKILL.md:287-329 · inspected 2026-07-20 · high confidence
Its best-practices checklist repeats the external-cron recommendation and append-only logging.SKILL.md:377-388 · inspected 2026-07-20 · high confidence
Public signal2334 /SkillsMP source-specificlocal-schedulingfile-based-statesession-resilientexplicit source
Still comparing?
Tell us the job, not just the skill names.
Request a task guide ↗Did this decision map help?