agentsclimarketplace

Jobs events

Skill event4u-app/agent-config/src/skills/jobs-events

Use when creating Laravel jobs, queued workflows, events, or listeners. Covers clear responsibilities, safe serialization, and retry/failure handling.From its SKILL.md

Install
npx -y skills add event4u-app/agent-config --skill jobs-events

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 572 tokens by cl100k_base, as published. Nobody here has run it

jobs-events

When to use

Use when creating jobs, events, listeners, or queued workflows.

Do NOT use when:

  • Artisan commands (use artisan-commands skill)
  • Scheduling configuration (use laravel-scheduling skill)

Procedure: Create a Job

Step 0: Inspect

  1. Check existing jobs — match naming, queue config, retry strategy, failure handling.
  2. Determine sync vs. async — only queue work that is slow, retryable, or non-blocking.
  3. Check queue driver: .env / config/queue.php (Redis, database, sync).
  4. Check Horizon: config/horizon.php for queue names, supervisors, balancing.

Step 1: Create the job class

  1. Pass IDs or compact DTOs in constructor — not full models with relations.
  2. Set queue via $this->onQueue(Queue::NAME->value).
  3. Add tags() for Horizon filtering.
  4. Set $maxExceptions, backoff(), $uniqueFor as needed.

Step 2: Implement handle()

  1. Keep focused and readable.
  2. Delegate complex logic to services/actions.
  3. Design for idempotency — retries must not create duplicates.

Step 3: Test

  • Bus::fake(), Queue::fake(), Event::fake().
  • Test side effects, not just dispatch assertions.

Procedure: Create an Event + Listener

Step 1: Create event

  • Past-tense naming: OrderPlaced, ImportCompleted.
  • Keep payload focused.
  • Laravel 11+: automatic discovery — no manual registration.

Step 2: Create listener

  • One responsibility per listener.
  • Delegate large logic to services.
  • Use ShouldQueue on listeners that do heavy work.

Conventions

→ See guideline php/jobs.md for full conventions (serialization, idempotency, events, dispatching).

Output format

  1. Job/Event/Listener class(es) with proper serialization and retry config
  2. Event registration in EventServiceProvider if needed

Gotcha

  • Without ShouldQueue, jobs run synchronously.
  • Queued jobs serialize constructor args — don't pass loaded models.
  • Listener exceptions block the event chain — queue heavy listeners.
  • Set $tries and $backoff — unlimited retries overwhelm the queue.

Do NOT

  • Do NOT serialize Eloquent models with loaded relations into queued jobs.
  • Do NOT ignore idempotency — retries must not create duplicates.
  • Do NOT hide critical business flows behind deep listener chains.

Auto-trigger keywords

  • Laravel job
  • queue
  • event
  • listener
  • dispatch
  • serialization

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.