Resend Setup

Overview

Send emails through the user's own Resend account. The user provides their Resend API key and you send via their domain.

Setup

Step 0: Check Existing Configuration

Before starting, check whether Resend is already configured:

bun skills/resend-setup/scripts/check-config.ts

The script outputs JSON: { "configured": boolean, "hasApiKey": boolean, "hasWebhookSecret": boolean, "details": string }.

• If configured is true — Resend is already set up. Offer to verify the connection or reconfigure.
• If configured is false — continue to Step 1.

Step 1: Store the API Key

Run the store script to securely collect the API key:

bun skills/resend-setup/scripts/store-api-key.ts

The script opens a secure credential prompt, stores the key with the correct injection templates, and exits. If it exits 0, the key is stored. Exit code 130 means the user cancelled the prompt — nothing was stored; that's a valid choice, not an error, so ask whether they'd like to try again rather than treating it as a failure. Any other non-zero exit is a real failure. Never ask for the key in chat.

Step 2: Detect the Domain

After storing the API key, automatically detect the user's domain — don't ask them for it. Call the Resend Domains API:

curl -s https://api.resend.com/domains \
  -H "Content-Type: application/json"

Run this with network_mode: "proxied" and the resend credential so the Authorization header is injected automatically. The response contains a data array of domain objects with name and status fields. Pick the first domain with "status": "verified" (or the only domain if there's just one). If no verified domains are found, tell the user they need to verify a domain in their Resend dashboard first.