Resend Email CLI
Use this skill when AIFi needs to send email through Resend from the local
machine. The Resend CLI is already authenticated with the default profile in
macOS Keychain.
Defaults
- Sender:
aifi@ifuryst.com
- CLI command:
resend
- Profile: default, unless the user explicitly asks for another profile
- API key handling: never print, persist, copy, or expose API keys
- Telemetry: set
RESEND_TELEMETRY_DISABLED=1 for agent-run commands
The user decides the recipient, subject, and content at send time. Do not invent
missing required fields. If any of to, subject, or body is absent, ask for
the missing value before sending.
Workflow
Confirm the CLI is available with command -v resend.
For a new environment or suspected auth issue, run:
RESEND_TELEMETRY_DISABLED=1 resend whoami --json
Build the email using the requested to, subject, body, and any optional
fields such as cc, bcc, reply-to, attachments, tags, or schedule.
Prefer a dry run when the content is complex, has attachments, or the user
asks to inspect before sending:
RESEND_TELEMETRY_DISABLED=1 resend emails send \
--from aifi@ifuryst.com \
--to recipient@example.com \
--subject "Subject" \
--text "Plain text body" \
--dry-run
Send exactly what the user approved or requested:
RESEND_TELEMETRY_DISABLED=1 resend emails send \
--from aifi@ifuryst.com \
--to recipient@example.com \
--subject "Subject" \
--text "Plain text body" \
--json
Report the result concisely, including the Resend email id when returned.
Body Handling
- Use
--text for short plain-text messages.
- Use
--html or --html-file only when HTML is requested or clearly needed.
- Use
--text-file - or --html-file - for long bodies to avoid shell quoting
problems.
- Preserve the user's exact intended meaning. Do not add marketing language,
disclaimers, signatures, or extra content unless requested.
Optional Commands
List recent sent emails:
RESEND_TELEMETRY_DISABLED=1 resend emails list --json
Get a sent email:
RESEND_TELEMETRY_DISABLED=1 resend emails get <email-id> --json
Diagnose setup:
RESEND_TELEMETRY_DISABLED=1 resend doctor --json
Safety Gate
Before any real send, verify:
--from is aifi@ifuryst.com
- at least one recipient is explicit
- subject is explicit
- body source is explicit
- attachments, if any, are intended and path-resolved
- scheduled sends include the exact intended time or natural-language schedule
Do not use hidden Resend API keys or direct HTTP calls when the CLI can perform
the task.
1---2name: resend-email-cli3description: Send transactional or operational emails for AIFi through the authenticated Resend CLI. Use when the user asks to send, draft-and-send, test, schedule, or verify email delivery from the AIFi sender address aifi@ifuryst.com using Resend.4---56# Resend Email CLI78Use this skill when AIFi needs to send email through Resend from the local9machine. The Resend CLI is already authenticated with the `default` profile in10macOS Keychain.1112## Defaults1314- Sender: `aifi@ifuryst.com`15- CLI command: `resend`16- Profile: default, unless the user explicitly asks for another profile17- API key handling: never print, persist, copy, or expose API keys18- Telemetry: set `RESEND_TELEMETRY_DISABLED=1` for agent-run commands1920The user decides the recipient, subject, and content at send time. Do not invent21missing required fields. If any of `to`, `subject`, or body is absent, ask for22the missing value before sending.2324## Workflow25261. Confirm the CLI is available with `command -v resend`.272. For a new environment or suspected auth issue, run:2829 ```sh30 RESEND_TELEMETRY_DISABLED=1 resend whoami --json31 ```32333. Build the email using the requested `to`, `subject`, body, and any optional34 fields such as `cc`, `bcc`, `reply-to`, attachments, tags, or schedule.354. Prefer a dry run when the content is complex, has attachments, or the user36 asks to inspect before sending:3738 ```sh39 RESEND_TELEMETRY_DISABLED=1 resend emails send \40 --from aifi@ifuryst.com \41 --to recipient@example.com \42 --subject "Subject" \43 --text "Plain text body" \44 --dry-run45 ```46475. Send exactly what the user approved or requested:4849 ```sh50 RESEND_TELEMETRY_DISABLED=1 resend emails send \51 --from aifi@ifuryst.com \52 --to recipient@example.com \53 --subject "Subject" \54 --text "Plain text body" \55 --json56 ```57586. Report the result concisely, including the Resend email id when returned.5960## Body Handling6162- Use `--text` for short plain-text messages.63- Use `--html` or `--html-file` only when HTML is requested or clearly needed.64- Use `--text-file -` or `--html-file -` for long bodies to avoid shell quoting65 problems.66- Preserve the user's exact intended meaning. Do not add marketing language,67 disclaimers, signatures, or extra content unless requested.6869## Optional Commands7071- List recent sent emails:7273 ```sh74 RESEND_TELEMETRY_DISABLED=1 resend emails list --json75 ```7677- Get a sent email:7879 ```sh80 RESEND_TELEMETRY_DISABLED=1 resend emails get <email-id> --json81 ```8283- Diagnose setup:8485 ```sh86 RESEND_TELEMETRY_DISABLED=1 resend doctor --json87 ```8889## Safety Gate9091Before any real send, verify:9293- `--from` is `aifi@ifuryst.com`94- at least one recipient is explicit95- subject is explicit96- body source is explicit97- attachments, if any, are intended and path-resolved98- scheduled sends include the exact intended time or natural-language schedule99100Do not use hidden Resend API keys or direct HTTP calls when the CLI can perform101the task.