resend / resend-cli

The skill's own description frames it plainly: load it before running any resend command, because it documents the flag contract an agent needs to avoid a silent failure — non-interactive mode requires every flag up front (resend emails send without --to and --subject errors immediately rather than prompting), the three-way API-key resolution order (--api-key flag, then RESEND_API_KEY, then a stored login), and the --json output mode most commands support for scripting. The CLI itself covers more ground than the one skill documents in depth — sending email, including React Email .tsx templates via --react-email, managing domains, contacts, broadcasts, templates, webhooks, API keys, logs, and automations, plus a resend doctor diagnostic that detects which AI agent it's running under.

This is for someone already scripting Resend from a terminal or a CI pipeline, running commands that all resolve an API key from a flag, an environment variable, or resend login first — there's no offline or sample-data mode. It's a usage guide for one CLI, not a tour of the platform behind it.

READ THE FULL ANALYSIS＋

The fuller Resend platform lives in a separate repository. The README points past this one for the rest of the platform — for API, React Email, and email-best-practices skills, it says to run npx skills add resend/resend-skills instead; installing from this repository gets only the CLI skill.

Our own "official" flag disagrees with the README. The README's first line calls this "The official CLI for Resend," and it lives under the resend GitHub org, but the flag we store for this repository reads false — a mismatch in our data, not a claim that Resend didn't build it.