Token导航 LogoToken导航TokenDH.com
AI 工具只读github未标认证来源可访问clear审计通过

email-marketing电子邮件营销

Agent Skill

email-marketing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

333

周安装

14

GitHub Stars

公开资料未说明

下载量

116
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:email-marketing(电子邮件营销)
来源仓库:https://github.com/vapvarun/claude-backup
仓库路径:skills/email-marketing
安装命令:
npx skills add https://github.com/vapvarun/claude-backup --skill email-marketing
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vapvarun/claude-backup --skill email-marketing

简介

email-marketing 提供人性化风格的邮件文案写作指导,避免 AI 化表达与冗余词汇。

  • 适用于创建具有真实语气的营销邮件,强调简洁自然与适度表情符号使用。
  • 包含主题行优化、段落长度控制、CTA 设计等实用技巧以提升打开与点击率。
  • 输出内容应符合品牌调性,避免滥用流行语损害专业形象。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Email Marketing Skill

Writing Style Guidelines

Be Human, Not AI:

  • Write like you're emailing a colleague, not a marketing database
  • Use natural language that sounds like a real person
  • Avoid buzzwords: "revolutionary", "game-changing", "seamless", "leverage"
  • Skip filler words: "basically", "essentially", "simply", "just"

Emoji Policy:

  • Maximum ONE emoji per email (in subject OR body, not both)
  • Use only when it genuinely helps (friendly greeting, celebration)
  • Never use emoji in serious/professional contexts
  • When in doubt, skip the emoji

Instructions

When creating email campaigns:

1. Subject Lines

Formulas:

  • How to [achieve desired outcome]
  • [Number] ways to [solve problem]
  • Don't [make this mistake]
  • [Name], your [thing] is ready
  • Last chance: [offer ending]
  • Quick question about [topic]

Best Practices:

  • 30-50 characters ideal
  • Personalize when possible
  • Create urgency (carefully, don't be manipulative)
  • A/B test always
  • Avoid spam triggers
  • No ALL CAPS or excessive punctuation

Preview Text:

  • Extends the subject line
  • 40-130 characters
  • Add context or intrigue

2. Email Types & Templates

Welcome Email:

Subject: Welcome to [Brand] — Here's what's next

Hi [Name],

Welcome aboard!

You're now part of [X,000] [customers/subscribers] who [benefit].

Here's what you can expect:
• [Benefit 1]
• [Benefit 2]
• [Benefit 3]

To get started, [simple first action]:
[CTA Button]

Questions? Just reply to this email.

[Signature]

P.S. [Bonus tip or resource]

Product Launch:

Subject: Introducing [Product] — [Key Benefit]

Hi [Name],

[One-line hook about the problem]

Today, we're launching [Product] — and it's going to change how you [do thing].

**What's new:**
- [Feature 1] — [benefit]
- [Feature 2] — [benefit]
- [Feature 3] — [benefit]

[CTA Button: Get [Product] Now]

**Launch special:** [Discount/bonus] for the first [X] customers.

[Signature]

Newsletter:

Subject: [Newsletter Name] #[Number]: [Topic]

Hey [Name],

[Personal intro or timely hook — 2-3 sentences, conversational]

---

**[Main Topic]**

[2-3 paragraphs of value — write like you're explaining to a friend]

[Key takeaway or action item]

---

**Links Worth Clicking**

• [Link 1] — [Why it's useful]
• [Link 2] — [Why it's useful]
• [Link 3] — [Why it's useful]

---

**Quick Tip**

[Actionable tip in 2-3 sentences]

---

That's all for this week!

[Signature]

P.S. [Teaser for next issue or CTA]

Abandoned Cart:

Subject: You left something behind

Hi [Name],

Looks like you didn't finish checking out. No worries — your cart is still waiting:

[Product Image]
[Product Name] — $[Price]

[CTA: Complete Your Order]

**Need help?** Reply to this email or chat with us.

[Signature]

P.S. Your cart expires in [X] hours.

Re-engagement:

Subject: We miss you, [Name]

Hi [Name],

It's been a while since we've seen you, and we wanted to check in.

Here's what's new since your last visit:
• [Update 1]
• [Update 2]
• [Update 3]

[CTA: Come Back & Explore]

If you'd like to unsubscribe, no hard feelings — just click below.

[Signature]

3. Drip Sequence Structure

Onboarding Sequence (7 emails):

  1. Day 0: Welcome + quick win
  2. Day 1: Getting started guide
  3. Day 3: Key feature spotlight
  4. Day 5: Success story/case study
  5. Day 7: Tips & tricks
  6. Day 10: Check-in + support
  7. Day 14: Upgrade/upsell (only if appropriate)

Nurture Sequence:

  1. Value email (no pitch)
  2. Value email (soft mention)
  3. Value email (case study)
  4. Pitch email (offer)
  5. FAQ/objection handling
  6. Last chance (no pressure tactics)

4. Email Design Best Practices

Layout:

  • Single column (mobile-first)
  • 600px max width
  • Clear visual hierarchy
  • Plenty of white space

Typography:

  • 16px+ body text
  • 22px+ headlines
  • System fonts for reliability
  • High contrast colors

Images:

  • Alt text always
  • Compressed file sizes
  • Don't rely on images for key info
  • Use real photos over stock when possible

CTAs:

  • One primary CTA per email
  • Button style (not just links)
  • Action-oriented text
  • Contrasting color
  • Above the fold

5. Deliverability Tips

Do:

  • Authenticate (SPF, DKIM, DMARC)
  • Clean list regularly
  • Use double opt-in
  • Include unsubscribe link
  • Monitor bounce rates

Avoid:

  • Purchased lists
  • Spam trigger words (FREE!!!, Act Now!!!)
  • Too many images
  • Misleading subjects
  • Sending too frequently

6. Metrics to Track

MetricGood Benchmark
Open rate20-30%
Click rate2-5%
Unsubscribe<0.5%
Bounce rate<2%
Spam complaints<0.1%

7. A/B Testing Ideas

  • Subject lines (always)
  • Send times
  • CTA button copy
  • Email length
  • Personalization
  • From name

Quality Checklist

Before sending, verify:

Content

  • Subject line is compelling (30-50 chars)
  • Preview text adds context
  • One clear CTA
  • Value before pitch
  • Unsubscribe link present

Tone

  • Human, conversational tone
  • No buzzwords or filler words
  • Maximum one emoji (if any)
  • Not salesy or pushy
  • Reads like a real person wrote it

Technical

  • Mobile responsive
  • Alt text on images
  • Links work
  • Personalization tokens correct
  • Tested in multiple email clients

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

28.8%
按下载量换算33

Gemini CLI

21.42%
按下载量换算25

Antigravity

16.53%
按下载量换算19

Codex

12.86%
按下载量换算15

OpenCode

7.49%
按下载量换算9

windsurf

3.1%
按下载量换算4

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills