Laravel mail
Skill event4u-app/agent-config/dist/agent-src/skills/laravel-mail
Use when building Laravel emails — Mailables, Markdown templates, queued sending, attachments, previews — even when the user says 'send this as an email' without naming Mailables.From its SKILL.md
npx -y skills add event4u-app/agent-config --skill laravel-mailAssembled 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
5.2 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it
laravel-mail
When to use
Use this skill when building email functionality:
- Mailable classes with HTML/Blade or Markdown templates
- Queued email sending
- Attachments and inline images
- Mail testing and previewing
For simple notification emails (one-off messages), see laravel-notifications. Use Mailables when you need full control over the email template.
Procedure: Create a Mailable
- Generate class —
php artisan make:mail InvoiceMail --markdown=emails.invoice. - Configure — Set subject, from, attachments, queuing (
ShouldQueue). - Create template — Markdown template in
resources/views/emails/. - Verify — Send test email, confirm rendering and delivery.
Example
php artisan make:mail InvoiceMail --markdown=emails.invoice
declare(strict_types=1);
namespace App\Mail;
use App\Models\Invoice;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Mail\Mailable;
use Illuminate\Mail\Mailables\Content;
use Illuminate\Mail\Mailables\Envelope;
use Illuminate\Queue\SerializesModels;
class InvoiceMail extends Mailable implements ShouldQueue
{
use Queueable;
use SerializesModels;
public function __construct(
private readonly Invoice $invoice,
) {}
public function envelope(): Envelope
{
return new Envelope(
subject: 'Invoice #' . $this->invoice->getNumber(),
replyTo: ['[email protected]'],
);
}
public function content(): Content
{
return new Content(
markdown: 'emails.invoice',
with: [
'invoice' => $this->invoice,
'url' => route('invoices.show', $this->invoice->getId()),
],
);
}
/** @return array<int, \Illuminate\Mail\Mailables\Attachment> */
public function attachments(): array
{
return [
Attachment::fromPath('/path/to/invoice.pdf')
->as('invoice-' . $this->invoice->getNumber() . '.pdf')
->withMime('application/pdf'),
];
}
}
Markdown templates
{{-- resources/views/emails/invoice.blade.php --}}
<x-mail::message>
# Invoice {{ $invoice->getNumber() }}
Thank you for your order. Here is your invoice summary:
<x-mail::table>
| Item | Amount |
|:-----|-------:|
@foreach ($invoice->getItems() as $item)
| {{ $item->getName() }} | {{ $item->getFormattedAmount() }} |
@endforeach
| **Total** | **{{ $invoice->getFormattedTotal() }}** |
</x-mail::table>
<x-mail::button :url="$url">
View Invoice
</x-mail::button>
Thanks,<br>
{{ config('app.name') }}
</x-mail::message>
Sending mail
// Send immediately
Mail::to($user)->send(new InvoiceMail($invoice));
// Queue for background sending (preferred)
Mail::to($user)->queue(new InvoiceMail($invoice));
// Send later
Mail::to($user)->later(now()->addMinutes(10), new InvoiceMail($invoice));
// Multiple recipients
Mail::to($users)
->cc($manager)
->bcc('[email protected]')
->send(new InvoiceMail($invoice));
Testing
// Assert mail was sent
Mail::fake();
// ... trigger action ...
Mail::assertSent(InvoiceMail::class, function (InvoiceMail $mail) use ($user) {
return $mail->hasTo($user->getEmail());
});
Mail::assertNotSent(InvoiceMail::class);
Mail::assertNothingSent();
Mail::assertQueued(InvoiceMail::class);
Previewing in browser
// routes/web.php (local only)
Route::get('/mail-preview', function () {
$invoice = Invoice::factory()->create();
return new InvoiceMail($invoice);
});
Core rules
- Always queue emails — implement
ShouldQueueto avoid blocking requests. - Use Markdown templates for consistent styling across email clients.
- Use Envelope + Content pattern (Laravel 11+) — not the old
build()method. - Test with
Mail::fake()— verify recipients, content, and queuing. - Keep Mailables focused — one Mailable per email type.
Output format
- Mailable class with envelope, content, and attachments
- Blade/Markdown email template
- Queued mail dispatch integration
Auto-trigger keywords
- Mailable
- email template
- send mail
- Mail::to
- markdown email
- mail attachment
Gotcha
- Always queue emails (
ShouldQueue) — synchronous sending blocks the request. - The model forgets that mail templates are Blade files — they need to be published/created.
- Don't test email content with
Mail::fake()alone — it doesn't render the template. UseMail::assertSent()with closure.
Do NOT
- Do NOT send emails synchronously in request lifecycle — always queue.
- Do NOT use
build()method — useenvelope(),content(),attachments(). - Do NOT hardcode email addresses — use config or environment variables.
- Do NOT put HTML in Mailable classes — use Blade templates.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.