resend
Skill38 starsChanged 8 months agoMITView on GitHub
Send emails, manage domains, contacts and broadcasts via Resend API
- Reads credentials
15 other projects use a version of this.
Adopted by
Most recently taken up by
- vercel-labs/emulatetheir own version, first seen Oct 29, 2026
- TommyBez/skillsboardtheir own version, first seen Oct 25, 2026
- domhhv/habitracktheir own version, first seen Oct 25, 2026
- Nirusan/claude-configtheir own version, first seen Oct 13, 2026
- gerald-donkor/poli-inteltheir own version, first seen Oct 11, 2026
- renatoasse/opensquadtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use email-best-practices, resend-cli and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
sirakinbSkillemail-best-practices
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.
Also in 4 projects that use this
resendSkillresend-cli
Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the `resend` CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running `resend` commands — it contains the non-interactive flag contract and gotchas that prevent silent failures.
Also in 3 projects that use this
VercelSkillreact-email
React Email renderer for json-render that turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render. Use when working with @json-render/react-email, building transactional or marketing emails from JSON, creating email catalogs, rendering AI-generated email specs, or when the user mentions react-email, HTML email, or transactional email.
Also in 4 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- renatoasse/opensquad★ 2.1ksame name
- vercel-labs/emulate★ 2ksame name
- resend/resend-skills★ 211same name
- tdimino/claude-code-minoan★ 41same name
- TommyBez/skillsboard★ 10same name
- domhhv/habitrack★ 8same name
- Nirusan/claude-config★ 7same name
- stonegiantstudio/skills★ 3same name
- kwhinnery/resend-skill-example★ 2same name
- nezaboravi/orkestar★ 2same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- abacatepaySkill
- appsignalSkill
- clickupSkill
- cloudflareSkill
- cloudinarySkill
- datadogSkill
- digitaloceanSkill
- discordSkill
- firebaseSkill
- flyioSkill
- google-sheetsSkill
- herokuSkill
- honeybadgerSkill
- hostingerSkill
- hubspotSkill
- intercomSkill
- jiraSkill
- linearSkill
- mercadopagoSkill
- n8nSkill
- notionSkill
- openaiSkill
- planetscaleSkill
- posthogSkill
- railwaySkill
- rewriteSkill
- sentrySkill
- shopifySkill
- slackSkill
- stripeSkill
- supabaseSkill
- trelloSkill
- twilioSkill
- vercelSkill
- xSkill
- zendeskSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
If the output is OK, proceed to the Flow section.
- Very specific: line 48
If the output is SETUP_NEEDED, guide the user step by step.
- Distinctive: line 67
If the script outputs an error, the key is invalid.
- Very specific: line 154
Add --send to send immediately after creation.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/resend
Connect to Resend to send transactional emails, manage domains, contacts, broadcasts and API keys. Pure Ruby, zero gems — stdlib only.
Structure
scripts/
├── auth.rb # Bearer token auth + resend_request helper (required by all scripts)
├── check_setup.rb # Check if token exists (outputs OK or SETUP_NEEDED)
├── save_token.rb # Save and validate an API key
├── send_email.rb # Send an email
├── email.rb # Get email details
├── emails.rb # List sent emails
├── cancel_email.rb # Cancel a scheduled email
├── domains.rb # List domains
├── domain.rb # Get domain details with DNS records
├── create_domain.rb # Create a domain
├── verify_domain.rb # Verify a domain
├── delete_domain.rb # Delete a domain
├── contacts.rb # List contacts
├── create_contact.rb # Create a contact
├── delete_contact.rb # Delete a contact
├── broadcasts.rb # List broadcasts
├── create_broadcast.rb # Create a broadcast
├── send_broadcast.rb # Send a broadcast
├── delete_broadcast.rb # Delete a broadcast
├── api_keys.rb # List API keys
├── create_api_key.rb # Create an API key
└── delete_api_key.rb # Delete an API keySetup (check before using)
ruby ~/.claude/skills/resend/scripts/check_setup.rbIf the output is OK, proceed to the Flow section.
If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.
Step 1 — Ask the user to get their API key:
You need a Resend API key.
- Go to https://resend.com/api-keys
- Click Create API Key
- Choose a name and permission level (full-access or sending-access)
- Copy the key (starts with
re_)Paste the API key here.
Step 2 — When the user pastes the key, save it:
ruby ~/.claude/skills/resend/scripts/save_token.rb 'PASTED_KEY'If the script outputs an error, the key is invalid. Ask the user to double-check and try again.
If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.
Flow
The argument $ARGUMENTS may contain an action or email address.
Step 1: List domains
ruby ~/.claude/skills/resend/scripts/domains.rbPresent the domains and ask what the user wants to do.
Step 2: Actions
Send an email (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/send_email.rb "Me <me@example.com>" "user@example.com" "Hello" --html "<h1>Hi!</h1>"
ruby ~/.claude/skills/resend/scripts/send_email.rb "me@example.com" "user@example.com" "Hello" --text "Plain text body"Get email details:
ruby ~/.claude/skills/resend/scripts/email.rb EMAIL_IDList sent emails:
ruby ~/.claude/skills/resend/scripts/emails.rbCancel a scheduled email (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/cancel_email.rb EMAIL_IDCreate a domain (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/create_domain.rb example.com
ruby ~/.claude/skills/resend/scripts/create_domain.rb example.com --region sa-east-1Regions: us-east-1 (default), eu-west-1, sa-east-1, ap-northeast-1
Get domain details:
ruby ~/.claude/skills/resend/scripts/domain.rb DOMAIN_IDVerify a domain:
ruby ~/.claude/skills/resend/scripts/verify_domain.rb DOMAIN_IDDelete a domain (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/delete_domain.rb DOMAIN_IDList contacts:
ruby ~/.claude/skills/resend/scripts/contacts.rbCreate a contact (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/create_contact.rb "user@example.com" --first-name "John" --last-name "Doe"Delete a contact (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/delete_contact.rb CONTACT_IDList broadcasts:
ruby ~/.claude/skills/resend/scripts/broadcasts.rbCreate a broadcast (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/create_broadcast.rb SEGMENT_ID "Me <me@example.com>" "Newsletter" --html "<h1>News</h1>" --name "March Newsletter"Add --send to send immediately after creation.
Send a broadcast (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/send_broadcast.rb BROADCAST_ID
ruby ~/.claude/skills/resend/scripts/send_broadcast.rb BROADCAST_ID --scheduled-at "2026-03-10T10:00:00Z"Delete a broadcast (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/delete_broadcast.rb BROADCAST_IDList API keys:
ruby ~/.claude/skills/resend/scripts/api_keys.rbCreate an API key (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/create_api_key.rb "my-key" --permission sending-access --domain-id DOMAIN_IDDelete an API key (requires user confirmation):
ruby ~/.claude/skills/resend/scripts/delete_api_key.rb API_KEY_IDNotes
- Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
- Auth via Bearer token (API key starting with
re_) - Token file:
~/.config/resend/token(outside the repo, never commit) - Requires
User-Agentheader (included automatically in auth helper) - Rate limit: 2 requests/second per team
- Sending emails, managing domains/contacts/broadcasts, and API key operations require explicit user confirmation
- Sender address format:
"Name <email@domain.com>"or plain"email@domain.com" - Scheduled emails support ISO 8601 or natural language dates
- Base URL:
https://api.resend.com
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

