email-best-practices skill
Email practices for an agent: SPF, DKIM and DMARC, transactional and marketing mail, send retries, webhooks and suppression lists
- 146 ★ on the repository
- Last commit
Minimal access
Why this level
- The skill contains reference material only, runs nothing and sends no emails.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/email-best-practicesDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill contains reference material only, runs nothing and sends no emails.
This is third-party code. Review the repository files before installing.
What it does
email-best-practices is the official Resend skill with guidance for building the email side of an application. `SKILL.md` holds a routing table: depending on the task the agent opens the right reference from the `references` folder. There are eleven: deliverability, transactional email, a catalog of emails by app type, marketing email, address capture, compliance, transactional versus marketing, sending reliability, webhooks, list management and email accessibility. Deliverability covers SPF, DKIM and DMARC records, sender reputation, IP warming and handling bounces and complaints. The reliability section explains idempotency keys, retries with exponential backoff and error codes. For webhooks it describes events, signature verification and idempotent processing. The legal reference covers CAN-SPAM, GDPR and CASL, plus the United Kingdom and Brazil. The skill is not tied to Resend: the advice applies to any email provider. The repository also has five test scenarios, for example on spam, duplicate sends and bounce handling.
Who it is for. Backend developers and product owners who build email sending from scratch or look for the reason mail lands in spam.
Good fit when
- Confirmation and password reset emails land in spam and the SPF, DKIM and DMARC records need checking.
- The app needs a list of emails: sign-up, receipt, password reset and notifications, and the agent picks a set for the product type.
- Sending fails on the network, and retries must be added so a customer does not get two identical emails.
- Delivery, bounce and complaint events must be received and a suppression list maintained.
- A mailing to subscribers in the EU and Canada is prepared with GDPR and CASL, consent and unsubscribe in mind.
Not a fit when
- Rules for a Russian mailing are needed: the laws 38-FZ and 152-FZ are not covered in the references.
- A ready sending API or an integration with a specific service is required: the skill gives practices and code examples rather than a client library.
- An email layout must be designed: the skill touches layout only through accessibility.
Example request
Sign-up confirmation emails land in spam. Check our domain against the deliverability checklist and tell me which DNS records to fix.Limitations
The references are written in English and tied to the rules of the US, EU, Canada, the United Kingdom and Brazil, and Russian norms on advertising mailings and personal data are not covered. The legal sections give general guidance and do not replace advice from a lawyer. Examples sometimes use Resend, though the principles are the same for any provider. The skill sends nothing and changes no DNS. The agent drafts SPF, DKIM and DMARC records, and a person enters them at the domain registrar.
How to disable. Delete the `email-best-practices` folder from the agent skills directory. Nothing else was installed or needs rolling back.
FAQ
How do I install email-best-practices in Claude Code?
Run `npx skills add resend/email-best-practices` in the project root. After the agent restarts, the skill triggers on requests about spam, bounces, SPF, DKIM, DMARC and webhooks.
Does the skill need a Resend account?
No. The skill consists of references and works with any email provider. A Resend account is needed only for the company's other skills and API.
What if emails land in spam?
Open the `deliverability.md` reference: it covers SPF, DKIM and DMARC checks, IP warming and complaint handling. Authentication problems are named there as the most common cause.
How do I avoid sending one email twice on retry?
The `sending-reliability.md` reference proposes idempotency keys and retries with exponential backoff. Build the key from the business event, such as an order number, and a retry within 24 hours returns the earlier response instead of a new email.
Does the skill cover Russian law?
No. The compliance section covers CAN-SPAM, GDPR, CASL and a few other countries, and the requirements of Russian laws on advertising and personal data must be checked separately.
Discussion
No questions or reviews yet.
Related
SkillsResend skills
Resend Skills
Official Resend skills for sending and receiving email, React Email and the CLI, plus a remote MCP covering the full API
Hundreds of per-provider skills teach an agent to receive webhooks, verify signatures and handle events, with code examples.
Upstash Redis SDK
redis-js
Reference skill for @upstash/redis: data structures, caching, rate limits, locks and full-text search
builder-skills: agent skills for Convex apps
builder-skills
17 skills that teach an agent to build Convex apps by the docs and run a project through a PRD, task.md and a changelog
Three backend skills for agents that guard access, data and schema migrations: 2 of 150 runs had critical mistakes instead of 25.
The official Payload CMS skill shipped inside the package: collections, fields, hooks, access control, queries and database adapters
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| email-best-practices (this card) | no | 146 | ||
| Resend skills | no | API key | 212 | a bundle of five Resend skills with API, CLI and MCP; this one is a standalone reference on deliverability and reliability, not tied to one service |
| Resend CLI | yes | 411 | the `resend` console utility for sending email and managing domains; this one is a guide only and runs nothing |
README in short
The documentation briefly lists what the skill covers: email planning, authentication, sending, compliance and resilient infrastructure with idempotency, webhooks and suppression lists. It shows the folder structure and the MIT license.