Skip to content
Back to skills

Ls Email Deliverability Compliance

ASecurity

Use when planning transactional or marketing email, designing email products, or reviewing deliverability, accessibility, compliance, and lifecycle decisions.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgitapi

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add CruxExperts/LocalSetup --skill ls-email-deliverability-compliance --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ls Email Deliverability Compliance?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ls Email Deliverability Compliance
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruxexperts-ls-email-deliverability-compliance/badge)](https://www.skillsdirectory.com/skills/cruxexperts-ls-email-deliverability-compliance)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ls-email-deliverability-compliance
description: Use when planning transactional or marketing email, designing email products, or reviewing deliverability, accessibility, compliance, and lifecycle decisions.
metadata:
  version: '1.0'
extensions:
  external_skill:
    source_kind: adapted-import
    source_url: https://github.com/resend/resend-skills
    source_path: skills/email-best-practices/SKILL.md
    source_commit: 298207bbe7a43d1886dc9490ecf880b5442600f9
    source_ref: main
    source_sha256: f1b957138619784e2c22f7ae689bde6e903a8134ee52d626d8846809382ef0c8
    license: MIT
    import_date: '2026-07-03'
    vetting_status: provenance-recorded-no-bundled-tooling-executed
---

# Email Best Practices

Use this skill when working on email best practices tasks.

## Workflow

- Classify the message type first: transactional, lifecycle, marketing, operational, or support.
- Check consent, unsubscribe requirements, accessibility, content clarity, deliverability, and rate limits.
- Keep secrets, recipient data, and suppression lists out of source and logs.

## Boundaries

- Inspect the target repository before making changes.
- Prefer existing project patterns, declared package managers, and documented validation commands.
- Do not expose secrets, credentials, private user data, or production account identifiers in source, examples, or logs.
- When external APIs or current vendor behavior matter, verify against official docs before implementation.

## Provenance

- Source: `https://github.com/resend/resend-skills`
- Ref: `main` at `298207bbe7a43d1886dc9490ecf880b5442600f9`
- Source path: `skills/email-best-practices/SKILL.md`
- License classification: `MIT`
- Source SHA-256: `f1b957138619784e2c22f7ae689bde6e903a8134ee52d626d8846809382ef0c8`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.