resend-cli
Resend CLI
Run bunx --bun resend-cli@latest from the user's project directory, where templates, attachment paths, and env files resolve. Never install the CLI globally or through npm, npx, pnpm, or yarn. Helpers live under the skill directory:
RESEND_SKILL_DIR="${RESEND_SKILL_DIR:-$HOME/.agents/skills/resend-cli}"
Explicit user instructions override anything below.
Access
RESEND_API_KEY in the environment authenticates everything; it never appears in --api-key, arguments, output, commits, or generated env files. Use sending_access scoped to a domain for send-only automation and full_access only for management. Helpers read the key from the shell, then the nearest .env.local, then .env walking upward; check the key source and team from whoami -q before a mutation so a parent env file does not silently select the team. Multiple teams: one explicit environment per operation; RESEND_PROFILE=<name> only when the user already uses stored profiles.
bash "$RESEND_SKILL_DIR/scripts/resend-ensure.sh" checks Bun, the CLI, curl, jq, key source, and authentication with read-only calls; run it only when the task needs live access. resend open, resend docs, and resend login need the user's explicit request. Missing dependencies are reported, never installed automatically.
Help without exposing the key: env -u RESEND_API_KEY bunx --bun resend-cli@latest <group> <command> --help, or commands --json for the full catalog. Current help beats any example here; for version-sensitive behavior beyond it, use Context7 with official Resend docs.