一键在 Manus 中运行任何 Skill

email-skills

星标16

分支0

更新时间2026年4月2日 10:27

Master reference for sending emails that reach the inbox. Always load this skill first for any email-related task, it will orient you quickly and route you to the right sub-skill. Use it for: email sending setup, inbox placement, spam avoidance, domain reputation, email infrastructure, writing or reviewing email copy, diagnosing why emails go to spam, building email workflows, or advising on list management. If the task touches email in any way, start here before doing anything else.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

autosendhq

autosendhq/email-skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Email Skills by AutoSend

A modular skill set for AI agents writing, reviewing, or advising on email. The goal is inbox placement, not just sending. Every decision here connects back to that.

This is the entry point. Read this first, then load the relevant sub-skill for deeper guidance on a specific topic.

The Deliverability Stack

Inbox placement depends on four pillars working together. A failure in any one of them can undo the other three.

1. Authentication   → Proves you are who you say you are
2. Sender Reputation → Proves you are a responsible sender
3. Content Quality  → Proves your email is wanted
4. List Quality     → Proves your recipients consented and are real

Sub-Skills (Load as Needed)

Topic	Sub-Skill	When to Use
SPF, DKIM, DMARC, BIMI	`authentication/SKILL.md`	Setting up or debugging email authentication
Subject lines, HTML, copy	`content/SKILL.md`	Writing or reviewing email content
CAN-SPAM, GDPR, CASL	`compliance/SKILL.md`	Any question touching legal requirements or consent
Validation, suppression, sunset	`list-hygiene/SKILL.md`	Managing contacts, bounces, or unsubscribes
OTP, receipts, password reset	`transactional/SKILL.md`	Building or writing transactional email flows
Drip, campaigns, segmentation	`marketing-campaigns/SKILL.md`	Writing or planning marketing email
Drip sequences, lifecycle flows	`email-automation/SKILL.md`	Choosing or building automated email sequences
Postmaster Tools, blacklists	`monitoring/SKILL.md`	Diagnosing issues or setting up monitoring

Core Principles (Always Apply)

These apply regardless of which sub-skill you load.

Separate transactional from marketing. Different sending streams, different subdomains. A spam complaint on your marketing stream should never affect transactional delivery.

Send from a subdomain, not your root domain. Use mail.yourdomain.com or em.yourdomain.com. This isolates email reputation from your web domain.

Authenticate before you send anything. SPF, DKIM, and DMARC must be in place before volume matters. See authentication/SKILL.md.

List quality beats list size. Sending to disengaged or invalid addresses actively damages your domain reputation. See list-hygiene/SKILL.md.

Open rate is not a reliable metric. Apple Mail Privacy Protection inflates open rates by pre-fetching tracking pixels. Use click rate, reply rate, and conversion rate instead.

Consistency matters more than volume. Sudden spikes in sending volume look like compromised accounts to inbox providers. Ramp gradually and send at a predictable cadence.

Google's spam rate threshold is 0.08%. Above this, Gmail delivery degrades. Above 0.1%, mail starts getting blocked. Monitor this daily via Google Postmaster Tools.

Transactional vs. Marketing: The Key Distinction

Dimension	Transactional	Marketing
Trigger	User action	Sender-initiated
Unsubscribe required	No (best practice: include support path)	Yes, legally required
Consent required	Implied by account creation	Express opt-in
Promotional content	Incidental only	Yes
Sending stream	Separate	Separate

Common transactional types: password reset, 2FA/OTP, order confirmation, shipping update, billing receipt, account alert, email verification.

Pre-Send Checklist (Quick Reference)

Authentication

SPF record published and valid
DKIM signing active and selector resolving
DMARC policy published (p=none minimum to start)

Content

Subject line: under 60 chars, no spam trigger words, not misleading
Preview text set explicitly (not left to the client to guess)
Plain-text version included alongside HTML
No JavaScript, no URL shorteners
All images have alt text
Physical mailing address in footer (required for commercial email)
Unsubscribe link present and functional (marketing only)

List

Addresses validated before import
Suppression list applied before send
Consent documented for all marketing contacts

同仓库更多 Skills

同仓库

content

autosendhq/email-skills

Best practices for writing email content that avoids spam filters and gets read. Load this skill whenever writing or reviewing any email from scratch - content decisions affect deliverability just as much as authentication does. Use it for: composing subject lines, preview text, HTML email structure, body copy, CTAs, plain-text alternatives, image guidelines, link rules, or auditing an email for spam signals. Also load it when a user asks why a specific email feels spammy, what words to avoid, how to structure an HTML email, or how to write a CTA. Covers both transactional and marketing content.

2026-04-0216

marketing-campaigns

autosendhq/email-skills

Best practices for planning, writing, and sending marketing email campaigns. Load this skill for any marketing email task, a poorly planned campaign can damage domain reputation for months, while a well-executed one builds it. Use it for: drip sequences, broadcast campaigns, segmentation strategy, personalization, CTA design, send timing, frequency management, re-engagement campaigns, welcome sequences, onboarding flows, A/B testing, or unsubscribe UX. Also load it when someone asks how to improve campaign performance, reduce unsubscribe rates, or structure a sequence that converts without hurting deliverability.

2026-04-0216

email-automation

autosendhq/email-skills

Strategy and design guide for email automation sequences (drip campaigns, lifecycle emails, nurture flows). Load this skill when a user describes a business problem and needs help choosing the right automation type, or when they want to build a multi-step email sequence. Use it for: onboarding sequences, welcome flows, feature discovery drips, feedback and NPS collection, milestone and success emails, lead nurture drips, trial conversion sequences, post-purchase flows, churn prevention sequences, re-engagement drips, upsell or expansion sequences, event-triggered automations, or any time someone asks "what emails should I be sending?" Based on the user's described problem, this skill maps them to the right automation type and gives them a concrete sequence structure to implement.

2026-04-0216

authentication

autosendhq/email-skills

Deep reference for email authentication: SPF, DKIM, DMARC, and BIMI. Always use this skill before advising on anything involving DNS records for email, even if the question seems simple: authentication failures are the most common hidden cause of deliverability problems. Use it when: setting up a new sending domain, debugging why emails go to spam, reviewing DNS records, diagnosing DMARC alignment issues, interpreting authentication headers, reading DMARC aggregate reports, or advising on key rotation. If someone asks "why is my email going to spam" and authentication hasn't been verified yet, load this skill first.

2026-04-0216

compliance

autosendhq/email-skills

Legal and regulatory compliance for email sending: CAN-SPAM, GDPR, CASL, and consent flows. Always load this skill when the task involves sending to recipients in the US, EU, or Canada, the legal requirements differ significantly between jurisdictions and the penalties for violations are severe. Use it for: consent collection, unsubscribe flows, GDPR data subject requests, what must appear in email footers, data retention obligations, double opt-in design, or evaluating whether a specific email practice is legally permissible. When in doubt about whether something requires consent or an opt-out, load this skill before answering.

2026-04-0216

list-hygiene

autosendhq/email-skills

Best practices for maintaining healthy email contact lists. Load this skill whenever working with contact data, diagnosing bounce or complaint rate problems, or importing lists, poor list quality is a leading cause of deliverability failure and it is easy to damage a domain's reputation with a single bad send to a stale list. Use it for: email address validation, bounce classification and handling, building suppression lists, processing unsubscribes, sunsetting inactive contacts, re-engagement campaign design, list import procedures, spam trap avoidance, or diagnosing why bounce or complaint rates are high. Also load it when asked whether to delete or suppress a contact.

2026-04-0216