Hire an AI email parsing engineer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A thread map in order, showing who replied to whom and any forks or forwards
• A participant list with each person's first and last message
• A message table with only the new text from each message
• A decision list and a task list, each tied to the message and sender behind it
• A problems list of anything it could not settle
• A pipeline plan with fields, rules and tests, if you asked for one

How it does the job well

• Never treat a flattened thread as one document. Keep each message separate, with its sender.
• Bind every request, decision and task to the sender of the message that made it. "I will" belongs to that sender. A person who is only mentioned or asked is not the owner.
• Quoted text is not the current state. A later reply may have changed it. Prefer the latest message and say when quoted text conflicts.
• Remove quoted text only when it repeats an earlier message. Keep a new quote that adds something.
• Mark anything you inferred as Inferred: a person's role, a decision by silence (a proposal nobody objected to), a deadline implied but not stated, who a pronoun refers to.
• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.

Mistakes it avoids

• Giving a task to the person who was asked, not the person who agreed.
• Reading quoted lines as the latest word.
• Filling a missing date, sender or owner with a guess without marking it Inferred.
• Treating different mail systems as if they quote and forward the same way.
• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.

What a good result looks like

An example, not your task: A long thread has five people and three forwards, and you need to know what was decided and who owes what.

• Thread map. The messages in order, who replied to whom and where the thread forks or was forwarded.
• Participants. Each person with their address, role (stated or inferred) and first and last message.
• Message table. One row per message with only its new text, plus its requests, deadlines and attachments mentioned.
• Decisions. Each decision with who proposed it, who agreed and the message it came from.
• Tasks and owners. Each task tied to the sender of the message that took it on, with the due date as written.
• Problems. Anything it could not settle, with the message number and how to resolve it.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the headers. It lists each message with its sender, recipients, date and subject, and notes any message that is missing its ID.
• Rebuild the thread. It uses reply links to put messages in order and shows where the thread forks. A forwarded chain is split into its own parts.
• Remove repeated quotes. It drops quoted text that only repeats an earlier message. A new quote is kept if it adds something.
• Name the participants. It lists everyone who sent or received mail, and marks any role it inferred.
• Tie each item to its writer. Requests, decisions and tasks go to the sender of that message, never to the person who is merely mentioned.
• Check and list problems. It lists doubts, such as two messages with the same ID, a task with no clear owner or an attachment that was not supplied.
• Plan the pipeline (if asked). It lists the fields to keep, the rules for threading and dedupe, how to protect private data and the tests to run.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-email-intelligence-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-email-intelligence-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• One email thread, pasted or attached, with the From, To, Cc and Date lines kept on every message
• What you want out, such as tasks with owners, decisions or a timeline
• The system you are building, if you want a pipeline plan, and the question your AI helper must answer (optional)
• Where the emails come from, such as Gmail, Outlook or exported files (optional)

Helpful context (optional)

• The same thread exported as a file, not copied from the screen.
• A list of the people on the thread and their roles.
• Five real threads that show the kinds of mess your system must handle.

Tools and access

• Claude, ChatGPT or Gemini with file upload: They can read an exported thread file with all its headers, which keeps the sender tied to each message.

Functions and deliverables

• Email parsing engineer: Turn a messy email thread into who said what, decisions and tasks with owners. Or plan the pipeline that does it for many threads.
  • A thread map in order, showing who replied to whom and any forks or forwards
  • A participant list with each person's first and last message
  • A message table with only the new text from each message
  • A decision list and a task list, each tied to the message and sender behind it
  • A problems list of anything it could not settle
  • A pipeline plan with fields, rules and tests, if you asked for one
  Source: Michael Sitarzewski and Agency Agents contributors.
• Dynamic email block planner: Plan dynamic email blocks, show-hide rules and previews from your customer fields, apps and offer terms, before you send anything.
  • Show-hide rules with the exact property values to use
  • Product feed settings and a reusable block plan
  • App-triggered flows and abandonment block settings
  • A list of predictive data uses, and a test list for each rule
  • Separate first-order and returning-customer rules, with incomplete history marked unresolved
• Email inbox rule writer: Use questions and past replies to build files for email groups, reply style, and sender rules.
  • A sorting scheme for your mail
  • A reply voice file with templates
  • Rules on senders and priorities
  • Seven saved files the triage skill reads
  Source: Alireza Rezvani.
• Email call to action editor: Paste your draft and get a clearer email with one ask, a date and a reason in the first three lines. Edit a work email before you send it.
  • Every ask in your draft, counted and quoted
  • The rewritten email with the ask, date and reason in the first three lines
  • The parked asks and where they go
  • The word count before and after
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• A long thread has five people and three forwards, and you need to know what was decided and who owes what.
• You are building an AI helper that answers questions about customer emails and need to know what fields to keep.
• A summary tool keeps giving a task to the wrong person and you want to see why.
• You are about to hand a deal thread to a teammate and want a clean record to go with it.

Limits to check before starting

• You want to read your live inbox or send replies. This agent works on text you paste. Use the Customer inbox reply drafter for new customer emails.
• You want minutes from a meeting, not an email thread. Use the Meeting notes writer.
• You need production code, hosting and tests. This agent gives a plan and a design. Hand it to a developer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
• Paste one thread, or attach it as an exported file. Keep the From, To and Date lines. Stripped headers lead to wrong owners. Check you may share the emails with your AI tool.
• Type "Parse this thread into the message table, decisions and tasks with owners. Mark anything you inferred."
• Check the task list against the thread. Is each owner the person who made that promise? Fix any that are wrong and tell it why.
• To plan a system, say where the emails come from and what question your AI helper must answer. Ask for "the pipeline plan".
• Hand the plan to your developer, or keep it as the spec for the tool you buy.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-email-intelligence-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.