agency-email-intelligence-engineer

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

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-email-intelligence-engineer-immamdouhaboammar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-email-intelligence-engineer
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/engineering-email-intelligence-engineer
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-email-intelligence-engineer-immamdouhaboammar

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 AI agents misattribute action items and decisions. This Skill builds pipelines that convert MIME, Gmail API, and Microsoft Graph email data into clean, structured, reasoning-ready context. ## Core Features & Use Cases - Thread Reconstruction: Resolves In-Reply-To/References header chains to rebuild conversation topology across replies, forwards, and forks. - Quoted Content Deduplication: Strips prefix-based, delimiter-based, and Outlook XML quoting to reduce token bloat by 4-5x without information loss. - Participant & Action Item Extraction: Binds commitments and decisions to the correct sender using preserved From: headers, producing participant maps and decision timelines. - Hybrid Retrieval & Context Assembly: Combines semantic search, full-text search, and metadata filters with token-budget-aware context assembly and source citations for LangChain, CrewAI, and LlamaIndex tools. - Use Case: Point an agent at a 20-message enterprise thread and receive structured JSON with deduplicated content, attributed action items, a decision timeline, and citations grounded in specific messages. ## Quick Start Ask the agent to reconstruct and analyze an email thread from your Gmail or IMAP source, returning structured JSON with participants, action items, decisions, and cited context for a given query.

Frequently Asked Questions about agency-email-intelligence-engineer

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

FAQPage Schema
How do I convert raw email threads into structured data for AI agents?▼

Parse raw MIME messages preserving In-Reply-To and References headers, reconstruct the thread topology as a reply graph, then strip quoted content and extract participants, decisions, and action items. The output is structured JSON with source citations that agent frameworks can consume directly.

How to deduplicate quoted replies in email threads?▼

Detect quoting styles including prefix-based '>' lines, delimiter markers 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.

Does this work with Gmail API and Microsoft Graph?▼

Yes, the pipeline ingests email from Gmail API, Microsoft Graph API, IMAP/SMTP, and Exchange Web Services, plus raw MIME files. It normalizes structural differences across providers since Gmail, Outlook, and Apple Mail all quote and forward differently.

Why do AI agents misattribute action items in email threads?▼

Flattened threads strip From: headers, making first-person pronouns like 'I' ambiguous across messages. The fix is binding each commitment to the actual sender at the message level during extraction, preserving participant identity through the entire pipeline.

Can I integrate email intelligence with LangChain or CrewAI?▼

Yes, the Skill defines tool interfaces for LangChain, CrewAI, LlamaIndex, and custom MCP servers. Example tools include email_ask for natural language questions with citations and email_search for hybrid retrieval with metadata filters.

What are the limitations of email thread processing?▼

Email structure varies across 40 years of clients and providers, so ambiguous or malformed threads require graceful degradation rather than perfect parsing. Forwarded chains collapsing multiple conversations and cross-thread decision dependencies remain hard edge cases requiring provenance tracking.