email-best-practices
This skill provides architectural guidance and best practices for implementing email features, including deliverability, compliance, accessibility, and reliability.
Is email-best-practices safe to install?
Safe to install: our audit of email-best-practices's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill provides static documentation and architectural guidance. It does not execute code or perform network requests.
How we audit skills: our security review methodology.
Who is this skill for?
Developers building email functionality into applications who need guidance on authentication, compliance, and sending reliability.
What can you do with it?
- Setting up SPF, DKIM, and DMARC authentication
- Resolving email deliverability and spam issues
- Implementing transactional email workflows
- Ensuring compliance with CAN-SPAM, GDPR, and CASL
- Designing accessible email templates
- Managing email list hygiene and webhooks
How good is this skill?
Quality score: 5/10. The skill is well-structured and provides clear, actionable guidance for email architecture. It is strictly informational.
What does the skill file contain?
# Email Best Practices
Guidance for building deliverable, compliant, user-friendly emails.
## Architecture Overview
```
[User] → [Email Form] → [Validation] → [Double Opt-In]
↓
[Consent Recorded]
↓
[Suppression Check] ←──────────────[Ready to Send]
↓
[Idempotent Send + Retry] ──────→ [Email API]
↓
[Webhook Events]
↓
┌────────┬────────┬──...Frequently asked questions
What is the recommended order for setting up email in a new application?
Start with the transactional email catalog to plan required emails, then configure DNS authentication for deliverability before sending.
How does this skill help with spam issues?
It directs users to the deliverability documentation to address common authentication failures related to SPF, DKIM, and DMARC.
Does this skill provide code for email implementation?
No, it provides architectural guidance and best practices rather than executable code.
Related skills
cold-email
63.5KSales development representatives, founders, and professionals conducting B2B cold outreach
The cold-email skill generates B2B cold outreach emails and follow-up sequences. It prioritizes human-sounding, concise copy that focuses on the recipient's perspective rather than vendor-style pitches. The skill incorporates product marketing context from local files to tailor messaging and utilizes specific frameworks for subject lines, body content, and calls to action.
recipe-email-drive-link
16.7KUsers who need to automate file sharing and email communication within the Google Workspace ecosystem
This skill automates the process of locating a Google Drive file, granting reader permissions to a specific email address, and sending the file link via Gmail.
recipe-label-and-archive-emails
16.6KUsers who manage Gmail accounts via the command line and require automated inbox organization
This skill automates Gmail inbox management by searching for specific messages, applying labels, and removing the inbox label to archive them.
recipe-forward-labeled-emails
16.2KUsers who manage Gmail workflows via the command line and require automated email forwarding based on labels
This skill automates the process of identifying Gmail messages with a specific label and forwarding them to a designated email address.