Token导航 LogoToken导航

Agent Skill · 开发

email(邮件)

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

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

总安装 261周安装 11GitHub Stars 167下载 92核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/whawkinsiv/claude-code-skills --skill email

这个 Skill 是做什么的

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

email 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用。安装前需确认权限范围、维护状态,避免触发联网或命令执行。

建议结合原始 README 核验具体用法和功能边界。

来源仓库内路径:skills/email

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

email 怎么安装?

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

email 支持哪些 AI 工具?

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

email 需要什么权限?

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

email 是免费的吗?

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

email 用的人多吗?

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

email 安全吗?

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

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

值得选的地方

  • 同时适配 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

邮件 · 本页

261167只读未明确通过

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

SKILL.md 原文

Email & Lifecycle Marketing

Email is the highest-ROI channel in SaaS — when done right. This skill helps you design email sequences that drive activation, retention, and revenue with specific copy you can paste into your email tool.

If ABOUT-ME.md and/or MY-ICP.md exist in the project root, read them before writing emails. The "from" voice should match ABOUT-ME.md Communication Style — emails should sound like the founder, not a marketing department. The content should speak to MY-ICP.md — their pain, their goals, their language.

Core Principles

  • Every email must answer: "Why should I care about this right now?"
  • Behavioral triggers > time-based drips. React to what users DO, not how long they've been around.
  • One email, one goal, one CTA. Multiple CTAs = no CTA.
  • Subject lines determine whether your email is read. Body copy determines whether it's acted on.
  • Unsubscribes are better than spam complaints. Make it easy to leave.

Part 1: Professional Branded Email (Do This First)

Before you send a single marketing email, you need a professional email address. Sending from yourname@gmail.com kills credibility. You want hello@yourdomain.com — and you can set this up for free in under 30 minutes.

The Free Setup (Cloudflare + Gmail)

This is the 80/20 approach. You get a branded email address without paying for Google Workspace or managing an email server.

What you need:

  • A free Gmail account (you probably already have one)
  • Your domain on Cloudflare (free plan works — if your domain is elsewhere, transfer DNS to Cloudflare)

Step 1: Set up Cloudflare Email Routing (receiving mail)

Cloudflare Email Routing forwards hello@yourdomain.com to your personal Gmail — for free.

  1. Go to Cloudflare dashboard > your domain > Email > Email Routing
  2. Click "Get started" and add a destination address (your Gmail)
  3. Verify your Gmail address when Cloudflare sends the confirmation
  4. Create a route: hello@yourdomain.com → yourpersonal@gmail.com
  5. Add a catch-all if you want (sends ANY @yourdomain.com address to your Gmail)

That's it. Emails to hello@yourdomain.com now arrive in your Gmail inbox.

Step 2: Send AS your branded address from Gmail

Receiving is only half the equation. You also want to reply FROM hello@yourdomain.com so recipients see your branded address, not your personal Gmail.

Option A — Use a free SMTP relay (most reliable):

  1. Create a free account on Resend or Brevo (both have free tiers)
  2. Verify your domain in their dashboard (they'll give you DNS records to add in Cloudflare)
  3. Get your SMTP credentials from the relay service
  4. In Gmail: Settings > Accounts > "Send mail as" > Add another email address
  5. Enter hello@yourdomain.com, uncheck "Treat as alias"
  6. Enter the SMTP server, port, username, and password from your relay service
  7. Click the verification link Gmail sends to hello@yourdomain.com (which forwards to your Gmail)

Option B — ImprovMX ($10/year):

  • Handles both forwarding AND SMTP sending in one service
  • Simpler setup than Option A if you want to skip the relay configuration
  • Free tier available (forwarding only; sending requires paid plan)

Step 3: Set your branded address as the default

In Gmail: Settings > Accounts > "Send mail as" > make hello@yourdomain.com the default. Now every email you send comes from your branded address.

Email Security: SPF, DKIM, and DMARC

These three DNS records prevent attackers from spoofing your domain (sending fake emails that look like they come from you). They also dramatically improve deliverability — without them, your emails land in spam.

Why this matters for founders:

  • Without DMARC, anyone can send emails pretending to be @yourdomain.com
  • Phishing attacks using your domain destroy trust and can get your domain blacklisted
  • Gmail, Outlook, and Yahoo now require SPF and DKIM for bulk senders — even small senders benefit

What to set up (add these as DNS records in Cloudflare):

RecordWhat It DoesPriority
SPFDeclares which servers can send email for your domainMust have
DKIMCryptographically signs your emails to prove they're authenticMust have
DMARCTells receiving servers what to do with emails that fail SPF/DKIM checksMust have

Your email forwarding service (Cloudflare) and SMTP relay (Resend/Brevo) will give you the exact DNS records to add. Follow their setup guides — they walk you through it.

DMARC record to start with (add as a TXT record for _dmarc.yourdomain.com):

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100
  • p=quarantine tells receiving servers to spam-folder emails that fail authentication (use p=reject once you're confident everything is configured correctly)
  • rua=mailto:... sends you aggregate reports about who's sending email from your domain

Verify your setup: Use MXToolbox or Google's Check MX to confirm SPF, DKIM, and DMARC are working.

When to Upgrade to Google Workspace

The free Cloudflare + Gmail setup works great for solo founders. Consider Google Workspace ($7/user/month) when:

  • You're hiring and need multiple @yourdomain.com accounts
  • You want native Google Calendar invites from your branded address
  • You need shared drives or team collaboration features
  • You want a cleaner separation between personal and business email

Don't pay for Google Workspace on day one. The free setup is professional enough to close deals, send investor updates, and handle customer support.

Other 80/20 Email Recommendations

  • Create 3-4 aliases for free: hello@, support@, billing@, founder@ — all forwarding to the same Gmail. This looks professional and helps you filter/label incoming mail.
  • Set up Gmail filters to auto-label emails by which alias received them (e.g., label "Support" for anything to support@).
  • Add a professional email signature with your name, title, product name, and website link. Keep it minimal — no logos, no quotes, no social icons.
  • Use "Canned Responses" (Gmail Templates) for repetitive replies: support answers, sales follow-ups, investor FAQs.
  • Never send marketing emails from your primary domain — use a subdomain like mail.yourdomain.com to protect your main domain's reputation. Your lifecycle email tool handles this separately.

Part 2: Lifecycle Email Marketing

Once you have professional email set up, here's how to build the automated sequences that drive activation, retention, and revenue.

Workflow

Email Sequence Setup:
- [ ] Choose which sequence you need (welcome, trial expiry, re-engagement, etc.)
- [ ] Write each email (subject, preview text, body, CTA)
- [ ] Define triggers and timing
- [ ] Set up in your email tool
- [ ] Test: send to yourself on mobile
- [ ] Track opens, clicks, and conversions

Choosing an Email Tool

StageToolWhyCost
Pre-revenueResend or LoopsModern, developer-friendly, good free tierFree tier
0-$5K MRRCustomer.io or LoopsBehavioral triggers, event-based sequences$0-150/mo
$5K+ MRRCustomer.io or IntercomAdvanced segmentation, in-app + email$150+/mo

For most bootstrapped founders: Loops (simple, modern) or Resend (if you want to code your own templates). Graduate to Customer.io when you need complex behavioral triggers.


Welcome Sequence (Most Important)

Triggered on signup. Goal: get users to their aha moment.

Tell AI:

Write a 5-email welcome sequence for our SaaS:
- Product: [what it does]
- Aha moment: [the first action where users experience value]
- Signup flow: [what happens after signup — onboarding wizard, empty dashboard, etc.]

Email 1 (send immediately): Welcome + single CTA to start [aha action]. No fluff.
  Subject line under 50 chars. Body under 100 words.

Email 2 (Day 1, if user hasn't activated): Quick win tip — how to get value in 2 minutes.
  Include a specific "here's how" with a link directly to the action.

Email 3 (Day 3, if user hasn't activated): Social proof — brief story of how
  someone like them got results. End with CTA to try it.

Email 4 (Day 5, if user hasn't activated): Address the #1 objection or confusion
  that prevents activation.

Email 5 (Day 7, if user hasn't activated): Personal check-in from founder.
  "Reply to this email — I read every one."

Stop the sequence as soon as the user completes [aha action].
For each email: subject line, preview text, body, CTA button text.

Trial Expiry Sequence

Triggered 3 days before trial ends. Goal: convert to paid.

Tell AI:

Write a 4-email trial expiry sequence:
- Product: [what it does]
- Trial length: [14 days / 30 days]
- What they lose on expiry: [specific features or data access]

Email 1 (Day -3): Remind what they'll lose + easy upgrade CTA.
  Mention specific features they've used during trial.

Email 2 (Day -1): Urgency + "here's everything you've built" —
  show them what's at stake.

Email 3 (Day 0): "Your trial ended." What happens next — is their data safe?
  Clear, calm, not pushy.

Email 4 (Day +3): "We saved your data." Final offer — extended trial
  or discount for annual plan.

For each: subject line, preview text, body, CTA. Keep subject lines under 50 chars.

Re-engagement Sequence

Triggered after 14+ days inactive. Goal: bring them back.

Tell AI:

Write a 3-email re-engagement sequence:
- Product: [what it does]
- Trigger: user hasn't logged in for 14+ days

Email 1 (Day 14): "Here's what's new" — 2-3 improvements since they left + CTA.
  Subject: not "We miss you" (too generic). Something specific about what changed.

Email 2 (Day 21): Value reminder — "Here's what [similar user] accomplished this week."
  Show what they're missing out on.

Email 3 (Day 30): Direct ask — "Is [Product] still useful to you?"
  If not, offer to help. If they're done, let them go gracefully.

For each: subject line, preview text, body, CTA.

Subject Line Formulas

  • Curiosity: "The one thing most [role]s get wrong about [topic]"
  • Specificity: "3 ways to [outcome] in [Product]"
  • Personal: "Quick question about your [project name]" (use merge tags)
  • Urgency (honest): "Your trial ends tomorrow"
  • Value: "Save 2 hours this week with [feature]"

Rules

  • Under 50 characters for mobile preview
  • No ALL CAPS. No excessive punctuation.
  • Personalization increases opens 20-30%
  • Preview text is the second subject line — don't waste it
  • A/B test subject lines on every send if volume allows

Transactional Emails

Receipts, password resets, invitations, notifications:

  • Send instantly. Users expect these within seconds.
  • Clear subject: "Your receipt from [Product]" or "Reset your password"
  • Minimal design. These are utility, not marketing.
  • Include a plain-text version.
  • Don't sneak marketing into transactional emails — legal risk and trust erosion.

Technical Setup

Before sending anything:

- [ ] SPF, DKIM, and DMARC configured (deliverability non-negotiable)
- [ ] Sending from a subdomain (e.g., mail.yourproduct.com) to protect main domain reputation
- [ ] List hygiene: remove hard bounces immediately, soft bounces after 3 fails
- [ ] Plain text fallback for every HTML email
- [ ] Mobile-responsive templates (60%+ of emails opened on mobile)
- [ ] Preference center (let users choose email types, not just unsubscribe from all)
- [ ] Track: opens, clicks, unsubscribes, spam complaints, conversions

Tell AI:

Set up email infrastructure for our app:
- Configure SPF, DKIM, and DMARC for [our domain]
- Set up a sending subdomain: mail.[domain].com
- Create mobile-responsive email templates for:
  1. Transactional (receipt, password reset, invite)
  2. Marketing (sequence emails, announcements)
- Add unsubscribe link and email preference center
- Verify deliverability with a test send

Common Mistakes

MistakeFix
Time-based drips only ("Day 3, Day 5")Use behavioral triggers: "hasn't completed X"
Multiple CTAs in one emailOne email, one goal, one button
"We miss you" as a subject lineBe specific: "3 new features since you left"
No plain-text versionAlways include one. Some clients strip HTML.
Sending from noreply@Use a real address. Let people reply.
No trackingTrack opens, clicks, and conversions per email
Marketing in transactional emailsKeep them separate. Trust > short-term engagement.

Related Skills

  • growth — Activation strategies that email sequences support
  • conversion — Optimize the full signup-to-paid funnel
  • analytics — Track email-driven conversions and attribution
  • copywriting — Write stronger subject lines and email body copy

平台分布

Codex

36.58%
按下载量换算34

Claude

31.18%
按下载量换算29

Cursor

16.81%
按下载量换算15

Gemini CLI

9.87%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills