resend / email-best-practices

The single skill routes through a SKILL.md table of contents into ten reference files: DNS authentication (SPF, DKIM, DMARC) and sender reputation, transactional email design for password resets, OTPs, and order confirmations, marketing-email rules around consent and segmentation, region-specific compliance (CAN-SPAM, GDPR, CASL), email capture and validation, and production concerns like idempotent sends, retry logic, webhook processing, and suppression-list hygiene. It ships as text and reference tables only — no code that calls an email provider, Resend's own included.

This is for anyone building the email side of a product, whether or not they send through Resend — the deliverability, compliance, and reliability material applies to any transactional email provider, since nothing in the skill or its references names a specific sending API.

READ THE FULL ANALYSIS＋

It doesn't mention Resend's own SDK or dashboard once. The one place Resend appears at all is the install command and the repository's owner — the content itself teaches DNS setup, list hygiene, and webhook handling in provider-neutral terms, the same guidance you'd want whether you send through Resend, SES, or Postmark.

It needs nothing to use. Our check finds no account, key, or local tool behind the skill — it is reference material an agent reads and applies, not something that calls out to a live service.