$ loading_
Organize inboxes, draft emails, verify sending, and follow up safely.
The material indicates this is essentially an open-source, highly adopted prompt-only email operations workflow, with no declared keys, remote endpoints, or executable installation steps. Overall risk is low, but because it targets real mailbox actions, users should still verify account selection and minimize unnecessary exposure of email content.
The material and objective checks indicate no keys or environment variables are required, and it does not ask for API tokens, email passwords, or other credentials. The README also explicitly says not to expose secrets or auth details, with no clear credential-abuse red flags.
No remote endpoints are declared, and the system marks it as prompt-only. While the material discusses sending through a real mail surface and verifying Sent items, there is no factual indication of data being exfiltrated to third-party services or unknown hosts.
Based on the provided material, this is a workflow/prompt-style skill with no installation commands, script execution, local process spawning, or system capability calls described. No execution privileges beyond documentation-style orchestration are requested.
This skill is intended for mailbox triage, reading threads, drafting, replying, sending, and Sent verification, so by design it may involve business communication data such as message bodies, recipients, subjects, and thread history. This is consistent with its stated purpose and not evidence of overreach, but users should limit it to the necessary account and threads.
The source is an open-source GitHub repository with very high community adoption (~210k stars), which are strong risk-reducing signals. The material shows no closed-source exfiltration, unknown provenance, or obvious injection-style content. Still, the missing license and unknown maintenance status should be verified before formal adoption.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "email-ops" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/email-ops/SKILL.md 2. Save it as ~/.claude/skills/email-ops/SKILL.md 3. Reload skills and tell me it's ready
Please triage today's inbox into urgent, needs reply, and archive, and suggest an action for each email.
A categorized email list with priority levels and recommended next actions for each message.
Draft a professional and sincere email to a client about a project delay, and verify the recipients, subject, and attachments before sending.
A send-ready draft plus pre-send verification results and any risk warnings.
Check whether the pricing email appears in Sent; if it was sent, draft a follow-up email for three days later if there is no reply.
Proof of sent status and a safe follow-up email draft for later use.
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.
Pull these ECC-native skills into the workflow when relevant:
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 correspondenceknowledge-ops when the message or thread should be captured into durable context afterwardresearch-ops when a reply depends on fresh external factsmessages-opsBefore acting, settle:
If replying:
If creating a new outbound:
brand-voice before draftingFor draft-only work:
For live-send work:
Use exact status words:
If the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.
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
Handle returns, refunds, fraud checks, and warranty claim decisions efficiently.
Use Bun for runtime, bundling, testing, packages, and Node migration decisions.
Use the correct Ethereum Keccak-256 hashing in Node.js and TypeScript.
Apply Nuxt 4 patterns for SSR safety, performance, and data fetching.
Generate images, videos, and audio with one unified AI media workflow.
Design Quarkus 3 backend patterns for messaging, APIs, data, and async workflows.
Search work emails, read messages, and draft replies without sending.
Triage inbox messages, route intents, track replies, and generate follow-up summaries.
Read, send, and organize emails with natural language across IMAP and SMTP.
Manage email reading, search, drafting, and sending directly through an MCP tool.
Verify email deliverability and detect disposable, role-based, and catch-all addresses.
Run repo tasks, debug CI, and deliver fixes with verified evidence.