home / skills / andrelandgraf / fullstackrecipes / resend-setup

resend-setup skill

safe

/.agents/skills/resend-setup

This skill helps you configure Resend for transactional emails like password resets and verifications across your app.

npx playbooks add skill andrelandgraf/fullstackrecipes --skill resend-setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

444 B

---
name: resend-setup
description: Configure Resend for transactional emails like password resets and email verification.
---

# Resend Setup

To set up Resend Setup, refer to the fullstackrecipes MCP server resource:

**Resource URI:** `recipe://fullstackrecipes.com/resend-setup`

If the MCP server is not configured, fetch the recipe directly:

```bash
curl -H "Accept: text/plain" https://fullstackrecipes.com/api/recipes/resend-setup
```

Overview

This skill configures Resend for sending transactional emails such as password resets and email verifications. It provides step-by-step guidance and production-ready patterns to integrate Resend into a TypeScript full-stack app. The goal is a secure, reliable setup for transactional flows with templates, API keys, and deliverability checks.

How this skill works

The skill walks through registering a Resend API key, wiring the key into server-side environment variables, and creating/sendable email templates for verification and reset flows. It shows how to call Resend’s API from backend routes or server functions, handle response errors, and test delivery. It also covers common production considerations like rate limits, retries, and webhook handling for bounces and complaints.

When to use it

You need reliable transactional emails (password resets, email confirmations).
Setting up or migrating transactional email provider to Resend.
Implementing server-side email flows in a TypeScript full-stack app.
Creating reusable email templates for multiple environments (dev/staging/prod).
Ensuring deliverability and handling bounces or unsubscribe events.

Best practices

Store the Resend API key in environment variables and never expose it to client code.
Use templated emails with variables for localization and personalization.
Send transactional emails only from server-side endpoints or secure server functions.
Implement retry and exponential backoff for transient API errors; log failures for monitoring.
Verify DNS and domain settings (SPF, DKIM) to maximize deliverability.
Set up webhooks to track bounces, complaints, and delivery status and act on them (e.g., suppress lists).

Example use cases

Password reset flow: generate short-lived token, send template with reset link via Resend.
Email verification: send confirmation email after signup using a verification template and token.
Order receipt or account change notifications triggered by server events.
Staging vs production: use different API keys/templates per environment to avoid polluting production data.
Automated monitoring: send daily or event-driven alerts to admins when bounce or spam reports exceed thresholds.

FAQ

Do I need a server to use Resend for transactional emails?

Yes. Transactional email API keys must be used from server-side code or secure server functions; never embed them in client apps.

How do I test emails without spamming users?

Use staging API keys and test recipient addresses. Many providers support suppression lists or test modes; also verify templates using Resend’s preview tools before sending live.