dev-toolings/superpowers-symfony119 installs
symfony-scheduler
Schedule recurring tasks with the Symfony Scheduler component (native since 7.x); define schedules, triggers, and integrate with Messenger
How do I install this agent skill?
npx skills add https://github.com/dev-toolings/superpowers-symfony --skill symfony-schedulerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides implementation guidance for the Symfony Scheduler component, including package installation via Composer and standard CLI commands for execution. All operations are typical for Symfony application development and involve trusted framework components.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Symfony Scheduler (Symfony)
Use when
- Running recurring work (reports, cleanups, syncs) without system cron entries.
- Choosing between
RecurringMessage::every(),RecurringMessage::cron(), and a customTriggerInterface. - Splitting jobs into several named schedules with
#[AsSchedule]. - Preventing overlap or lost runs of heavy scheduled tasks.
Default workflow
- Install
symfony/scheduler, then write the message and its#[AsMessageHandler]handler. - Create a
#[AsSchedule('default')]class implementingScheduleProviderInterfaceand addRecurringMessageentries. - Pick the trigger:
every('5 minutes')orcron('0 */6 * * *'), with an explicit timezone for cron. - Add
stateful($cache)andlock($lockFactory->createLock('scheduler'))on theSchedulefor heavy tasks. - Run it with
messenger:consume scheduler_defaultunder Supervisor, one process per schedule. - Log with
PreRunEventandPostRunEvent, and test the provider throughgetRecurringMessages()andgetNextRunDate().
Guardrails
- Run a single consumer per schedule (
numprocs=1) and add a lock, or the same task fires twice. - Be explicit about timezones on every cron trigger.
- Scheduled handlers must be idempotent, since a run can be repeated.
- Use
--time-limitwith Supervisorautorestartso the long-lived worker recycles itself.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The schedule provider(s) with their triggers and timezone.
- The worker command and the Supervisor entry.
- The overlap policy (stateful, lock) and the monitoring hooks.
References
reference.md
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/dev-toolings/superpowers-symfony/symfony-scheduler">View symfony-scheduler on skillZs</a>