Update to Resend

{
  "name": "email-best-practices",
  "description": "Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing.",
  "included_files": [
    {
      "relative_path": "references/accessibility.md",
      "size_in_bytes": 9546
    },
    {
      "relative_path": "references/compliance.md",
      "size_in_bytes": 4236
    },
    {
      "relative_path": "references/deliverability.md",
      "size_in_bytes": 3420
    },
    {
      "relative_path": "references/email-capture.md",
      "size_in_bytes": 3468
    },
    {
      "relative_path": "references/email-types.md",
      "size_in_bytes": 5815
    },
    {
      "relative_path": "references/list-management.md",
      "size_in_bytes": 4608
    },
    {
      "relative_path": "references/marketing-emails.md",
      "size_in_bytes": 3313
    },
    {
      "relative_path": "references/sending-reliability.md",
      "size_in_bytes": 4764
    },
    {
      "relative_path": "references/transactional-email-catalog.md",
      "size_in_bytes": 10338
    },
    {
      "relative_path": "references/transactional-emails.md",
      "size_in_bytes": 2489
    },
    {
      "relative_path": "references/webhooks-events.md",
      "size_in_bytes": 4351
    }
  ],
  "skill_md_contents": "---\nname: email-best-practices\ndescription: Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing.\nlicense: MIT\nmetadata:\n  author: Resend\n  version: \"1.0.2\"\n  homepage: https://resend.com/agent-skills\n  source: https://github.com/resend/email-best-practices\n  openclaw:\n    links:\n      repository: https://github.com/resend/email-best-practices\n      documentation: https://resend.com/docs/email-best-practices-skill\n---\n\n# Email Best Practices\n\nGuidance for building deliverable, compliant, user-friendly emails.\n\n## Architecture Overview\n\n```\n[User] → [Email Form] → [Validation] → [Double Opt-In]\n                                              ↓\n                                    [Consent Recorded]\n                                              ↓\n[Suppression Check] ←──────────────[Ready to Send]\n        ↓\n[Idempotent Send + Retry] ──────→ [Email API]\n                                       ↓\n                              [Webhook Events]\n                                       ↓\n              ┌────────┬────────┬─────────────┐\n              ↓        ↓        ↓             ↓\n         Delivered  Bounced  Complained  Opened/Clicked\n                       ↓        ↓\n              [Suppression List Updated]\n                       ↓\n              [List Hygiene Jobs]\n```\n\n## Quick Reference\n\n| Need to... | See |\n|------------|-----|\n| Set up SPF/DKIM/DMARC, fix spam issues | [Deliverability](./references/deliverability.md) |\n| Build password reset, OTP, confirmations | [Transactional Emails](./references/transactional-emails.md) |\n| Plan which emails your app needs | [Transactional Email Catalog](./references/transactional-email-catalog.md) |\n| Build newsletter signup, validate emails | [Email Capture](./references/email-capture.md) |\n| Send newsletters, promotions | [Marketing Emails](./references/marketing-emails.md) |\n| Ensure CAN-SPAM/GDPR/CASL compliance | [Compliance](./references/compliance.md) |\n| Decide transactional vs marketing | [Email Types](./references/email-types.md) |\n| Handle retries, idempotency, errors | [Sending Reliability](./references/sending-reliability.md) |\n| Process delivery events, set up webhooks | [Webhooks & Events](./references/webhooks-events.md) |\n| Manage bounces, complaints, suppression | [List Management](./references/list-management.md) |\n| Make emails accessible (screen readers, alt text, contrast) | [Accessibility](./references/accessibility.md) |\n\n## Start Here\n\n**New app?**\nStart with the [Catalog](./references/transactional-email-catalog.md) to plan which emails your app needs (password reset, verification, etc.), then set up [Deliverability](./references/deliverability.md) (DNS authentication) before sending your first email.\n\n**Spam issues?**\nCheck [Deliverability](./references/deliverability.md) first—authentication problems are the most common cause. Gmail/Yahoo reject unauthenticated emails.\n\n**Marketing emails?**\nFollow this path: [Email Capture](./references/email-capture.md) (collect consent) → [Compliance](./references/compliance.md) (legal requirements) → [Marketing Emails](./references/marketing-emails.md) (best practices).\n\n**Production-ready sending?**\nAdd reliability: [Sending Reliability](./references/sending-reliability.md) (retry + idempotency) → [Webhooks & Events](./references/webhooks-events.md) (track delivery) → [List Management](./references/list-management.md) (handle bounces).\n\n**Accessibility?**\nMost emails fail basic accessibility checks. See [Accessibility](./references/accessibility.md) for `lang`/`dir`, presentational tables, headings, alt text, `<title>`, and contrast.\n"
}