resend-email
Send emails via Resend.com API. Use when the user wants to (1) send an email, (2) email someone, (3) send a message to an email address, (4) send email with attachments, (5) schedule an email for later. Requires RESEND_API_KEY environment variable.
Best use case
resend-email is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Send emails via Resend.com API. Use when the user wants to (1) send an email, (2) email someone, (3) send a message to an email address, (4) send email with attachments, (5) schedule an email for later. Requires RESEND_API_KEY environment variable.
Teams using resend-email should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/resend-email/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How resend-email Compares
| Feature / Agent | resend-email | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Send emails via Resend.com API. Use when the user wants to (1) send an email, (2) email someone, (3) send a message to an email address, (4) send email with attachments, (5) schedule an email for later. Requires RESEND_API_KEY environment variable.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Resend Email
Send emails using the [resend-cli](https://github.com/resend/resend-cli). The CLI authenticates via `RESEND_API_KEY` environment variable.
## Sending Email
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to user@example.com \
--subject "Hello" \
--text "Email body here"
```
Always pass `--json` to get machine-readable output.
### Required Flags
| Flag | Description |
|------|-------------|
| `--from` | Sender address (default to `Claude <claude@ehop.me>`) |
| `--to` | Recipient address(es), repeat flag for multiple |
| `--subject` | Email subject line |
| `--text` or `--html` or `--html-file` | Body content (exactly one required) |
### Optional Flags
| Flag | Description |
|------|-------------|
| `--html` | HTML body as string |
| `--html-file` | Path to an HTML file for the body |
| `--text` | Plain text body |
| `--cc` | CC recipient(s), repeat flag for multiple |
| `--bcc` | BCC recipient(s), repeat flag for multiple |
| `--reply-to` | Reply-to address |
| `--attachment` | File path(s) to attach, repeat flag for multiple |
| `--scheduled-at` | Schedule delivery (ISO 8601, e.g. `2024-12-25T09:00:00Z`) |
| `--headers` | Custom headers as `key=value` pairs |
| `--tags` | Email tags as `name=value` pairs |
### Examples
**Simple text email:**
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to user@example.com \
--subject "Quick update" \
--text "Just a quick note."
```
**HTML email:**
```bash
resend emails send --json \
--from "Newsletter <news@ehop.me>" \
--to user@example.com \
--subject "Newsletter" \
--html "<h1>Hello</h1><p>Welcome to our newsletter.</p>"
```
**With attachments:**
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to user@example.com \
--subject "Report attached" \
--text "Please find the report attached." \
--attachment /path/to/report.pdf \
--attachment /path/to/data.csv
```
**Multiple recipients with CC:**
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to alice@example.com \
--to bob@example.com \
--cc manager@example.com \
--subject "Team update" \
--text "Hi team..."
```
**Scheduled email:**
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to user@example.com \
--subject "Reminder" \
--text "Don't forget!" \
--scheduled-at "2024-12-25T09:00:00Z"
```
**HTML from file:**
```bash
resend emails send --json \
--from "Claude <claude@ehop.me>" \
--to user@example.com \
--subject "Report" \
--html-file ./email.html
```
### Output
Success returns JSON with email ID:
```json
{"id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794"}
```
Errors exit with code 1 and return:
```json
{"error": {"message": "...", "code": "..."}}
```
## Limits
- Sender domain must be verified in Resend dashboard
- Max 50 recipients per email
- Max 40MB total size including attachmentsRelated Skills
stop-slop
Use this skill when writing or editing prose to eliminate predictable AI writing patterns. Helps make writing more direct, authentic, and human.
sonos-control
Control Sonos speakers on Tim's home network. Use when the user wants to (1) play, pause, or stop music on Sonos speakers, (2) change volume on speakers, (3) skip tracks, (4) check what's playing, (5) see speaker status, (6) group or ungroup speakers, (7) any Sonos or music/audio playback task involving home speakers. Triggers on "sonos", "speakers", "play music", "what's playing", "volume", "turn up", "turn down", "pause music", "stop music".
slack-message
Draft and send Slack messages in Tim's natural voice. Use when the user wants to (1) post an update to a channel, (2) draft a Slack message, (3) share something on Slack, (4) send a DM, (5) reply in a thread. Applies Tim's Slack writing style and prose principles automatically.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
sending-to-codex
Delegate tasks or ask questions to OpenAI's Codex CLI from within Claude Code. Use this skill when the user says "ask codex", "send to codex", "delegate to codex", "have codex do this", "get codex's opinion", "run this in codex", or wants to offload a coding task or question to the Codex agent. Supports both fire-and-forget coding tasks (fix bugs, add features, refactor) and research questions (analyze code, explain behavior, get a second opinion).
reviewing-writing
Review and critique writing using Michael Nielsen's principles on craft. Analyzes text for purpose focus, brevity, danger words, opening strength, originality, reader psychology, truthfulness, and title impact. Use when the user says "review my writing", "nielsen review", "writing review", "review this writing", "critique my writing", or asks for feedback on prose quality.
reviewing-code
Review pull requests, branch changes, or code diffs. Triggers on "review this PR", "review my changes", "code review", "review branch", or GitHub PR URLs. Focuses on bugs, tests, complexity, and performance - not linting.
refresh-dotfiles
Full sync of personal (yadm) and work (yadm-work) dotfiles. Pulls remote changes, commits and pushes local changes, and audits for untracked files that should be tracked. Use when the user says 'refresh yadm', 'sync dotfiles', 'dotfiles sync', or 'update dotfiles'.
omnifocus
Interact with OmniFocus task manager via the command-line interface (@stephendolan/omnifocus-cli). Use when the user wants to: (1) Add tasks or projects to OmniFocus, (2) List, view, or search tasks/projects, (3) Update or complete tasks, (4) Manage inbox items, (5) Work with tags and analyze tag usage, (6) Process or organize their OmniFocus database from the command line.
omnifocus-triage
Interactively process OmniFocus inbox items using AskUserQuestion. Use when the user wants to (1) triage their inbox, (2) process inbox items, (3) organize their OmniFocus inbox, (4) clear out their inbox, (5) do a GTD-style inbox review. Triggers on "triage inbox", "process inbox", "organize inbox", "clear inbox", "inbox zero".
Nightshift
Manage and interact with Nightshift, an AI-powered development automation tool that runs coding tasks during off-hours.
modal
Run code on Modal's cloud infrastructure via `uvx modal run`. Use whenever the user wants to (1) validate handbook tutorial shell commands on a fresh Debian container from scratch (uv, pip, build tooling, etc. with no cached state from Tim's laptop), (2) test GPU-specific Python code (torch, CUDA, cupy, transformers, CUDA wheels) on real hardware, or (3) reproduce a "does this actually work from zero?" check. Trigger on phrases like "run this on modal", "test on a fresh machine", "try this on a GPU", "validate from scratch", "does the tutorial work end-to-end", "test this without my venv state", or any mention of modal.com / cloud GPUs / ephemeral containers for verification. Also trigger when the user is writing a handbook tutorial that involves GPU installs (PyTorch, CUDA wheels) and they want to confirm the commands work.