Token导航 LogoToken导航

Agent Skill · 开发

email-marketing(电子邮件营销)

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

email-marketing 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 14,913。

总安装 649周安装 26GitHub Stars 115下载 210核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/shawnpang/startup-founder-skills --skill email-marketing

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

email-marketing 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。它适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。使用时需结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。当前顶部介绍为空,需结合原始 SKILL.md 内容进一步核验功能细节和使用限制。

来源仓库内路径:skills/email-marketing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/shawnpang/startup-founder-skills --skill email…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

email-marketing 怎么安装?

在终端执行 npx skills add https://github.com/shawnpang/startup-founder-skills --skill email-marketing。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

email-marketing 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

email-marketing 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

email-marketing 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

email-marketing 用的人多吗?

公开数据是累计安装 649 次,近一周安装 26 次,下载 210 次,GitHub 115 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

email-marketing 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
email-marketing

电子邮件营销 · 本页

649115需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Email Marketing

When to Use

  • Building a welcome sequence for new signups or lead magnet downloads.
  • Designing a lead nurture sequence to move prospects toward conversion.
  • Creating a re-engagement campaign for inactive users or subscribers.
  • Writing an onboarding email series that drives product activation.
  • Planning a newsletter cadence and format.
  • Optimizing existing sequences for open rate, click rate, or conversion.

Context Required

  • From startup-context: product description, ICP, value proposition, tone of voice, current user journey stages, key activation metrics.
  • From the user: sequence type needed (welcome, nurture, re-engagement, onboarding, post-purchase, educational), audience context (who they are, what triggered entry, relationship stage), current email list size and segments, existing sequences (if optimizing), email platform in use, primary conversion action, any existing performance data.

Workflow

  1. Define the sequence goal -- Every sequence gets one job. Map it to a specific outcome:

- Welcome: activate, build trust, convert - Nurture: educate, build desire, drive trial/demo/purchase - Re-engagement: reactivate or clean the list - Onboarding: drive users to key activation milestones (coordinate with in-app messaging -- email supports, does not duplicate) - Newsletter: maintain top-of-mind, drive traffic, build relationship

  1. Map the sequence arc -- Plan the emotional and logical progression across emails:

- Welcome (5-7 emails, 12-14 days): Deliver value and quick win, origin story/connection, educational content on their pain, social proof/case study, address #1 objection, feature highlight, conversion ask with reason to act now. - Lead nurture (6-8 emails, 2-3 weeks): Lead magnet delivery, topic expansion, problem deepening, solution framework, case study, differentiation, objection handling, direct offer. - Re-engagement (3-4 emails, 2 weeks, triggered at 30-60 days inactivity): Check-in, value reminder, incentive, last chance and list cleanup. - Onboarding (5-7 emails, 14 days): Activate, guide to aha moment, feature education, milestone celebration, upgrade prompt.

  1. Write each email using One Email, One Job -- Each email has one primary message and one call to action. No competing CTAs, no kitchen-sink emails.
  2. Apply the email copy structure:

- Hook (first 1-2 lines): Open with a question, surprising fact, or relatable scenario. This determines whether they keep reading. - Context (2-3 lines): Bridge from hook to value. Why does this matter to them right now? - Value (body): Deliver the insight, story, resource, or proof. - CTA (final 1-2 lines): Clear, specific, single action. Button for transactional CTAs, text link for content CTAs. - Formatting: Short paragraphs (1-3 sentences), generous whitespace, bullet points where helpful, mobile-first. Conversational tone, active voice.

  1. Optimize subject lines -- Write 3 variants per email:

- Keep under 40-60 characters for mobile - Patterns: questions, how-tos, numbers, direct statements, story teases - Clear beats clever, specific beats vague - Avoid spam triggers (ALL CAPS, excessive punctuation, "free") - Preview text (90-140 characters) is the second subject line -- write it deliberately, do not repeat the subject

  1. Set timing and triggers -- Welcome email sends immediately. Early sequence emails 1-2 days apart. Nurture phase 2-4 days apart. Long-term weekly or bi-weekly. Define behavior-triggered branching where relevant.
  2. Plan measurement -- Define success metrics per email: open rate, click rate, reply rate, conversion rate. B2B SaaS benchmarks: 25-35% open, 3-5% click, 1-3% conversion.

Output Format

  • Sequence overview: name, entry trigger, goal, number of emails, timing, exit conditions.
  • Per-email detail: number/purpose, send timing, 3 subject line options, preview text, full body copy (50-500 words depending on type), CTA, segment/conditions.
  • Email length guidance: transactional 50-125 words, educational 150-300 words, story-driven 300-500 words. Anything over 500 words should be a blog post you link to.
  • Segmentation logic and branching paths if applicable.

Frameworks & Best Practices

  • One Email, One Job. The most common email mistake is trying to do too much. One message, one CTA. If you have two things to say, send two emails.
  • Value Before Ask. Lead with usefulness, build trust through content before making the conversion ask. The sequence arc should front-load value.
  • Relevance Over Volume. Fewer, better emails win. Segmentation by behavior (what they did) matters more than personalization by demographics (who they are).
  • Plain text outperforms HTML for B2B. For B2B audiences, plain text emails (or minimal HTML that looks like plain text) consistently outperform heavily designed emails. They feel personal, not promotional.
  • Send timing. Tuesday through Thursday, 9-11 AM in the recipient's timezone performs best on average, but the best send time is when your audience actually reads email. Test and adjust.
  • List hygiene. Remove unengaged subscribers (no opens in 90 days for weekly senders, 180 days for monthly) after a re-engagement attempt. A smaller, engaged list outperforms a large, dead one.
  • Reply-to matters. Use a real person's email as the reply-to address. Replies improve deliverability and create sales conversations.
  • Unsubscribe is not the enemy. Make unsubscribing easy and obvious. People who cannot leave will mark you as spam, which damages deliverability for everyone on your list.
  • Mobile-first writing. Over 60% of emails are opened on mobile. Short paragraphs, generous whitespace, thumb-sized buttons.

Related Skills

  • cold-outreach -- when emails are going to prospects who have not opted in (different rules, different approach)
  • content-strategy -- when email content needs to be part of a broader content distribution plan
  • onboarding-flow -- when the email sequence is part of product onboarding and needs to align with in-app messaging

Examples

Example 1: Welcome sequence for lead magnet

"We launched a free template as a lead magnet. Need a welcome sequence to convert downloads to free trial signups."

Good output: A 6-email sequence over 12 days. Email 1 delivers the template with a quick-start tip. Email 2 shares the founder story. Email 3 teaches a technique related to the template topic. Email 4 shares a customer case study. Email 5 addresses the "I don't have time for another tool" objection. Email 6 offers a free trial with a specific reason to start this week. Each email includes 3 subject line variants, full copy (100-400 words), and a single CTA.

Example 2: Re-engagement campaign

"We have 3,000 subscribers who haven't opened an email in 60 days. What do we do?"

Good output: A 3-email re-engagement sequence. Email 1 (day 0): "Still interested?" with a high-value resource, no hard sell. Email 2 (day 3): Direct question asking what content they want, reply-based engagement. Email 3 (day 7): "Last email unless you want to stay" with a clear re-opt-in link. Anyone who does not engage after email 3 goes to a suppression list. Includes list cleaning guidance and re-engagement benchmarks.

平台分布

Codex

38.71%
按下载量换算81

Claude

27.59%
按下载量换算58

Cursor

17.63%
按下载量换算37

Gemini CLI

8.56%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills