← ClaudeAtlas

resend-clilisted

Operate Resend from a coding-agent terminal with the official resend-cli and bundled REST helpers. Use when the agent needs to send, schedule, inspect, forward, or cancel emails; manage inbound email, domains, API keys, contacts, contact properties, segments, topics, broadcasts, templates, webhooks, automations, events, suppression entries, or API logs; diagnose Resend authentication or delivery; invoke resend-cli; or translate a Resend MCP workflow to shell commands. Do not use for application runtime integration through a Resend SDK, continuous monitoring, non-Resend email providers, or Resend MCP server configuration.
arthjean/skills · ★ 3 · AI & Automation · score 66
Install: claude install-skill arthjean/skills
# Resend CLI Operate Resend through `bunx --bun resend-cli@latest`. Keep the working directory in the user's project so local email templates, attachment paths, and project environment files resolve correctly. ## Operating contract 1. Set the absolute directory containing this `SKILL.md` as `RESEND_SKILL_DIR`. In a standard user installation: ```bash RESEND_SKILL_DIR="${RESEND_SKILL_DIR:-$HOME/.agents/skills/resend-cli}" ``` 2. Do not `cd` into the skill directory. Invoke bundled scripts with `bash "$RESEND_SKILL_DIR/scripts/<script>.sh"` from the target project. 3. Use `bunx --bun resend-cli@latest`. Do not install the CLI globally and do not use npm, npx, pnpm, or yarn. 4. Authenticate with `RESEND_API_KEY` in the environment. Never pass a literal key through `--api-key`, command arguments, output, committed files, or generated environment files. 5. Prefer the official CLI. Use the bundled scripts only for raw REST calls, deterministic shell pipelines, or an option the CLI does not expose. 6. Keep browser use opt-in. Do not run `resend open`, `resend docs`, or any command that opens a browser unless the user explicitly requested it. Do not persist credentials with `resend login` unless the user explicitly requested profile storage. 7. Require explicit intent and an unambiguous team, recipient, or resource before any send, broadcast, event trigger, create, update, delete, cancellation, or key rotation. An exact user request is authorization; do not add a redund