Best for
- 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, broadca…
resend/resend-skills/skills/resend/SKILL.md
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 verifi
Decision brief
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 verifi
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/resend/resend-skills --skill "skills/resend"Inspect the Agent Skill "resend" from https://github.com/resend/resend-skills/blob/cd37d96c50fd3043cf989c22902e5620bea58371/skills/resend/SKILL.md at commit cd37d96c50fd3043cf989c22902e5620bea58371. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Store in environment variable — never hardcode:
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.
Batch is atomic — if one email fails validation, the entire batch fails. Always validate before sending. Batch does NOT support attachments or scheduledat.
Batch is atomic — if one email fails validation, the entire batch fails. Always validate before sending. Batch does NOT support attachments or scheduledat.
Prevent duplicate emails when retrying failed requests:
Permission review
The documentation includes sending, uploading, or posting data to a remote service.
| 4 | **Expecting email body in webhook payload** | Webhooks contain metadata only — call `resend.emails.receiving.get()` for body content |The documentation includes network, browsing, or remote request actions.
| 4 | **Expecting email body in webhook payload** | Webhooks contain metadata only — call `resend.emails.receiving.get()` for body content |Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 94/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 167 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
import { Resend } from 'resend';
const resend = new Resend(process.env.RESEND_API_KEY);
const { data, error } = await resend.emails.send(
{
from: 'Acme <[email protected]>',
to: ['[email protected]'],
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.
import resend
import os
resend.api_key = os.environ["RESEND_API_KEY"]
email = resend.Emails.send({
"from": "Acme <[email protected]>",
"to": ["[email protected]"],
"subject": "Hello World",
"html": "<p>Email body here</p>",
}, idempotency_key=f"welcome-email/{user_id}")
| Choose | When |
|---|---|
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.
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) |
| Expiration | 24 hours |
| Max length | 256 characters |
| Same key + same payload | Returns original response without resending |
| Same key + different payload | Returns 409 error |
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.
| Task | Reference |
|---|---|
| Send a single email | sending/overview.md — parameters, deliverability, testing |
| Send batch emails | sending/overview.md → sending/batch-email-examples.md |
| Full SDK examples (Node.js, Python, Go, cURL) | sending/single-email-examples.md |
| Idempotency, retries, error handling | sending/best-practices.md |
| Get, list, reschedule, cancel emails, retrieve metrics | sending/email-management.md |
| Receive inbound emails | receiving.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 keys | api-keys.md — permission scoping, domain restrictions |
| View API request logs | logs.md — list and retrieve API call history, debugging |
| Define contact properties | contact-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 inbox | Install the agent-email-inbox skill — covers security levels for untrusted input |
Always install the latest SDK version. These are the minimum versions for full functionality (sending, receiving, webhook verification):
| Language | Package | Min Version | Install |
|---|---|---|---|
| Node.js | resend | >= 6.14.0 | npm install resend |
| Python | resend | >= 2.34.0 | pip install resend |
| Go | resend-go/v3 | >= 3.11.0 | go get github.com/resend/resend-go/v3 |
| Ruby | resend | >= 1.6.0 | gem install resend |
| PHP | resend/resend-php | >= 1.1.0 | composer require resend/resend-php |
| Rust | resend-rs | >= 0.26.1 | cargo add resend-rs |
| Java | resend-java | >= 4.16.0 | See installation.md |
| .NET | Resend | >= 0.2.1 | dotnet 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(), ordomains.claims.*.
See installation.md for full installation commands, language detection, and cURL fallback.
Store in environment variable — never hardcode:
export RESEND_API_KEY=re_xxxxxxxxx
Get your key at resend.com/api-keys.
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).
| # | Mistake | Fix |
|---|---|---|
| 1 | Retrying without idempotency key | Always include idempotency key — prevents duplicate sends on retry. Format: <event-type>/<entity-id> |
| 2 | Not verifying webhook signatures | Always verify with resend.webhooks.verify() — unverified events can't be trusted |
| 3 | Template variable name mismatch | Variable names are case-sensitive — must match the template definition exactly. Use triple mustache {{{VAR}}} syntax |
| 4 | Expecting email body in webhook payload | Webhooks contain metadata only — call resend.emails.receiving.get() for body content |
| 5 | Using try/catch for Node.js SDK errors | SDK returns { data, error } — check error explicitly, don't wrap in try/catch |
| 6 | Using batch for emails with attachments | Batch doesn't support attachments — use single sends instead |
| 7 | Testing with fake emails ([email protected]) | Use [email protected] — fake addresses bounce and hurt reputation |
| 8 | Sending with draft template | Templates must be published before sending — call .publish() first |
| 9 | html + template in same send call | Mutually exclusive — remove html/text/react when using template |
| 10 | MX record not lowest priority for inbound | Ensure Resend's MX has the lowest number (highest priority) or emails won't route |
| 11 | 403 when sending from resend.dev | The default [email protected] is a sandbox — it can only deliver to your Resend account email. Verify your own domain first |
| 12 | 403 domain mismatch | The from address domain must exactly match a verified domain. Verified send.acme.com but sending from [email protected] will fail |
| 13 | Calling 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) |
| 14 | 401 restricted_api_key | A sending-only API key was used on a non-sending endpoint (domains, contacts, etc.). Create a full-access key instead |
Auto-replies, email forwarding, or any receive-then-send workflow requires both capabilities:
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.
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.
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.
Never test with fake addresses at real email providers ([email protected], [email protected]) — they bounce and destroy sender reputation.
| Address | Result |
|---|---|
[email protected] | Simulates successful delivery |
[email protected] | Simulates hard bounce |
[email protected] | Simulates spam complaint |
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.
| Event | Trigger |
|---|---|
email.sent | API request successful |
email.delivered | Reached recipient's mail server |
email.bounced | Permanently rejected (hard bounce) |
email.complained | Recipient marked as spam |
email.opened / email.clicked | Recipient engagement |
email.delivery_delayed | Soft bounce, Resend retries |
email.received | Inbound email arrived |
domain.* / contact.* | Domain/contact changes |
See webhooks.md for full details, signature verification, and retry schedule.
| Code | Action |
|---|---|
| 400, 422 | Fix request parameters, don't retry |
| 401 | Check API key — restricted_api_key means sending-only key used on non-sending endpoint |
| 403 | Verify domain ownership — common causes: resend.dev sandbox, from domain mismatch, unverified domain |
| 409 | Idempotency conflict — use new key or fix payload |
| 429 | Rate limited — retry with exponential backoff (default rate limit: 2 req/s) |
| 500 | Server error — retry with exponential backoff |
Frequently asked questions
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 verifi
The source record exposes this install command: npx skills add https://github.com/resend/resend-skills --skill "skills/resend". Inspect the command and pinned source before running it.
Static rules flagged send-data, network in the source; the page lists the matching lines and excerpts.
Alternatives
github/awesome-copilot
Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from
bestdeejay-design/agent-skills
Audit and polish frontend (static HTML/CSS/JS or built SPA) to measurable perfection: real-Chrome Lighthouse >=13 runs (mobile+desktop, no Playwright internals), SEO meta layer, WCAG contrast by computed luminance, heading order, a11y checks (axe-core subset: img-alt/button-name/link-name/label/aria-valid/landmark-unique), back-to-top navigation check, design tokens (zero raw hex outside tokens), adaptive checks, and OG-image generation with a crop-safe layout. Front-End Checklist-inspired check
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
indranilbanerjee/contentforge
Generate 3-10 scored A/B test variations of a single content element — headline, hook, CTA, intro, or conclusion — each rated across 6 quality dimensions and ranked by your optimization goal (clicks, engagement, conversions, or readability), with top-3 recommendations and A/B test setup guidance (sample size, duration, success metric). Triggers on "/contentforge:cf-variants", "give me headline alternatives", "A/B test options for this CTA", "which hook is stronger", "write 5 versions of this int