email-ops

Triage, draft, and verify email sends against the Sent folder.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill email-ops-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-ops
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/email-ops
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill email-ops-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Email Ops helps you triage and draft real outbound messages while providing evidence-safe verification that what you sent actually landed in Sent.

Core Features & Use Cases

  • Mailbox triage and safe cleanup: Organize or archive low-signal mail without deleting uncertain business messages.
  • Evidence-first drafting and replying: Create context-aware replies after reading the thread and identifying commitments, deadlines, and unanswered questions.
  • Sent-proof send workflow: Support live sending while verifying the message appears in Sent (or an equivalent sent-copy store) before claiming success.
  • Account-appropriate routing: Choose the correct sender mailbox account and avoid casually switching accounts without intent.

Quick Start

Use email-ops to draft and verify a reply in the correct mailbox thread, then confirm what landed in Sent.

Frequently Asked Questions about email-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an email was actually sent without just assuming the client delivered it?

To verify an email was sent, you must check the Sent folder or an equivalent sent-copy store for the specific recipient or thread. This evidence-first approach confirms the message landed before reporting a successful sent state.

What is the best way to draft a context-aware email reply that captures previous commitments?

Drafting a context-aware reply requires reading the thread first to identify commitments, deadlines, and unanswered questions. This prevents sending contextless messages and ensures your response directly addresses the ongoing conversation.

How to triage and organize a mailbox without accidentally deleting important business messages?

Triage your mailbox by organizing or archiving low-signal mail while avoiding deletion of uncertain business messages. This safe cleanup process uses guardrails to prevent data loss during inbox organization workflows.

Can I use RBAC to route outbound messages from the correct sender mailbox account?

Yes, RBAC supports account-appropriate routing by ensuring you choose the correct sender mailbox account. This prevents casually switching accounts without intent and maintains strict sender identity control.

Why does my email workflow accidentally claim messages were sent when they failed?

False send claims happen when workflows lack sent-verification guardrails. Requiring client-side confirmation or Sent-folder verification before reporting a sent state prevents unverified or contextless email actions.

Do I need any specific email client or platform to run sent-proof mailbox workflows?

No specific platform is required, but your environment must support reading mailbox threads and accessing a Sent-folder or equivalent sent-copy store to validate outbound delivery before confirming success.