Email Best Practices

What it does

The source maps the full lifecycle from signup and validation through sending and delivery events. It routes authentication, transactional messages, marketing, webhooks and list management into separate references. This helps teams see that a successful API request is only one part of a reliable email feature.

Best for

Applications adding password resets, confirmations or opt-in newsletters that need coherent operational behavior.

Tradeoffs and requirements

The skill does not establish legal compliance or guarantee inbox delivery. DNS setup, provider limits and recipient consent require independent checks. Rules vary by jurisdiction and message type, while tracking events can be incomplete or privacy-sensitive.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/resend/resend-skills/tree/b2ae7b1798b70134faf679f35fc05b4331462988/skills/email-best-practices --skill email-best-practices

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

85/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

42/100

42

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Classify the message, establish consent and suppression behavior, then implement idempotent sending and verified event handling. Use a controlled test audience before enabling a real campaign.

How to judge the result

Exercise retries, duplicate events, bounces and complaints. Check rendering and accessibility in representative clients, verify unsubscribe behavior where required, and inspect the provider’s actual delivery outcomes without treating open tracking as a complete measure of engagement.