How do I install the Jobs Events skill?

Run npx skillmds@latest add event4u-app/jobs-events in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jobs Events safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jobs Events?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jobs Events free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jobs Events?

event4u-app (@event4u-app) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jobs Events by event4u-app — Agent Skill

Name: Jobs Events
Author: event4u-app

File contents

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

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

Step 1: Create the job class

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

Step 2: Implement handle()

Keep focused and readable.
Delegate complex logic to services/actions.
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

Job/Event/Listener class(es) with proper serialization and retry config
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

---name: jobs-eventsdescription: Use when creating Laravel jobs, queued workflows, events, or listeners. Covers clear responsibilities, safe serialization, and retry/failure handling.---# jobs-events## When to useUse 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: Inspect1. 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 class1. 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 format1. Job/Event/Listener class(es) with proper serialization and retry config2. 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

Frequently asked questions

Jobs Events