send-email

Send transactional and bulk emails via the Resend API with idempotency keys.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/marcosmlslira/observadordedominios --skill send-email-marcosmlslira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send-email
Source: https://github.com/marcosmlslira/observadordedominios/tree/main/.agents/skills/resend/send-email
Command: npx skills add https://github.com/marcosmlslira/observadordedominios --skill send-email-marcosmlslira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sending transactional emails and notifications can be error-prone and time-consuming; this skill streamlines composing, sending, and tracking emails via the Resend API for reliability and scale.

Core Features & Use Cases

  • Single and batch email sending via Resend APIs with idempotency keys to prevent duplicates.
  • Support for transactional messages (welcome, order confirmations, password resets) and bulk notifications, with guidance on best practices and error handling.
  • Optional metadata like tags, attachments, and scheduling, plus guidance on webhooks for delivery events.

Quick Start

Authenticate with your Resend API key and send a sample email using the Resend SDK.

Frequently Asked Questions about send-email

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

FAQPage Schema
How do I send transactional emails using the Resend API?

You can send transactional emails using the Resend API by authenticating with your API key and using the SDK to dispatch messages, utilizing built-in retry logic and idempotency keys to prevent duplicate deliveries.

Can I send bulk emails and batch notifications without creating duplicates?

Yes, you can send bulk notifications and batch emails safely by enforcing idempotency keys, which ensure that any retried or duplicated requests do not result in multiple identical emails being delivered to recipients.

What is the best way to handle email delivery tracking and webhook events for transactional messages?

The best way to handle email delivery tracking is by configuring webhooks to monitor delivery events, allowing you to track the status of transactional messages like order confirmations and password resets in real-time.

Does this approach support scheduling emails and adding attachments or metadata tags?

Yes, the Resend API approach supports adding optional metadata like tags and attachments to your messages, along with scheduling capabilities to send transactional emails at designated times.

Why does my transactional email system need idempotency keys and retry logic?

Idempotency keys and retry logic are needed in transactional email systems to handle network failures gracefully, ensuring that temporary errors trigger automatic retries without sending duplicate emails to users.

How do I send a welcome email or password reset notification with minimal configuration?

You can send welcome emails and password reset notifications with minimal configuration by applying safe defaults provided by the Resend API, streamlining the composition and dispatch of transactional messages.