agentleFS
Sign inStart free
gerard-labsgerard-labs/superpowers-api-platform/skills/symfony-scheduler/SKILL.md

symfony-scheduler

Skill2 starsChanged 6 months agoMITView on GitHub

Schedule recurring tasks with Symfony Scheduler — `#[AsSchedule]` provider, `RecurringMessage::every('1 hour')` / `cron('0 0 * * *')` / `trigger(...)` triggers, integration with Messenger transports, `messenger:consume scheduler_default` for the worker, custom scheduler IDs for parallel cron tracks, `between('09:00', '18:00')` business-hour windows. Trigger on "nightly cleanup", "every N minutes report", "cron job in Symfony", or "replace crontab with native code".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep handlers deterministic and side-effect aware.

    line 28
  2. Distinctive:

    Use this file for execution posture and risk controls.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Symfony Scheduler (Symfony)

Use when

  • Implementing asynchronous workflows with Messenger/Scheduler/Cache.
  • Stabilizing retries and failure transports.

Default workflow

  1. Define async contract and delivery semantics.
  2. Implement idempotent handlers and routing strategy.
  3. Configure retries, failure transport, and observability.
  4. Validate success/failure replay scenarios.

Guardrails

  • Assume at-least-once delivery, not exactly-once.
  • Keep handlers deterministic and side-effect aware.
  • Surface poison-message handling strategy.

Progressive disclosure

  • Use this file for execution posture and risk controls.
  • Open references when deep implementation details are needed.

Output contract

  • Async config/handlers updated.
  • Retry/failure policy decisions.
  • Operational validation evidence.

References

  • reference.md
  • docs/complexity-tiers.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free