resend
Skill1 starsChanged 10 months agoMITView on GitHub
Manage Resend email workflows including sending email, inspecting received (inbound) messages and attachments, configuring domains, and managing contacts, broadcasts, API keys, teams, and webhooks. Use when user asks about Resend email operations or account setup.
- Pipes a download into a shell
- Reads credentials
- Installs packages
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Create an API key at https://resend.com/api-keys
- Very specific: line 165
Use resend --help and resend <command> --help to inspect the latest subcommands and flags
“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 CLI
Official CLI for the Resend email API.
Installation
# Preferred install methods
brew install resend/cli/resend
# Or use the official installer
curl -fsSL https://resend.com/install.sh | bashSetup
- Create an API key at https://resend.com/api-keys
- Authenticate with one of:
resend login # or export RESEND_API_KEY="re_your_key" - For sending email, verify a domain first:
resend domains create --name example.com resend domains verify <domain-id> - For inbound email commands, create a domain with receiving enabled:
resend domains create --name example.com --receiving - Optional: manage multiple accounts with team profiles:
resend login --team work export RESEND_TEAM="work"
Commands
Authentication and Status
resend login # Store API key locally
resend logout # Remove stored API key
resend whoami # Show current auth source/team
resend doctor # Validate CLI setup, auth, domains, agents
resend open # Open the Resend dashboardEmails
resend emails send --from you@example.com --to user@example.com --subject "Hello" --text "Hi"
resend emails batch --file ./emails.json
resend emails receiving list --limit 25
resend emails receiving get <email-id>
resend emails receiving attachments <email-id>
resend emails receiving attachment <email-id> <attachment-id>Domains
resend domains list
resend domains create --name example.com --receiving
resend domains get <domain-id>
resend domains verify <domain-id>
resend domains update <domain-id> --tls enforced --open-tracking
resend domains delete <domain-id> --yesAPI Keys and Teams
resend api-keys list
resend api-keys create --name "CI Token"
resend api-keys delete <key-id> --yes
resend teams list
resend teams switch <team-name>
resend teams remove <team-name>Contacts, Segments, Topics, Broadcasts
resend contacts list
resend contacts create --email jane@example.com --first-name Jane
resend contacts get jane@example.com
resend contacts update jane@example.com --unsubscribed
resend contacts delete jane@example.com --yes
resend contact-properties list
resend segments list
resend topics list
resend broadcasts list
resend broadcasts create --from hello@example.com --subject "Launch" --segment-id <segment-id> --html "<p>Hi</p>"
resend broadcasts send <broadcast-id>Webhooks
resend webhooks list
resend webhooks create --endpoint https://app.example.com/hooks/resend --events all
resend webhooks get <webhook-id>
resend webhooks update <webhook-id> --status disabled
resend webhooks delete <webhook-id> --yesUsage Examples
User: "Send a status email to the team"
resend emails send \
--from hello@example.com \
--to team@example.com \
--subject "Status update" \
--text "Everything is green."User: "Do I have any new inbound emails?"
resend emails receiving list --limit 5User: "Show me the latest email"
resend emails receiving list --json | jq -r '.data[0].id'
resend emails receiving get <id>User: "What attachments are on that email?"
resend emails receiving attachments <email_id>User: "Set up a receiving domain"
resend domains create --name example.com --receivingUser: "What domains do I have set up?"
resend domains listNotes
- Global flags:
--api-key,--team,--json,--quiet,--version,--help - JSON output is useful for agents and scripts; piping output also switches to machine-readable mode
- Inbound email commands live under
resend emails receiving ..., notresend email ... - Received email IDs, domain IDs, broadcast IDs, webhook IDs, and contact IDs are shown in list output
- Use
resend --helpandresend <command> --helpto inspect the latest subcommands and flags
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★ 206same name
- tdimino/claude-code-minoan★ 41same name
- alanalvestech/hitank★ 38same name
- TommyBez/skillsboard★ 10same name
- domhhv/habitrack★ 8same name
- Nirusan/claude-config★ 7same 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.
Used alongsideProjects with it also use resend-cli, email-best-practices 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.
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
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
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
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.

