Fähigkeiten email-systems
📦

email-systems

Sicher

Build High-Deliverability Email Systems

Most email campaigns fail due to poor deliverability. This skill helps you implement proper SPF/DKIM/DMARC authentication, configure transactional email queues with retry logic, and avoid spam folder placement.

UnterstĂĽtzt: Claude Codex Code(CC)
🥉 73 Bronze
1

Die Skill-ZIP herunterladen

2

In Claude hochladen

Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen

3

Einschalten und loslegen

Teste es

Verwendung von "email-systems". What DNS records do I need for email authentication?

Erwartetes Ergebnis:

  • SPF Record (TXT): v=spf1 include:_spf.sendgrid.net ~all
  • DKIM Record (CNAME): selector1._domainkey.yourdomain.com -> selector1._domainkey.sendgrid.net
  • DMARC Record (TXT): _dmarc.yourdomain.com -> v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com

Verwendung von "email-systems". Why are my emails going to spam?

Erwartetes Ergebnis:

  • Check: 1) SPF/DKIM/DMARC authentication
  • 2) Sending reputation (IP warm-up status)
  • 3) Email content (image-to-text ratio, subject line quality)
  • 4) List hygiene (confirmed opt-in, bounce handling)
  • 5) Engagement metrics (recipients marking as spam)

Sicherheitsaudit

Sicher
v1 • 2/24/2026

All three static findings were evaluated and determined to be false positives. The scanner misinterpreted email-related terminology ('opt in', description text) as security issues. This is a benign documentation skill with no executable code, network calls, or security-relevant operations.

1
Gescannte Dateien
59
Analysierte Zeilen
2
befunde
1
Gesamtzahl Audits

Probleme mit hohem Risiko (1)

SKILL.md:3SKILL.md:58
Weak Cryptographic Algorithm (FALSE POSITIVE)
Scanner flagged 'weak cryptographic algorithm' at SKILL.md:3 and :58. This is a false positive - the lines contain plain text descriptions about email marketing ROI with no cryptographic algorithms present.
Probleme mit niedrigem Risiko (1)
SKILL.md:54
System Reconnaissance (FALSE POSITIVE)
Scanner flagged 'system reconnaissance' at SKILL.md:54. This is a false positive - the line discusses email opt-in practices for compliance, not system reconnaissance.
Auditiert von: claude

Qualitätsbewertung

38
Architektur
100
Wartbarkeit
87
Inhalt
50
Community
93
Sicherheit
91
Spezifikationskonformität

Was du bauen kannst

Set Up Transactional Email System

Build a reliable transactional email queue with retry logic, monitoring, and bounce handling for a SaaS application

Fix Email Deliverability Issues

Diagnose and resolve email deliverability problems including SPF/DKIM/DMARC failures and spam folder placement

Build Compliant Marketing Emails

Create email templates that comply with CAN-SPAM and GDPR requirements including proper unsubscribe flows

Probiere diese Prompts

Basic Email Setup 
Help me set up transactional email for my SaaS application. I need to configure SPF, DKIM, and DMARC records. What DNS records do I need?
Email Queue Design 
Design a transactional email queue system with retry logic, dead letter handling, and monitoring. What patterns should I use?
Deliverability Troubleshooting 
My emails are landing in spam folders. How do I debug SPF, DKIM, and DMARC authentication issues? What tools should I use?
Email Template Best Practices 
Create an HTML email template that works across major email clients (Outlook, Gmail, Apple Mail). Include proper structure and fallbacks.

Bewährte Verfahren

  • Always use authenticated sending (SPF, DKIM, DMARC) to prevent spoofing
  • Implement feedback loops to process bounces, complaints, and unsubscribes immediately
  • Warm up new IP addresses gradually over 4-8 weeks before sending high volumes

Vermeiden

  • Sending HTML-only emails without plain text alternatives (accessibility and spam risk)
  • Using shared IP pools for transactional email (reputation contamination)
  • Embedding tracking pixels in initial emails before establishing trust

Häufig gestellte Fragen

What is the difference between transactional and marketing email?
Transactional emails are triggered by user actions (password reset, order confirmation) and have higher deliverability. Marketing emails are bulk campaigns and face stricter spam regulations.
How do I check if my emails are authenticated?
Use tools like mail-tester.com, MXToolbox, or Google Postmaster Tools. Send a test email and check the authentication headers in the received message.
What is IP warm-up and why is it important?
IP warm-up is gradually increasing email volume from a new IP address. It builds sender reputation with mailbox providers. Starting with high volume immediately triggers spam filters.
How do I handle email bounces?
Process bounce notifications within 24 hours. Hard bounces (invalid addresses) require immediate removal. Soft bounces should be retried with backoff, then removed after multiple failures.
What is the CAN-SPAM requirement?
CAN-SPAM requires: accurate subject lines, physical address, clear unsubscribe mechanism, and honoring opt-outs within 10 business days.
How does email template versioning help?
Versioning allows rollback when template changes cause issues, enables A/B testing of different designs, and maintains audit trail for compliance.

Entwicklerdetails

Autor

sickn33

Lizenz

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/email-systems

Ref

main

Dateistruktur

đź“„ SKILL.md