email-communicator

Centralize Gmail send, reply, search, and read operations for ACE skills.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill email-communicator-dimagi-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-communicator
Source: https://github.com/dimagi-internal/ace/tree/main/skills/email-communicator
Command: npx skills add https://github.com/dimagi-internal/ace --skill email-communicator-dimagi-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for individual ACE skills to implement their own Gmail access logic, centralizing all email operations for the ACE Gmail account to ensure consistent compliance with approval requirements, thread logging rules, and identity guardrails.

Core Features & Use Cases

  • Centralized Gmail Access: Provides a single, approved interface for all ACE skills to send, reply, search, and read Gmail messages, removing redundant Gmail integration code from individual skills.
  • Compliance & Routing Guarantees: Enforces procedural approval for all outbound sends and automatically logs thread and message IDs to the run's comms-log, ensuring all inbound replies are correctly routed to their associated opportunity runs.
  • Use Case: When an ACE skill needs to send a follow-up email to a Connect opportunity stakeholder, it delegates to this skill to handle the send, capture the thread ID for future reply routing, and enforce required approval steps.

Quick Start

Use the email-communicator skill to send a follow-up email to the Connect opportunity stakeholder with the subject "Q3 Progress Update" and the approved body content.

Frequently Asked Questions about email-communicator

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

FAQPage Schema
How do I centralize Gmail send and reply operations across multiple skills?

Centralizing Gmail send and reply operations across multiple skills eliminates redundant integration code by providing a single approved interface. This ensures consistent compliance with approval gates and automatic thread ID logging for routed replies.

What is the best way to track email thread IDs for routed replies in automated workflows?

Tracking email thread IDs for routed replies is handled automatically by logging thread and message IDs to the run's comms-log during every outbound send, ensuring inbound replies are correctly routed to their associated opportunity runs.

How do I enforce approval gates for outbound emails in Gmail automation?

Enforcing approval gates for outbound emails in Gmail automation requires a centralized communication skill that applies procedural approval requirements to all outbound sends, preventing unauthorized messages from being dispatched.

Can I use a single Gmail account for searching and reading emails across different workflow skills?

Using a single Gmail account for searching and reading emails across different workflow skills is fully supported. The centralized interface manages compliant Gmail access via the designated account and CLI, removing the need for individual skill integrations.

Why do I need a centralized email communicator instead of building Gmail integration logic into each skill?

You need a centralized email communicator instead of building Gmail integration logic into each skill to ensure consistent compliance with approval requirements, thread logging rules, and identity guardrails across all opportunity lifecycle workflows.

Does centralized Gmail access support inbound email triage for opportunity lifecycle workflows?

Centralized Gmail access fully supports inbound email triage for opportunity lifecycle workflows by providing search and read operations that route inbound replies to their associated opportunity runs using logged thread tracking.