Install
npx skills add resend/resend-skillsWho it is for
If you already send with Resend and want a coding agent to send and receive mail in the Agent Skills format, instead of assembling the API yourself, this set fits. The explainer is
https://github.com/resend/resend-skills
The format notes are
https://agentskills.io/
The better fit already has a Resend account and a verified domain, can run npx locally, and accepts only the skill install command below. After install you will be asked to tick the skills to install. The plugin form can also register hosted MCP at
https://mcp.resend.com/mcp
Source is
https://github.com/resend/resend-mcp
MCP uses OAuth. The first client connection walks you through sign-in; that path does not need another API key or request headers. The skill path instead requires the environment variable RESEND_API_KEY. Do not merge the two auth styles into one undocumented setup.
If you still lack a verified domain, finish domain verification first. Do not use the skills to blast unauthorized recipients. The first run should draft or check a test message, then send only after you confirm. Do not read named environments as the only usable clients.
First try in 3 minutes
Skills use only this official install path:
npx skills add resend/resend-skills
Then tick the skills to install as prompted. Do not hunt for a marketplace or a second skills add. Restart the agent after install.
Prerequisite: a Resend account and a verified domain. If you use API calls inside the skills, put the secret in RESEND_API_KEY. Do not put the secret in chat or the code repository. If you use MCP, sign in with the client's OAuth.
In an agent that already has the skills, do a low-risk task: ask it to draft plain text to a test inbox you control, first print the recipient, sending domain, and whether it will call the send API at once, and do not send yet. After you confirm the domain and recipient, allow this one send.
Success signal: you see the message in the test inbox, or MCP/the skill returns an accepted send receipt — not a blast to unknown addresses. If it says the domain is unverified or RESEND_API_KEY is missing, go back to the Resend console for prerequisites. Do not change the install package name. If MCP asks you to sign in, use OAuth; do not hand-write undocumented request headers.
Use cases
Case 1: Send mail. The pack is for send and receive. The first time, send only one message to your own test address. First check that the sending domain is verified and the body has no secrets. Official docs do not name a concrete slash command; triggering follows the installed skill names. Do not send before you confirm.
Case 2: Receive, or inspect read-only through MCP. The overview includes receiving mail; MCP gives tool access to the full Resend API. First list read-only actions around inbox or domains; do not change templates or delete domains. This page gives no receive polling command or webhook setup. When those are missing, stay with the read-only tools the skill/MCP itself exposes; do not invent endpoints. Skills marked Synced from must not be edited in this repository; the next sync will overwrite. Change the source repository instead.
Limits
Without a verified domain, do not send to real users. The skill path requires the API key in RESEND_API_KEY. The MCP path uses OAuth and does not need extra request headers. Do not put secrets in the prompt.
Official skill install is only npx skills add resend/resend-skills then tick. MCP is a tool channel, not a second skill installer. The page mentions any Agent Plugins client; that is not an invitation to invent a marketplace install.
Send, receive, and API calls all have external side effects. Confirm recipient and domain first. Do not edit Synced from files in this repository. This page does not list every skill filename; do not treat unticked capabilities as installed.