laravel-jobs

Delegate Laravel domain work to actions via jobs and listeners.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Sivanwol/sabo-platfom --skill laravel-jobs-sivanwol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-jobs
Source: https://github.com/Sivanwol/sabo-platfom/tree/main/.ai/skills/laravel-jobs
Command: npx skills add https://github.com/Sivanwol/sabo-platfom --skill laravel-jobs-sivanwol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Background jobs and event listeners in Laravel are often tempted to merge domain logic with infrastructure code. This Skill promotes moving business rules into Actions and using Jobs and Listeners as thin delegators.

Core Features & Use Cases

  • Thin delegation: Jobs and Listeners delegate to domain actions to perform work.
  • Queue configuration: Supports retries, timeouts, and unique constraints.
  • Event-driven flows: Listeners react to events and orchestrate actions.
  • Use cases: Async processing, delayed tasks, and complex workflows where domain logic must stay in Actions.

Quick Start

Create your domain work in an Action and dispatch it from a Job or Listener to run asynchronously.

Frequently Asked Questions about laravel-jobs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate business logic from Laravel jobs and event listeners?

Use Laravel jobs and listeners as thin delegators that pass execution to dedicated Actions, isolating domain logic from infrastructure code to maintain clean background processing workflows.

Can I configure retries and timeouts for asynchronous Laravel actions?

Yes, you can configure retries, timeouts, and unique constraints for Laravel actions by defining queue settings on the delegating Jobs that orchestrate the asynchronous domain work.

What is the best way to structure event-driven workflows in Laravel?

The best way to structure event-driven workflows in Laravel is using Listeners to react to events and delegate orchestration to Actions, keeping domain logic separate and enabling delayed tasks.

When should I use Laravel actions instead of putting code directly in jobs?

Use Laravel actions instead of putting code directly in jobs when you need to separate domain logic from orchestration, enable thin delegation, and support complex asynchronous workflows with retries.

How do I dispatch Laravel actions to run asynchronously via queues?

Dispatch Laravel actions asynchronously by creating the domain work in an Action and dispatching it from a Job or Listener, allowing the queue to handle background processing and delayed tasks.