email

Render HTML email templates and queue asynchronous delivery via Celery.

Updated Aug 23, 2026

Search Tags:#templates #email #smtp #resend #celery #transactional-email #sendgrid

Ready to run

npx skills add https://github.com/mrsknetwork/nemodev --skill email-mrsknetwork

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: email
Source: https://github.com/mrsknetwork/nemodev/tree/main/skills/domains/references/email
Command: npx skills add https://github.com/mrsknetwork/nemodev --skill email-mrsknetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Email delivery in production is fragile when emails are created and sent inside request handlers. This skill ensures HTML template rendering, queue-based sending, and unsubscribe/bounce handling to improve reliability and deliverability.

Core Features & Use Cases

Template-driven emails: Render HTML emails using a template engine with dynamic data.
Queue-based sending: Send emails asynchronously via Celery to avoid blocking user requests.
Provider flexibility: Works with Resend, SendGrid, or SMTP backends with consistent templates and unsubscribe headers.
Common flows: Welcome emails, password resets, order confirmations, and digest notifications.

Quick Start

Configure a provider, create a template, and enqueue the send task on relevant user events.

Frequently Asked Questions about email

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

FAQPage Schema

How do I send transactional email asynchronously without blocking web requests?▼

Transactional email can be sent asynchronously by offloading the delivery task to a Celery queue, allowing web request handlers to return immediately while the background worker processes the email sending workflow.

Can I use the same email templates across Resend, SendGrid, and SMTP backends?▼

Yes, provider flexibility allows you to use consistent HTML templates and unsubscribe headers across Resend, SendGrid, or SMTP backends without altering the rendering logic for each provider.

What is the best way to handle unsubscribe and bounce management for transactional email?▼

Safe handling for unsubscribe and bounce management is achieved by processing these events asynchronously through the queue-based sending workflow, ensuring deliverability is maintained across all outgoing transactional emails.

How do I render dynamic HTML email templates for password resets and order confirmations?▼

HTML email templates are rendered using a template engine that injects dynamic data, enabling personalized content for common flows like password resets, order confirmations, and welcome emails.

Why does sending transactional email directly inside request handlers fail in production?▼

Sending transactional email inside request handlers makes delivery fragile because it blocks the user response and lacks queue-based retry logic, causing failures when the provider experiences delays or errors.

Do I need Celery to queue transactional email delivery for digest notifications?▼

Yes, a Celery-based async sending workflow is required to queue transactional email delivery, ensuring that digest notifications and other batched sends do not block application processes.