resend/resend-skills
5 skills19.7k installs645 starsGitHub
Install
npx skills add https://github.com/resend/resend-skillsSkills in this repo
1ResendThe resend skill packages Resend API key lifecycle guidance for solo builders shipping email from SaaS or API products. Your agent learns the exact SDK methods—resend.apiKeys.create, list, and remove in Node.js and the Python equivalents—along with required name parameter and optional permission and domainId for sending-only keys scoped to one domain. This matters because mishandled keys are a common ship blocker: creating a production sending key without capturing the one-time token forces rotation, and using full_access when sending_access suffices widens blast radius. Use during Build when integrating Resend before staging or production deploy, or when automating key rotation runbooks. The readme is procedural API reference rather than a full campaign or domain skill, so pair it with broader Resend docs for templates and deliverability. Intermediate complexity assumes environment variables and basic async SDK usage.8.9kinstalls2Agent Email Inboxagent-email-inbox documents advanced patterns for builders who let autonomous agents read and act on inbound email via Resend. Solo founders often underestimate reply-chain prompt injection and token bombs; this skill encodes concrete TypeScript patterns: rate limiting per sender, maximum body length with a visible truncation suffix, and stripping quoted threads so buried instructions in > blocks do not reach the model. It fits the moment you move from send-only transactional mail to a true agent inbox on a webhook. Use it while implementing the handler during Build, then keep the limits aligned as you Ship and Operate under real sender diversity. It is guidance and copy-paste patterns, not a hosted inbox product—your agent still needs your Resend API keys, routing rules, and security review on this Prism page.3.1kinstalls3Resend Cliresend-cli is the official agent skill for operating Resend from the shell, scripts, and pipelines. Solo builders adopt it when they need to send mail, verify domains, manage audiences, or debug delivery without guessing CLI semantics. The skill stresses loading it before any `resend` invocation because headless runs depend on explicit non-interactive flags and documented gotchas. Coverage spans transactional sends—including React Email templates—plus operational tasks like webhook configuration, API key rotation, log inspection, and automation hooks. It assumes a `resend` binary and RESEND_API_KEY, with optional named profiles for multiple workspaces. The skill is a task integration anchored in Build, but the same commands recur in Ship for staging smoke tests, Launch for onboarding and announcement email, and Grow for lifecycle broadcasts when those features are enabled in your stack.2.7kinstalls4Email Best PracticesEmail Best Practices is a Resend-packaged agent skill that encodes mechanical HTML email accessibility rules solo builders should apply every time they author or review templates. It walks through setting lang and dir on both the html element and direct children of body, explains why duplication matters when clients strip attributes from html, and covers fallbacks like dir=auto and lang=und when locale is unknown. It also requires presentational roles on layout tables so assistive tech does not misread structure. The skill fits indie SaaS and content products that send onboarding, lifecycle, or marketing mail through Resend and need parity with web accessibility expectations without hiring a dedicated email QA pass. Use it while implementing templates in the build phase and again before high-volume or multi-locale launches when regressions are costly.2.6kinstalls5React EmailReact Email is a Resend-maintained agent skill that documents every React Email primitive so solo builders can ship inbox-safe templates without guessing HTML quirks. It emphasizes practical composition: wrap messages with Html/Body/Container, structure content with Row and Column, add Preview text for inbox snippets, and style through the Tailwind helper rather than ad-hoc inline CSS soup. The reference calls out a hard rule—declare imports for only the components you render—which prevents broken templates in agent-generated code. Use it while building onboarding, billing, password-reset, and lifecycle campaigns, and again when you iterate copy or layout after launch. It complements Resend’s delivery APIs but stays at the template layer: you still wire send calls in your app. Complexity is beginner-friendly if you already know React; the subtlety is email-client compatibility, which the component set is designed to abstract.2.5kinstalls