agency-email-intelligence-engineer

Parse email threads into structured JSON with topology, participants, and citations.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/anavvanzin/Research --skill agency-email-intelligence-engineer-anavvanzin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-email-intelligence-engineer
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-email-intelligence-engineer
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-email-intelligence-engineer-anavvanzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracting structured, reasoning-ready data from messy email threads to power AI agents and automation pipelines, preserving thread topology and ensuring safe attribution.

Core Features & Use Cases

  • Thread reconstruction and participant detection across forwards, replies, and forks
  • Quoted text deduplication and provenance-aware context assembly for agent frameworks
  • Structured output with source citations, decision timelines, and action-item attribution for multi-tenant use

Quick Start

Instruct your AI to ingest an email thread and output a structured JSON with thread topology, participants, decisions, actions, and 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 raw email threads for AI agents?

You extract structured data from raw email threads by ingesting the MIME content and reconstructing the message topology. This produces reasoning-ready JSON context with participant attribution, decision timelines, and source citations for AI agent frameworks.

What is the best way to deduplicate quoted text in forwarded email chains?

Deduplicating quoted text in forwarded email chains involves parsing MIME headers to reconstruct thread topology. This provenance-aware deduplication removes redundant reply fragments while preserving attribution, ensuring clean context assembly for downstream agent processing.

Can I use MIME parsing to reconstruct email forks and reply trees?

Yes, you can use MIME parsing to reconstruct email forks and reply trees. By analyzing header-based threading data, the system maps complex multi-tenant email topology, detecting forks and participant relationships across forwards and replies.

How do I generate token-conscious context from multi-tenant enterprise emails?

Generating token-conscious context from multi-tenant enterprise emails requires assembling deduplicated thread fragments with provenance awareness. This structured output includes source citations and action-item attribution while respecting token limits for agent consumption.

Does thread reconstruction work for multi-tenant email pipelines requiring action-item attribution?

Thread reconstruction works for multi-tenant email pipelines by mapping participant detection and decision timelines across forks. It outputs structured JSON with safe attribution and source citations, ensuring isolated, reasoning-ready context for each tenant's agent workflows.