ifuryst/aifi · Archived

resend-email-cli

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 [email protected] using Resend.

First seen Aug 8, 2026

Installation

$ npx skills add ifuryst/aifi --skill resend-email-cli

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ifuryst/aifi · top by installs.

npx skills add ifuryst/aifi

Browse all from ifuryst/aifi

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 22
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,025 B
  • docs SUMMARY.md 260 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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: [email protected]
  • 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 RESENDTELEMETRYDISABLED=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

  1. Confirm the CLI is available with command -v resend.
  2. For a new environment or suspected auth issue, run:

``sh RESENDTELEMETRYDISABLED=1 resend whoami --json ``

  1. Build the email using the requested to, subject, body, and any optional

fields such as cc, bcc, reply-to, attachments, tags, or schedule.

  1. Prefer a dry run when the content is complex, has attachments, or the user

asks to inspect before sending:

``sh RESENDTELEMETRYDISABLED=1 resend emails send \ --from [email protected] \ --to [email protected] \ --subject "Subject" \ --text "Plain text body" \ --dry-run ``

  1. Send exactly what the user approved or requested:

``sh RESENDTELEMETRYDISABLED=1 resend emails send \ --from [email protected] \ --to [email protected] \ --subject "Subject" \ --text "Plain text body" \ --json ``

  1. 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:

``sh RESENDTELEMETRYDISABLED=1 resend emails list --json ``

  • Get a sent email:

``sh RESENDTELEMETRYDISABLED=1 resend emails get <email-id> --json ``

  • Diagnose setup:

``sh RESENDTELEMETRYDISABLED=1 resend doctor --json ``

Safety Gate

Before any real send, verify:

  • --from is [email protected]
  • 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.