agency-email-intelligence-engineer

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

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-email-intelligence-engineer-ai-staffing-solution-consultants-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-email-intelligence-engineer
Source: https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system/tree/main/.agents/skills/engineering-email-intelligence-engineer
Command: npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-email-intelligence-engineer-ai-staffing-solution-consultants-llc

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 From: headers so action items get attributed to the wrong people. This Skill builds pipelines that convert raw email into clean, structured context that AI agents can reason over reliably. ## Core Features & Use Cases - Thread Reconstruction: Resolve In-Reply-To/References header chains to rebuild conversation topology across replies, forwards, and forks. - Quoted Content Deduplication: Strip prefix-based, delimiter-based, and Outlook XML quoting to reduce token bloat by 4-5x without information loss. - Participant & Action Item Extraction: Bind commitments and decisions to the correct sender using preserved message-level identity. - Hybrid Retrieval & Context Assembly: Combine semantic search, full-text search, and metadata filters with token-budget-aware context assembly and source citations. - Use Case: Connect a Gmail or Microsoft Graph mailbox, index historical threads, and expose LangChain tools like email_ask and email_search so an agent can answer questions with citations grounded in specific messages. ## Quick Start Ask the agent to reconstruct and deduplicate a raw email thread, then extract the participant map, decisions, and action items as structured JSON with source citations.

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 extract structured data from email threads for AI agents?▼

Parse raw messages with MIME-compliant parsing, rebuild the reply graph from In-Reply-To and References headers, strip quoted content, then emit structured JSON containing participants, decisions, action items, and a timeline with per-message 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 any content already present in parent messages. This typically reduces a 20-message thread's token count by 4-5x with no information loss.

Does email parsing work with both Gmail and Outlook?▼

Yes, pipelines can ingest via Gmail API, Microsoft Graph, IMAP/SMTP, or Exchange Web Services. However, quoting and forwarding styles differ across providers, so normalization logic must handle each format rather than assuming consistent structure.

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

Flattened threads strip From: headers, making every first-person pronoun ambiguous. The fix is binding each extracted commitment to the actual sender of its source message using preserved participant identity through the processing pipeline.

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

Semantic search alone misses exact entity matches and struggles with multilingual threads. Hybrid retrieval combining embeddings, full-text search, and metadata filters (date, participant, attachment) produces more relevant context, and chunks must never split mid-message.