email-ops
The email-ops skill provides a structured workflow for mailbox triage, drafting, sending, and verification within the ECC environment. It mandates verification of sent status through mail-folder confirmation and requires adherence to specific sender account and thread context.
Is email-ops safe to install?
Safe to install: our audit of email-ops's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill defines a procedural workflow for email management and does not contain executable shell commands or network request endpoints.
How we audit skills: our security review methodology.
Who is this skill for?
Users of the ECC platform who need to manage email communication, including triage, drafting, and sending, while maintaining verifiable records of sent messages.
What can you do with it?
- Triage inbox and archive low-signal mail
- Draft, reply, or send new outbound emails
- Verify if a specific email was sent
- Provide proof of account, thread, or Sent entry usage
How good is this skill?
Quality score: 5/10. The skill documentation is clear, follows a logical workflow, and provides specific guardrails for email operations. It lacks technical implementation details like API endpoints, which is appropriate for a procedural workflow skill.
What does the skill file contain?
# 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 ...
Frequently asked questions
Does this skill send emails automatically?
No. The skill mandates a draft-first approach unless the user explicitly requests a live send.
How does the skill verify that an email was sent?
The skill requires confirmation that the message landed in the Sent folder or an equivalent sent-copy store.
Can I use this skill for direct messages or iMessage?
No. The skill instructs the user to hand off DM or iMessage tasks to the messages-ops skill.
Related skills
cold-email
63.5KSales development representatives, founders, and professionals conducting B2B cold outreach
The cold-email skill generates B2B cold outreach emails and follow-up sequences. It prioritizes human-sounding, concise copy that focuses on the recipient's perspective rather than vendor-style pitches. The skill incorporates product marketing context from local files to tailor messaging and utilizes specific frameworks for subject lines, body content, and calls to action.
gws-workflow-email-to-task
17.9KUsers who manage tasks directly from their Gmail inbox via the command line
The gws-workflow-email-to-task skill converts a Gmail message into a Google Tasks entry using the gws CLI tool.
recipe-email-drive-link
16.7KUsers who need to automate file sharing and email communication within the Google Workspace ecosystem
This skill automates the process of locating a Google Drive file, granting reader permissions to a specific email address, and sending the file link via Gmail.
recipe-label-and-archive-emails
16.6KUsers who manage Gmail accounts via the command line and require automated inbox organization
This skill automates Gmail inbox management by searching for specific messages, applying labels, and removing the inbox label to archive them.