Email Intelligence Engineer

Extract structured, reasoning-ready data from raw email threads for AI agents.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill email-intelligence-engineer-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Email Intelligence Engineer
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/engineering/email-intelligence-engineer
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill email-intelligence-engineer-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw email threads are structurally chaotic: quoted replies duplicate content 4-5x, forwarded chains collapse multiple conversations, and flattened threads strip sender identity so action items get attributed to the wrong person. This Skill builds pipelines that convert raw email into clean, structured context that AI agent frameworks can consume reliably. ## Core Features & Use Cases - Thread Reconstruction & Deduplication: Resolve In-Reply-To/References header chains into conversation topology and strip quoted content across Gmail, Outlook, and Apple Mail quoting styles. - Structured Extraction: Build participant maps, decision timelines, and action items with correct sender attribution, output as JSON with source citations. - Hybrid Retrieval & Context Assembly: Combine semantic search, full-text search, and metadata filters with token-budget-aware context assembly, exposed as LangChain tools, CrewAI skills, or MCP servers. - Use Case: Connect a shared mailbox, index historical threads, and let an agent answer questions like "what did the client commit to last quarter?" with citations grounded in specific messages. ## Quick Start Ask the agent to ingest a raw email thread, reconstruct its conversation topology, and return structured JSON with participants, decisions, and action items.

Frequently Asked Questions about Email Intelligence Engineer

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

FAQPage Schema
How do I extract structured data from email threads for AI agents?▼

Parse raw messages via IMAP, Gmail API, or Microsoft Graph, reconstruct the reply graph from In-Reply-To and References headers, then strip quoted content and extract participants, decisions, and action items into structured JSON with source citations.

How to deduplicate quoted replies in email threads?▼

Detect prefix quoting (lines starting with '>'), delimiter quoting like '---Original Message---', and Outlook XML quoting, then remove content duplicated from parent messages. This typically reduces a 20-message thread's token count by 4-5x with no information loss.

Can I use Gmail API and Microsoft Graph in the same email pipeline?▼

Yes, but never assume structure is consistent across providers. Gmail, Outlook, Apple Mail, and Exchange all quote and forward differently, so normalize messages into a common schema before thread reconstruction and indexing.

Why are action items attributed to the wrong person in email summaries?▼

Flattened threads strip From: headers, making every first-person pronoun ambiguous. Preserve participant identity per message through the pipeline and bind each extracted commitment to the actual sender of that message.

What are the limitations of semantic search over raw email?▼

Semantic retrieval fails when content is corrupted before indexing, such as duplicated quotes or collapsed forwards. Fix preprocessing first, chunk only at message boundaries, and combine semantic search with full-text and metadata filters.