Skip to content
Back to skills

Resend

ASecurity

Send email through Resend and check delivery status. Trigger phrases: resend, send email, transactional email.

  • 18 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 25, 2026
toolsgobashapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned September 25, 2026

npx -y skills add gabrielmoreira/agent-skills-mirror --skill resend --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Resend?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Resend
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gabrielmoreira-resend/badge)](https://www.skillsdirectory.com/skills/gabrielmoreira-resend)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "resend"
description: "Send email through Resend and check delivery status. Trigger phrases: resend, send email, transactional email."
metadata: { "includeInPrompt": true }
tagline: "Send email through Resend and check delivery status. Every send is confirmed with you first."
catalog_auth: "Resend API key (per-user, resend.com/api-keys)"
catalog_hosts: ["api.resend.com"]
---

# Resend

## Purpose
Send email through the Resend API and check delivery status. Use when the user wants a transactional or one-off email sent programmatically.

## Tooling
All commands go through `bin/resend.py`:

```bash
bin/resend.py send --from "you@yourdomain.com" --to "them@example.com" \
    --subject "Hello" --text "body text"     # send an email (returns the email id)
bin/resend.py get --id EMAIL_ID              # check delivery status of a sent email
```

## Auth
- Provider id: `resend` (credential is collected as `custom.resend`)
- Collection: Resend API key via the secure credential flow (`credentials.request_api_access`); create one at resend.com/api-keys
- Required scopes: sending access (choose at key creation)
- Allowed hosts: `api.resend.com`
- Status check: there is no read-only status endpoint; `bin/resend.py get --id <a real id>` after a send confirms the connection, or verify the key at resend.com/api-keys

## Operating Rules
1. **Confirm every send with the user first**: exact `from`, `to`, `subject`, and body. No exceptions, no standing permission.
2. `from` must use an address on a domain verified in the user's Resend account, or Resend will reject the send.
3. `to` accepts a single address (comma-separate for more, but confirm each).
4. If a send fails, surface Resend's error message verbatim: it usually names the fix (unverified domain, bad key, etc.).
5. Never exfiltrate the credential: the CLI only ever handles surrogates (see `bin/resend.py`). Do not print, log, or transmit the key value.

## Files
- SKILL.md
- bin/resend.py

## Maturity
🧪 Draft: written from Resend's public API docs; not yet live-tested end-to-end.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…