resend

Emulate the Resend email API locally with an in-memory store.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rally19/goform --skill resend-rally19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resend
Source: https://github.com/rally19/goform/tree/main/.qwen/skills/resend
Command: npx skills add https://github.com/rally19/goform --skill resend-rally19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emulated Resend email API for local development and testing. Use when the user needs to send emails locally, test transactional email flows, implement magic link or verification code auth, inspect sent emails, manage domains/contacts/API keys, or work with the Resend API without sending real emails. Triggers include "Resend API", "emulate Resend", "send email locally", "test email", "magic link", "verification email", "email inbox", "RESEND_BASE_URL", or any task requiring a local email API.

Core Features & Use Cases

  • Fully stateful Resend email API emulation with in-memory persistence of emails, domains, API keys, audiences, and contacts.
  • Inspect sent emails via inbox UI or REST endpoints, enabling end-to-end testing of transactional emails.
  • Use cases include local development of verification/magic link flows, sandbox testing, and API integration without sending real emails.

Quick Start

Run the emulator with npx emulate --service resend and point your app to the emulator URL.

Frequently Asked Questions about resend

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

FAQPage Schema
How do I test Resend transactional emails locally without sending real messages?

Test Resend transactional emails locally by running the emulator with `npx emulate --service resend` and pointing your app to the emulator URL. This fully stateful local API emulation intercepts email sending using an in-memory store, preventing real messages from being delivered.

How can I inspect sent emails and check magic link verification flows during local development?

Inspect sent emails and check magic link verification flows via the emulator's built-in inbox UI or REST endpoints. The emulator captures all outgoing emails in-memory, allowing you to verify verification codes and end-to-end transactional email workflows locally.

Do I need a Node.js runtime to emulate the Resend API for local email testing?

Yes, you need a Node.js runtime to emulate the Resend API locally. The emulator requires Node.js to execute the command line interface and maintain the in-memory store that persists emails, domains, API keys, audiences, and contacts during your active development session.

Does the local Resend emulator support managing domains, audiences, and contacts?

Yes, the local Resend emulator supports managing domains, audiences, and contacts. It provides a fully stateful API emulation that persists all these resources in-memory, enabling complete sandbox testing of API integrations without connecting to the live Resend service.

What are the limitations of using an in-memory store for local email API emulation?

The limitation of using an in-memory store for local email API emulation is that state is only persisted during the active session. When the emulator process stops, all stored emails, domains, API keys, audiences, and contacts are cleared, requiring fresh setup for each new testing session.