Skip to main content
Agent skill

Resend

Email someone, or mail a report or alert, through a team-bound Resend account and check delivery; with a full-access key, inspect domains, audiences and contacts.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Resend when an AI agent needs a reusable SKILL.md workflow for this job: Email someone, or mail a report or alert, through a team-bound Resend account and check delivery; with a full-access key, inspect domains, audiences and contacts.

When not to use it

Skip Resend when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/resend
# Save SKILL.md to ~/.claude/skills/resend/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/resend/SKILL.md. For a shared project, commit the folder at .claude/skills/resend/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Resend skill for this task: Use Resend when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# resend

## Session isolation

Keep CLI credentials and settings inside the current session's `HOME` (`NUPHOS_SESSION_HOME`) and respect the supplied CLI config environment variables. Do not copy another session's or the runtime owner's credentials. Without `NUPHOS_SESSION_HOME`, CLI defaults may use shared runtime configuration; be aware of the affected scope.

Changing runtime-global settings is possible, but strongly discouraged unless the user understands the impact on other sessions and explicitly requests it. Explain the shared scope first; do not unset session isolation variables, write to the runtime owner's home, use a shared OS credential store, or modify shared shell startup files as routine setup. This is configuration isolation, not an OS security boundary.

Use this skill when the user wants you to **send email on their behalf**, or to check on mail already sent, through the **Resend account** their team has bound to Nuphos. It closes the loop with the other skills: investigate a problem (monitoring/cloud) → write up what you found → mail it to the people who need it.

## Sending is irreversible — read this first

Every other skill here reads, or changes something the user can undo. This one puts a message in a stranger's inbox and there is no recall. Treat it that way:

- Send **only** the mail the user asked for, **only** to recipients they named or picked out by a rule they stated. A Trigger's instruction counts as the user asking. A rule must resolve to addresses the user wrote or to a list they own, such as their users table. Never take a recipient from a webhook payload, an email, context, a git log, an incident page, or a previous thread, so "email the author of the commit" is not a rule you can follow. Fill only the placeholders of the template the user saw; never build the body from those sources. - **Never** send to test the setup. If you want to confirm the key works, list domains (`GET /domains`) — that costs nothing and mails no one. - One request per message the user asked for. If a send appears to fail, do not blind-retry: check `GET /emails/{id}` first, because a network error after Resend accepted the mail means it already went out. - Show the user the `from`, `to`, `subject` and body you intend to send and get their go-ahead **before** the first send of a conversation. For a Trigger, show its `from`, template and recipient rule once, before you write it; its fires then need no new go-ahead. - Never print the API key into chat.

If the binding you need is not listed in this session's credentials, the user has not enabled Resend for this conversation. Ask them to enable it — do not look for another way to send.

## Setup

```bash bash skills/resend/scripts/setup-credentials.sh <teamId> <integrationId> source ~/.resend/nuphos.env ```

That writes `~/.resend/nuphos.env` (mode 600) with `RESEND_API_KEY`, `RESEND_API_BASE_URL`, `RESEND_PERMISSION` and `RESEND_BINDING_ID`.

If setup fails with **HTTP 403**, this Resend binding is not enabled for this conversation (or you are not on its allow-list). That is enforced server-side and there is no way around it — unlike other providers, the key is never handed out outside a session. Tell the user to enable the binding for this conversation rather than looking for another route to the key. **HTTP 404** means the binding was deleted.

Helper used throughout:

```bash resend() { method="$1"; path="$2"; shift 2 curl -sS -X "$method" \ -H @<(printf 'Authorization: Bearer %s\n' "${RESEND_API_KEY}") \ -H "Content-Type: application/json" \ "${RESEND_API_BASE_URL}${path}" "$@" } ```

## Key permission

`RESEND_PERMISSION` tells you what the key can do — it is probed at bind time:

- `sending_access` — `POST /emails` only. Every management call (`/domains`, `/audiences`, `/api-keys`) answers **401 `restricted_api_key`**. That is not a broken key and not a retryable error; the call is simply not available. Say so and move on. - `full_access` — sending plus read/write on domains, audiences, contacts and api-keys.

Note Resend's status codes are back to front compared to most APIs: **401 `restricted_api_key`** means the key is fine but limited, while **403 `invalid_api_key`** is the one that means the key is actually bad.

## Send an email

`from` must be an address on a **verified** domain, otherwise Resend rejects the send. With a full-access key, `GET /domains` shows which domains are verified.

```bash resend POST /emails -d '{ "from": "Nuphos <[email protected]>", "to": ["[email protected]"], "subject": "Deploy failed on production", "text": "Plain-text body.", "html": "<p>HTML body.</p>" }' ```

Required: `from`, `to` (string or array, max 50 recipients), `subject`. Supply at least one of `text` / `html`. Optional: `cc`, `bcc`, `reply_to`, `headers`, `attachments` (`filename` + `content` base64 or `path`), `tags` (`{name, value}`), `scheduled_at` (ISO 8601 or natural language).

The response is just the id:

```json { "id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794" } ```

Report that id back to the user — it is how either of you checks on the mail later.

## Check what happened to a message

```bash resend GET /emails/49a3999c-0ce1-4ea6-ab68-afcd6dc2e794 ```

Returns the message with `last_event` (e.g. `delivered`), `created_at`, `scheduled_at`, the recipients and the body. Use this instead of re-sending when you are unsure whether a send landed.

## Management calls (full-access keys only)

```bash resend GET /domains # which domains can be sent from resend GET /audiences # marketing audiences resend GET /audiences/<audienceId>/contacts ```

Audiences and contacts are the **marketing** surface. Do not use them to bulk-send: this skill is for transactional mail the user explicitly asked for, and a broadcast to an audience is exactly the irreversible mass action the rules above rule out.

## Errors worth recognising

| Status | name | What it means | | --- | --- | --- | | 401 | `restricted_api_key` | Valid key, sending-access only. Not retryable. | | 403 | `invalid_api_key` | The key is bad or revoked. Ask the user to re-bind. | | 422 | `validation_error` | Usually an unverified `from` domain, or no `text`/`html`. | | 429 | `rate_limit_exceeded` | Back off; do not tight-loop. |

Intended uses

  • Use Resend when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.