adelinalsidor

AI Email Assistant — AI skill for Claude Code

AI community

AI-powered triage for a shared team inbox.

How to install AI Email Assistant

This entry records only its repository, not the path inside it, so there is no exact command to give. Open adelinalsidor/ai-email-assistant and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AI Email Assistant does

AI-powered triage for a shared team inbox. Uses IMAP + Claude — not a vendor API or MCP — so it works with any mail provider. Triggered on a schedule (cron / Task Scheduler), it tags each new email by owner and urgency right in the mailbox, unattended.

Alternatives in AI

Agmsg — Cross-vendor messaging for CLI AI coding agents — let Claude Code, Codex, Gemini & Copilot talk to each other 1.5k ★
Phantom — An AI co-worker with its own computer 1.3k ★
Nativeprompt — Rewrite your prompt into the native dialect of the model you're actually running (Claude Code / Codex) — by ea 113 ★

README

AI Email Assistant

AI-powered triage for a shared team inbox. It reads new emails over IMAP, classifies each one with Claude (who should handle it, and how urgent it is), and tags the message directly in the inbox - no folders, nothing moved, nothing deleted.

Built as a portfolio project based on a real consulting scenario for a small logistics team, with the client's identity and data fully anonymized. See [Background](#background) below.

What it does

A small logistics team shares one mailbox. Emails come in for quotes, loading orders, transport documents, delivery status, and complaints, addressed to no one in particular - someone has to read each one and figure out who should act on it and how fast.

This script does that triage automatically, on a schedule:

Connects to the mailbox over IMAP.
Fetches only the emails that arrived since the last run (see Why UID tracking, not "unread").
Sends each one to Claude with the team's current routing rules, asking for a category, an urgency level, and one sentence of reasoning.
Tags the message in place with two IMAP keywords - who it's assigned to (Assigned-A, Assigned-B, ...) and how urgent it is (Urgent / Today / CanWait, meant to map to a red/yellow/green colored tag in the mail client).
Logs every decision to a local CSV, so there's a record of who got assigned what and why - useful for a periodic summary to whoever manages the inbox.

Nothing is moved out of the shared inbox. Each team member filters by their own tag to see their queue; the manager sees everything, unfiltered, for free.

Why tags instead of folders

The first design considered routing by moving each email into a per-person subfolder. That works well for a single person's inbox, but it actively hurts a *shared* inbox: the whole point is that a manager can see the team's overall activity at a glance, and splitting mail across folders means checking N folders instead of one.

Tagging