Resend transactional email patterns, React Email templates, domain configuration, and webhook handling. Use when sending emails, building email templates, or configuring email delivery.
70
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Docs: https://resend.com/docs
Env: RESEND_API_KEY (resend.com → API Keys), RESEND_WEBHOOK_SECRET (resend.com → Webhooks).
svix-id, svix-timestamp, svix-signature — passed to new Webhook(process.env.RESEND_WEBHOOK_SECRET).verify(rawBody, headers). Verify against the raw request.text(); parsing the JSON first invalidates the signature. Return 400 on failure, 200 on success. Events: email.delivered, email.bounced, email.complained.from must use a verified domain and the 'Name <no-reply@yourdomain.com>' form. to is an array.react: (not html:); the two are mutually exclusive.dig TXT yourdomain.com — SPF/DKIM records must appear.curl -X POST -H 'Content-Type: application/json' -d '{"type":"email.delivered"}' https://yourapp.com/api/webhooks/resendFailures here are nearly always DNS propagation, a wrong API key scope, or a mismatched webhook secret.
npm install resend @react-email/components. Build templates from @react-email/components primitives (Html, Head, Body, Container, Heading, Text, Button) — plain HTML/CSS is unreliable across clients. Preview locally with npx email dev.
fa0c341
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.