One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill email-ops-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-ops
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/email-ops
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill email-ops-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unverified send claims, contextless replies, and incorrect account usage for ECC teams managing business email correspondence, replacing manual, error-prone mailbox work with a structured, evidence-first workflow.

Core Features & Use Cases

  • Evidence-first inbox triage: Sort and archive low-signal emails while preserving important business correspondence to avoid accidental deletion of critical threads.
  • Context-aware drafting and send verification: Create user-facing, investor, or billing-related emails aligned with brand voice, then confirm messages land in the Sent folder before marking them as sent.
  • Use case: An ECC team member can use this skill to triage a crowded inbox, draft a compliant reply to an investor inquiry, and get verifiable proof the message was sent from the correct project account.

Quick Start

Use the email-ops skill to triage my ECC inbox and draft a reply to the latest investor inquiry thread.

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 sent from the correct business account?

Email send verification requires checking the Sent folder to confirm message delivery and prevent false send status reports. This workflow enforces verifiable Sent folder confirmation for investor, billing, and general business communications.

What is the best way to triage a crowded inbox without deleting important business correspondence?

Inbox triage involves sorting and archiving low-signal emails while preserving important business correspondence to avoid accidental deletion. This ensures critical investor and billing threads remain intact during mailbox operations.

How do I draft a compliant reply to an investor inquiry with the right brand voice?

Drafting investor replies requires context-aware composition that preserves thread context and aligns with brand voice. This ensures business correspondence meets compliance standards for user-facing and billing-related communications.

Can I use this email management workflow for account-specific send routing?

Yes, this email management workflow satisfies requirements for account-specific send routing. It ensures business correspondence is sent from the correct project account, preventing incorrect account usage for investor and billing communications.

Why does my email management workflow produce unverified send claims?

Unverified send claims occur when email workflows lack evidence-first Sent folder confirmation. Replacing manual, error-prone mailbox work with structured verification eliminates false send status reports and contextless business correspondence.