Run any Skill in Manus with one click

Get Started

ls-email-best-practices

Stars3

Forks2

UpdatedJuly 3, 2026 at 07:19

Guide email product, transactional, marketing, deliverability, accessibility, compliance, and lifecycle decisions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

CruxExperts

CruxExperts/localsetup

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	ls-email-best-practices
description	Guide email product, transactional, marketing, 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

More from this repository

same repository

ls-nodejs-nextjs

CruxExperts/localsetup

Practical Node.js and Next.js project runbook. Use for Node, Next.js, React, package-manager, build, migration, debugging, testing, security, deployment, and version-verification tasks.

2026-07-053

ls-scrapling

CruxExperts/localsetup

Host-first Scrapling integration skill: install or upgrade Scrapling via pipx, run single-URL extractions (simple and structured), and manage adapter and version refresh flows, with Docker as an optional escape hatch.

2026-07-053

ls-shadcn-ui

CruxExperts/localsetup

Project-aware shadcn/ui guide. Use for shadcn setup, components, CLI/MCP, registry, theming, forms, Radix/Base UI, aliases, updates, and troubleshooting in React UI projects.

2026-07-053

ls-workflow-codex-github-issue-goal-loop

CruxExperts/localsetup

Use when running a bounded Codex goal loop over GitHub issues, PRs, and maintenance alerts with explicit approval gates.

2026-07-053

ls-omniroute-admin-automation

CruxExperts/localsetup

Comprehensive OmniRoute administration and automation via Python tooling. Use when you need full API-driven control of providers, nodes, aliases, combos, fallbacks, keys, policies, budgets, backup/restore, sync, resilience, and configuration reconciliation with safety gates.

2026-07-043

ls-omniroute-codex

CruxExperts/localsetup

OmniRoute client onboarding and Codex CLI configuration workflow. Use for setup, launch, Codex profile files, wire_api responses configuration, and safe agent-client registration with OmniRoute.

2026-07-043

name	ls-email-best-practices
description	Guide email product, transactional, marketing, 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