email-triage

/email-triage — Reliable conversation-level email triage

Account-to-CLI map and mail/calendar search rules: ~/repos/claude-config/docs/accounts.md.

/check-email is for quick inbox glances. This skill is for trustworthy backlog triage over a long window (weeks/months), where the cost of a wrong verdict is real (chasing a closed deal, missing a live one).

The failure mode this skill exists to prevent

Naive triage judges a thread from one message's bodyPreview. That is wrong because:

• Mobile replies roll into quoted text. A reply Magnus sent from his phone often does not appear as a separate sentitems row in the window — it lives inside the quoted body of a later message. Judging by inbox rows alone makes resolved threads look open.
• The last inbound message is not the same as an open obligation. Martin/Saab, Koenigsegg, William — all were flagged "needs Magnus" when Magnus had already replied (or the ball was explicitly in the other party's court).
• bodyPreview truncates before the resolution. "Thanks for this — will get back within 1–2 weeks" reads as a question in preview; the closure is past the cutoff.
• A draft is not proof of an unsent obligation. Outlook leaves a lingering draft twin when you save-then-send, and old drafts from long-resolved threads persist forever. Because drafts are fetched with no date filter, a draft from months ago surfaces as "action owed" even though the offert was sent and the deal closed outside the window (Uddevalla: a March offert+acceptance was invisible to an April-onward window, so the March draft looked unsent). And a draft can carry a newer lastModifiedDateTime than a real sent reply in the same thread, making the sent reply look absent (Saab: an empty draft shadowed a substantive sent reply from the same morning).
• The date window clips conversations. The window is a discovery filter for finding candidates, not the boundary of a conversation. A thread that looks open inside the window is frequently resolved by sent/received messages just outside it.
• A deliverable is often sent as a new thread, not a reply. Magnus answers a request by composing a fresh email with a new subject — so it has a different conversationId than the request and the lingering draft. ConversationId grouping alone never connects them, so the request looks unanswered and the draft looks unsent (Photowall: the planning-meeting invite + an "Underlag inför vårt samtal" draft looked open, but the material had been sent May 31 as "AI-utbildningar Photowall — upplägg & förslag (juni)" — a separate thread to the same person). Cure: reconcile by counterparty, not just by conversationId.
• The agent has no clock — it guesses dates. Without today's date stated explicitly, the subagent invents relative deadlines ("passed yesterday", "overdue") and gets them wrong (AFRY: a June-5 deadline was called overdue on June 3). Today's date must be injected, and every deadline claim must show the arithmetic.
• Editorial nudges masquerade as obligations. The agent likes to add prophylactic "worth confirming X soon" actions that no inbound message actually asked for, inflating the owed-list with invented work (Traton: "confirm final agenda" — nobody asked). Only a quotable inbound request is an obligation.