Slash Command

/send-email

Sends an email via the Resend API after collecting recipient, subject, and content from the user. Formats the body as clean HTML for a professional appearance.

REST API

automation

Popularity

Stars

Forks

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/searchatlas:send-email

Model invocable

No pre-commands

Referenced Files

Files this command reads when invoked

example.comresend.dev

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /searchatlas:send-email

Send an email via the Resend API.

## Instructions

### Prerequisites

The user must have `RESEND_API_KEY` and `EMAIL_FROM` set in their `.env` file. If not configured, direct them to:
1. Sign up at https://resend.com
2. Create an API key under API Keys
3. (Optional) Verify a sender domain under Domains
4. Add `RESEND_API_KEY` and `EMAIL_FROM` to `.env`

For testing without a verified domain, they can use `[email protected]` as the from address.

### Step 1: Collect Details

Ask the user for:
- **Recipient email** — who should receive this?
- **Subject** — wha...

Command Content

75 lines · ~478 tokens

Stats

LanguageHTML

Stars7

Forks3

MaintenanceExcellent

Last CommitJun 1, 2026

Actions

View Source View Plugin View on GitHub View README

/searchatlas:send-email

Send an email via the Resend API.

Instructions

Prerequisites

The user must have RESEND_API_KEY and EMAIL_FROM set in their .env file. If not configured, direct them to:

Sign up at https://resend.com
Create an API key under API Keys
(Optional) Verify a sender domain under Domains
Add RESEND_API_KEY and EMAIL_FROM to .env

For testing without a verified domain, they can use [email protected] as the from address.

Step 1: Collect Details

Ask the user for:

Recipient email — who should receive this?
Subject — what's the email about?
Content — what should the body say?

Common patterns:

Send a client their monthly SEO report
Share workflow results (e.g., "email the PPC report to the client")
Custom update or notification

Step 2: Format Body

Compose the email body as HTML:

Use <h1>, <h2> for headings
Use <p> for paragraphs
Use <ul><li> for bullet lists
Use <strong> for bold, <a href=""> for links
Use <table> for tabular data (metrics, comparisons)

Keep formatting clean and professional.

Step 3: Send

Use the integrations/email/send-email.sh script:

source .env
bash "$CLAUDE_PLUGIN_ROOT/integrations/email/send-email.sh" "$RESEND_API_KEY" "$EMAIL_FROM" "[email protected]" "Subject" "<html body>"

Step 4: Confirm

Show the user what was sent and confirm delivery.

Output Format

✅ Email sent

📧 To: {recipient}
📋 Subject: {subject}
📝 Preview:
   {body preview — first ~200 chars of plain text}

Golden Rules

Never expose the API key in output
Always show a preview before sending
Always confirm the recipient address before sending
Format body as clean HTML, not markdown