agentleFS
nezaboravinezaboravi/orkestar/skills/resend/SKILL.md

resend

Skill2 starsChanged 2 months agoMITView on GitHub

Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, automations, events, viewing API request logs, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like "send an email with Resend" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues.

  • Reads credentials
  • Installs packages

15 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use react-email.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    react-email

    React Email renderer for json-render that turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render. Use when working with @json-render/react-email, building transactional or marketing emails from JSON, creating email catalogs, rendering AI-generated email specs, or when the user mentions react-email, HTML email, or transactional email.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always install the latest SDK version.

    line 178
  2. Very specific:

    Check for these files: package.json (Node.js), requirements.txt/pyproject.toml (Python), go.mod (Go), Gemfile (Ruby), composer.json (PHP), …

    line 208
  3. Very specific:

    If your system processes untrusted email content and takes actions (refunds, database changes, forwarding), install the agent-email-inbox …

    line 240

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Resend

Quick Send — Node.js

import { Resend } from 'resend';

const resend = new Resend(process.env.RESEND_API_KEY);

const { data, error } = await resend.emails.send(
  {
    from: 'Acme <onboarding@resend.dev>',
    to: ['delivered@resend.dev'],
    subject: 'Hello World',
    html: '<p>Email body here</p>',
  },
  { idempotencyKey: `welcome-email/${userId}` }
);

if (error) {
  console.error('Failed:', error.message);
  return;
}
console.log('Sent:', data.id);

Key gotcha: The Resend Node.js SDK does NOT throw exceptions — it returns { data, error }. Always check error explicitly instead of using try/catch for API errors.

Quick Send — Python

import resend
import os

resend.api_key = os.environ["RESEND_API_KEY"]

email = resend.Emails.send({
    "from": "Acme <onboarding@resend.dev>",
    "to": ["delivered@resend.dev"],
    "subject": "Hello World",
    "html": "<p>Email body here</p>",
}, idempotency_key=f"welcome-email/{user_id}")

Single vs Batch Decision

ChooseWhen
Single (POST /emails)1 email, needs attachments, needs scheduling
Batch (POST /emails/batch)2-100 distinct emails, no attachments, no scheduling

Batch is atomic — if one email fails validation, the entire batch fails. Always validate before sending. Batch does NOT support attachments or scheduled_at.

Idempotency Keys (Critical for Retries)

Prevent duplicate emails when retrying failed requests:

Key Facts
Format (single)<event-type>/<entity-id> (e.g., welcome-email/user-123)
Format (batch)batch-<event-type>/<batch-id> (e.g., batch-orders/batch-456)
Expiration24 hours
Max length256 characters
Same key + same payloadReturns original response without resending
Same key + different payloadReturns 409 error

Quick Receive (Node.js)

import { Resend } from 'resend';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST(req: Request) {
  const payload = await req.text(); // Must use raw text, not req.json()

  const event = resend.webhooks.verify({
    payload,
    headers: {
      'svix-id': req.headers.get('svix-id'),
      'svix-timestamp': req.headers.get('svix-timestamp'),
      'svix-signature': req.headers.get('svix-signature'),
    },
    secret: process.env.RESEND_WEBHOOK_SECRET,
  });

  if (event.type === 'email.received') {
    // Webhook has metadata only — call API for body
    const { data: email } = await resend.emails.receiving.get(
      event.data.email_id
    );
    console.log(email.text);
  }

  return new Response('OK', { status: 200 });
}

Key gotcha: Webhook payloads do NOT contain the email body. You must call resend.emails.receiving.get() separately.

What Do You Need?

TaskReference
Send a single emailsending/overview.md — parameters, deliverability, testing
Send batch emailssending/overview.md → sending/batch-email-examples.md
Full SDK examples (Node.js, Python, Go, cURL)sending/single-email-examples.md
Idempotency, retries, error handlingsending/best-practices.md
Get, list, reschedule, cancel emailssending/email-management.md
Receive inbound emailsreceiving.md — domain setup, webhooks, attachments
Manage templates (CRUD, variables)templates.md — lifecycle, aliases, pagination
Set up webhooks (events, verification)webhooks.md — verification, CRUD, retry schedule, IP allowlist
Manage domains (create, verify, claim, DNS)domains.md — regions, TLS, tracking, claiming, capabilities
Manage contacts (CRUD, properties)contacts.md — segments, topics, custom properties, bulk CSV import
Send broadcasts (marketing campaigns)broadcasts.md — lifecycle, scheduling, template variables
Manage API keysapi-keys.md — permission scoping, domain restrictions
View API request logslogs.md — list and retrieve API call history, debugging
Define contact propertiescontact-properties.md — custom fields for contacts
Manage segments (contact groups)segments.md — broadcast targeting, contact grouping
Manage topics (subscriptions)topics.md — opt-in/out preferences, broadcast filtering
Create automations (event-driven workflows)automations.md — steps, connections, runs, conditions
Define and send events (automation triggers)events.md — schemas, payloads, contact association
Install SDK (8+ languages)installation.md
Set up an AI agent inboxInstall the agent-email-inbox skill — covers security levels for untrusted input

SDK Version Requirements

Always install the latest SDK version. These are the minimum versions for full functionality (sending, receiving, webhook verification):

LanguagePackageMin VersionInstall
Node.jsresend>= 6.14.0npm install resend
Pythonresend>= 2.34.0pip install resend
Goresend-go/v3>= 3.11.0go get github.com/resend/resend-go/v3
Rubyresend>= 1.6.0gem install resend
PHPresend/resend-php>= 1.1.0composer require resend/resend-php
Rustresend-rs>= 0.26.1cargo add resend-rs
Javaresend-java>= 4.16.0See installation.md
.NETResend>= 0.2.1dotnet add package Resend

If the project already has a Resend SDK installed, check the version and upgrade if it's below the minimum. Older SDKs may be missing webhooks.verify(), emails.receiving.get(), or domains.claims.*.

See installation.md for full installation commands, language detection, and cURL fallback.

Common Setup

API Key

Store in environment variable — never hardcode:

export RESEND_API_KEY=re_xxxxxxxxx

Get your key at resend.com/api-keys.

Detect Project Language

Check for these files: package.json (Node.js), requirements.txt/pyproject.toml (Python), go.mod (Go), Gemfile (Ruby), composer.json (PHP), Cargo.toml (Rust), pom.xml/build.gradle (Java), *.csproj (.NET).

Common Mistakes

#MistakeFix
1Retrying without idempotency keyAlways include idempotency key — prevents duplicate sends on retry. Format: <event-type>/<entity-id>
2Not verifying webhook signaturesAlways verify with resend.webhooks.verify() — unverified events can't be trusted
3Template variable name mismatchVariable names are case-sensitive — must match the template definition exactly. Use triple mustache {{{VAR}}} syntax
4Expecting email body in webhook payloadWebhooks contain metadata only — call resend.emails.receiving.get() for body content
5Using try/catch for Node.js SDK errorsSDK returns { data, error } — check error explicitly, don't wrap in try/catch
6Using batch for emails with attachmentsBatch doesn't support attachments — use single sends instead
7Testing with fake emails (test@gmail.com)Use delivered@resend.dev — fake addresses bounce and hurt reputation
8Sending with draft templateTemplates must be published before sending — call .publish() first
9html + template in same send callMutually exclusive — remove html/text/react when using template
10MX record not lowest priority for inboundEnsure Resend's MX has the lowest number (highest priority) or emails won't route
11403 when sending from resend.devThe default onboarding@resend.dev is a sandbox — it can only deliver to your Resend account email. Verify your own domain first
12403 domain mismatchThe from address domain must exactly match a verified domain. Verified send.acme.com but sending from user@acme.com will fail
13Calling Resend API from the browser (CORS)The API does not support CORS — this is intentional to protect your API key. Always call from server-side (API routes, serverless functions)
14401 restricted_api_keyA sending-only API key was used on a non-sending endpoint (domains, contacts, etc.). Create a full-access key instead

Cross-Cutting Concerns

Send + Receive Together

Auto-replies, email forwarding, or any receive-then-send workflow requires both capabilities:

  1. Set up inbound domain first (see receiving.md)
  2. Set up sending (see sending/overview.md)
  3. Note: batch sending does NOT support attachments or scheduling — use single sends when forwarding with attachments

AI Agent Inbox

If your system processes untrusted email content and takes actions (refunds, database changes, forwarding), install the agent-email-inbox skill. This applies whether or not AI is involved — any system interpreting freeform email content from external senders needs security measures.

Marketing Emails

The sending capabilities in this skill are for transactional email (receipts, confirmations, notifications). For marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking, use Resend Broadcasts — see broadcasts.md for the API.

Domain Warm-up

New domains must gradually increase sending volume. Day 1 limit: ~150 emails (new domain) or ~1,000 (existing domain). See the warm-up schedule in sending/overview.md.

Testing

Never test with fake addresses at real email providers (test@gmail.com, fake@outlook.com) — they bounce and destroy sender reputation.

AddressResult
delivered@resend.devSimulates successful delivery
bounced@resend.devSimulates hard bounce
complained@resend.devSimulates spam complaint

Suppression List

Resend automatically suppresses hard-bounced and spam-complained addresses. Sending to suppressed addresses fires the email.suppressed webhook event instead of attempting delivery. Manage in Dashboard → Suppressions.

Webhook Event Types

EventTrigger
email.sentAPI request successful
email.deliveredReached recipient's mail server
email.bouncedPermanently rejected (hard bounce)
email.complainedRecipient marked as spam
email.opened / email.clickedRecipient engagement
email.delivery_delayedSoft bounce, Resend retries
email.receivedInbound email arrived
domain.* / contact.*Domain/contact changes

See webhooks.md for full details, signature verification, and retry schedule.

Error Handling Quick Reference

CodeAction
400, 422Fix request parameters, don't retry
401Check API key — restricted_api_key means sending-only key used on non-sending endpoint
403Verify domain ownership — common causes: resend.dev sandbox, from domain mismatch, unverified domain
409Idempotency conflict — use new key or fix payload
429Rate limited — retry with exponential backoff (default rate limit: 2 req/s)
500Server error — retry with exponential backoff

Resources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.