Back to browse

affaan-m/ECC

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.

81Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "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: Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.

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

Best fit

  • user asks to triage inbox or archive low-signal mail
  • user wants a draft, reply, or new outbound email
  • user wants to know whether a mail was already sent

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

  • drafted
  • approval-pending
  • sent

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

Workflow

If creating a new outbound:

SKILL.md · Workflow
which mailbox accountwhich thread or recipientwhether the task is triage, draft, reply, or send
02

Verification

the response names the account and thread or recipient

SKILL.md · Verification
the response names the account and thread or recipientany send claim includes Sent proof or an explicit client-side confirmationthe final state is one of drafted / sent / blocked / awaiting verification
03

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

SKILL.md · Skill Stack
brand-voice before drafting anything user-facinginvestor-outreach for investor, partner, or sponsor-facing mailcustomer-billing-ops when the thread is a billing/support incident rather than generic correspondence
04

When to Use

user asks to triage inbox or archive low-signal mail

SKILL.md · When to Use
user asks to triage inbox or archive low-signal mailuser wants a draft, reply, or new outbound emailuser wants to know whether a mail was already sent
05

Guardrails

draft first unless the user clearly asked for a live send

SKILL.md · Guardrails
draft first unless the user clearly asked for a live sendnever claim a message was sent without a real Sent-folder or client-side confirmationdo not switch sender accounts casually; choose the account that matches the project and recipient

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: “Workflow”, “Verification”, “Skill Stack”, “When to Use”, “Guardrails”. 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 “Workflow” has been checked.

The source section “Verification” has been checked.

The source section “Skill Stack” has been checked.

The source section “When to Use” 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

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

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

Open source detail

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does email-ops do?

Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.

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 "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
81/100
Source repository last pushed

Quality breakdown

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

81/100
Documentation24/30
Specificity20/25
Maintenance20/20
Trust signals17/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

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

design-review by event4u-app

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

dask by k-dense-ai

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

neurokit2 by k-dense-ai

Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.

biopython by k-dense-ai

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

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

Email Ops

Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.

This is not a generic writing skill. It is an operator workflow around the actual mail surface.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • brand-voice before drafting anything user-facing
  • investor-outreach for investor, partner, or sponsor-facing mail
  • customer-billing-ops when the thread is a billing/support incident rather than generic correspondence
  • knowledge-ops when the message or thread should be captured into durable context afterward
  • research-ops when a reply depends on fresh external facts

When to Use

  • user asks to triage inbox or archive low-signal mail
  • user wants a draft, reply, or new outbound email
  • user wants to know whether a mail was already sent
  • the user wants proof of which account, thread, or Sent entry was used

Guardrails

  • draft first unless the user clearly asked for a live send
  • never claim a message was sent without a real Sent-folder or client-side confirmation
  • do not switch sender accounts casually; choose the account that matches the project and recipient
  • do not delete uncertain business mail during cleanup
  • if the task is really DM or iMessage work, hand off to messages-ops

Workflow

1. Resolve the exact surface

Before acting, settle:

  • which mailbox account
  • which thread or recipient
  • whether the task is triage, draft, reply, or send
  • whether the user wants draft-only or live send

2. Read the thread before composing

If replying:

  • read the existing thread
  • identify the last outbound touch
  • identify any commitments, deadlines, or unanswered questions

If creating a new outbound:

  • identify warmth level
  • select the correct channel and sender account
  • pull brand-voice before drafting

3. Draft, then verify

For draft-only work:

  • produce the final copy
  • state sender, recipient, subject, and purpose

For live-send work:

  • verify the exact final body first
  • send through the chosen mail surface
  • confirm the message landed in Sent or the equivalent sent-copy store

4. Report exact state

Use exact status words:

  • drafted
  • approval-pending
  • sent
  • blocked
  • awaiting verification

If the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.

Output Format

MAIL SURFACE
- account
- thread / recipient
- requested action

DRAFT
- subject
- body

STATUS
- drafted / sent / blocked
- proof of Sent when applicable

NEXT STEP
- send
- follow up
- archive / move

Pitfalls

  • do not claim send success without a sent-copy check
  • do not ignore the thread history and write a contextless reply
  • do not mix mailbox work with DM or text-message workflows
  • do not expose secrets, auth details, or unnecessary message metadata

Verification

  • the response names the account and thread or recipient
  • any send claim includes Sent proof or an explicit client-side confirmation
  • the final state is one of drafted / sent / blocked / awaiting verification
Source repo
affaan-m/ECC
Skill path
skills/email-ops/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected