Back to browse

affaan-m/ECC

email-ops

以证据为先的邮箱分类、草稿、发送验证及已发送邮件安全跟进工作流，适用于ECC。当用户希望整理邮件、通过真实邮件界面起草或发送、或证明已发送邮件内容时使用。

54Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/email-ops"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn email-ops's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 当实际任务为邮箱工作时使用：分类、起草、回复、发送，或确认邮件已进入已发送文件夹。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/email-ops"
Check the pinned source

Best fit

  • 以证据为先的邮箱分类、草稿、发送验证及已发送邮件安全跟进工作流，适用于ECC。当用户希望整理邮件、通过真实邮件界面起草或发送、或证明已发送邮件内容时使用。

Bring this context

  • A concrete task that matches the documented purpose of email-ops.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned email-ops instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read email-ops through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

技能栈

brand-voice 在起草任何面向用户的内容之前 investor-outreach 用于面向投资者、合作伙伴或赞助商的邮件 customer-billing-ops 当邮件线程属于账单/支持事件而非普通通信时 knowledge-ops 当需要将消息或线程捕获到持久上下文中时 research-ops 当回复依赖最新外部事实时

SKILL.md · 技能栈
brand-voice 在起草任何面向用户的内容之前investor-outreach 用于面向投资者、合作伙伴或赞助商的邮件customer-billing-ops 当邮件线程属于账单/支持事件而非普通通信时
02

使用时机

用户要求分类收件箱或清理低价值邮件 用户需要起草、回复或发送新邮件 用户想确认邮件是否已发送 用户需要验证使用的账户、线程或已发送记录

SKILL.md · 使用时机
用户要求分类收件箱或清理低价值邮件用户需要起草、回复或发送新邮件用户想确认邮件是否已发送
03

安全护栏

除非用户明确要求实时发送，否则先起草 未经真实已发送文件夹或客户端确认，不得声称邮件已发送 不随意切换发件账户；选择与项目和收件人匹配的账户 清理时不删除不确定的业务邮件 若任务实为私信或iMessage工作，转交至messages-ops

SKILL.md · 安全护栏
除非用户明确要求实时发送，否则先起草未经真实已发送文件夹或客户端确认，不得声称邮件已发送不随意切换发件账户；选择与项目和收件人匹配的账户
04

工作流程

哪个邮箱账户 哪个线程或收件人 任务是分类、起草、回复还是发送 用户需要仅起草还是实时发送

SKILL.md · 工作流程
哪个邮箱账户哪个线程或收件人任务是分类、起草、回复还是发送
05

1. 确认具体界面

哪个邮箱账户 哪个线程或收件人 任务是分类、起草、回复还是发送 用户需要仅起草还是实时发送

SKILL.md · 1. 确认具体界面
哪个邮箱账户哪个线程或收件人任务是分类、起草、回复还是发送

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use email-ops to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned email-ops source to [task]. Pay particular attention to these source sections: “技能栈”, “使用时机”, “安全护栏”, “工作流程”, “1. 确认具体界面”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current email-ops result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “技能栈” has been checked.

The source section “使用时机” has been checked.

The source section “安全护栏” has been checked.

The source section “工作流程” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

email-ops

Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does email-ops do?

当实际任务为邮箱工作时使用：分类、起草、回复、发送，或确认邮件已进入已发送文件夹。

How do I start using email-ops?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/email-ops". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
54/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

54/100
Documentation15/30
Specificity7/25
Maintenance20/20
Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

email-ops by affaan-m

Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

邮件操作

当实际任务为邮箱工作时使用：分类、起草、回复、发送，或确认邮件已进入已发送文件夹。

这不是通用写作技能，而是围绕实际邮件界面的操作工作流。

技能栈

在相关场景下调用这些ECC原生技能：

  • brand-voice 在起草任何面向用户的内容之前
  • investor-outreach 用于面向投资者、合作伙伴或赞助商的邮件
  • customer-billing-ops 当邮件线程属于账单/支持事件而非普通通信时
  • knowledge-ops 当需要将消息或线程捕获到持久上下文中时
  • research-ops 当回复依赖最新外部事实时

使用时机

  • 用户要求分类收件箱或清理低价值邮件
  • 用户需要起草、回复或发送新邮件
  • 用户想确认邮件是否已发送
  • 用户需要验证使用的账户、线程或已发送记录

安全护栏

  • 除非用户明确要求实时发送，否则先起草
  • 未经真实已发送文件夹或客户端确认，不得声称邮件已发送
  • 不随意切换发件账户；选择与项目和收件人匹配的账户
  • 清理时不删除不确定的业务邮件
  • 若任务实为私信或iMessage工作，转交至messages-ops

工作流程

1. 确认具体界面

操作前明确：

  • 哪个邮箱账户
  • 哪个线程或收件人
  • 任务是分类、起草、回复还是发送
  • 用户需要仅起草还是实时发送

2. 撰写前阅读线程

若回复：

  • 阅读现有线程
  • 识别最后一次对外联系
  • 识别任何承诺、截止日期或未回答问题

若创建新外发邮件：

  • 确定亲密度等级
  • 选择正确渠道和发件账户
  • 起草前调用brand-voice

3. 起草，然后验证

仅起草任务：

  • 生成最终副本
  • 说明发件人、收件人、主题和目的

实时发送任务：

  • 先验证最终正文
  • 通过选定邮件界面发送
  • 确认消息已进入已发送文件夹或等效的已发送副本存储

4. 报告确切状态

使用精确状态词：

  • 已起草
  • 待审批
  • 已发送
  • 被阻止
  • 等待验证

若发送界面被阻止，保留草稿并报告确切阻止原因，而非未经说明即改用第二传输方式。

输出格式

邮件界面
- 账户
- 邮件线程/收件人
- 请求的操作

草稿
- 主题
- 正文

状态
- 已草拟/已发送/已拦截
- 适用时附上发送证明

下一步
- 发送
- 跟进
- 归档/移动

常见陷阱

  • 未经已发送副本检查不得声称发送成功
  • 不得忽略线程历史而撰写无上下文的回复
  • 不得混淆邮箱工作与私信或短信工作流
  • 不得泄露机密、认证详情或不必要的消息元数据

验证

  • 回复中指明账户和线程或收件人
  • 任何发送声明均包含已发送证明或明确的客户端确认
  • 最终状态为：已起草/已发送/被阻止/等待验证
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/email-ops/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected