01
It starts by itself
weekly email review. Runs in Claude Code routine.
- ↻ weekly email review
0 8 * * 1
resend · 13K installsEmail best practices skill
Runs by itself, weekly email review.
Emails stay deliverable and accessible.
Install the Email best practices skill and make it a habit: follow https://gethabit.dev/skills/resend/email-best-practices.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
13K installs203 starsMIT licenceSource on GitHub ↗
Email best practices
by resend · 13K installs
The skill
The email best practices skill by Resend guides developers through deliverable, compliant and accessible email: SPF, DKIM and DMARC, transactional versus marketing mail, consent, retries, webhooks, bounce handling and screen reader friendly templates.
Only when you ask.
The habit
Emails stay deliverable and accessible.
↻ Runs by itselfweekly email review
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
One review per run, at most 20 findings written.
- 01
Read the board
Start from the open findings of the last review.
- 02
Check deliverability
Compare the sending domain's SPF, DKIM and DMARC setup with the deliverability guide.
- 03
Check accessibility
Review templates for lang and dir, presentational tables, headings, alt text, title and contrast.
- 04
Check compliance
Confirm marketing mail follows the capture, consent and CAN-SPAM, GDPR and CASL guidance.
- 05
Check reliability
Look for idempotent sends with retry and for webhook events that update the suppression list.
- 06
Update the board
Write each failed item as a task and close the ones that now pass.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only inloops/email-best-practices-loop/**
- Talks tono outside service
- Sendsnothing
- Your OKNothing goes out, so it needs no OK.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the Email best practices skill helps.
Use it when
- ✓ Your emails land in spam
- ✓ You build signup or transactional emails
- ✓ You need CAN-SPAM, GDPR or CASL compliance
Skip it when
- – Your app sends no email
- – You need a full email sending SDK guide
Email best practices skill, answered.
Does it change my DNS or send mail?
No. It reviews the setup and code and writes findings to the board.
Where does it look first for spam problems?
At deliverability, since the skill names authentication as the most common cause.
Is it only for Resend users?
The guides are general email practice, so the review fits any email API.
How do I install the Email best practices skill?
Copy the prompt at the top into your agent. It installs the skill from resend/resend-skills and sets up the habit. Or run npx skills add resend/resend-skills --skill email-best-practices.
Is the Email best practices skill free?
Yes. It is published under MIT. Habit is free too.
Email best practices. Now as a habit.
Install the Email best practices skill and make it a habit: follow https://gethabit.dev/skills/resend/email-best-practices.md
All resend skills →More code skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by resend, published under MIT. Habit links to the original and never changes it. Is this your skill?