The Inbox Line Cook

Let's start with what this lesson is not, because the difference is the lesson. Every automation catalog sells "AI reads your email!" — which means handing an app the keys to your entire inbox: every contract, every HR thread, every password reset. For a work account, that's not a productivity decision. That's a security decision wearing a productivity costume.

There's a quieter move that gets you most of the value at none of the exposure: the export. You choose a pile of mail, bring it to the agent as files, mask what's private, and get back the thing you actually wanted — not a robot answering for you, but a line cook who's pre-read everything and tells you: these three need you today, these can wait, these are noise, and here's a draft for the hard one.

What you'll plate today

A triage digest built from a real day's mail — needs-you / can-wait / noise, with a suggested one-line answer for the quick ones — plus the export-and-mask ritual that makes it safe to repeat.

Ingredients

• Your prep-station kitchen
• A folder of exported mail: in Outlook desktop, select a day's messages and drag them into a mail-drop folder inside your project (they land as files). Gmail web: open each mail → ⋮ → "Show original" is heavy; the lighter path is select-all → forward as attachment to yourself, or simply copy-paste the inbox list view into mail-drop/inbox.txt. Ugly works.
• About 30 minutes

Cook

1. Seatbelt first — this is the drill now

Your Lesson 1 house rule was built for this moment:

There's exported work mail in mail-drop/. House rule applies
doubly: list ONLY the file names and count first. Then, before
reading contents, tell me what categories of sensitive things
mail usually contains, and propose what to mask. Wait for my go.

Its list will be sound — names, addresses, account numbers, salary talk, legal threads. Decide like the owner:

Go, with masking: replace people's names with roles (boss, client-A,
vendor), drop signatures and legal footers, skip anything from HR
entirely. Work from masked copies only.

The skip-HR line is the one to feel: masking isn't only mechanical — some categories don't enter the kitchen at all. You just wrote your first data-handling policy. Lesson 9 makes it official.

2. Order the triage

Read the masked pile and cook me a digest, digest.md:

1. NEEDS ME — must be answered by me, today. One line each: who
   (role), what they want, and the deadline if any.
2. CAN WAIT — needs me, but not today. One line each.
3. FYI/NOISE — needs nothing. Just count these and list senders.
4. For each NEEDS ME item: draft a one-line reply I could adapt.

Order by urgency. If something is genuinely unclear, say so —
don't guess importance.

Read the digest against your own sense of the pile. The first run usually mis-ranks one thing — a sender whose mail looks routine but never is. That's a rule for the notebook:

Anything from [role] is always NEEDS ME, whatever it looks like.
Add that to CLAUDE.md.

3. Taste the drafts, keep the keys

Look at the suggested replies. Some will be exactly right — send them (you, pasting, in your mail client — the agent never touches the send button, same law as Lesson 3). Some will be tonally off; adjust once and teach it: "my declines are warmer than that — always offer an alternative time."

Notice what happened to the chore: not eliminated — shrunk to its true size. Forty mails became three decisions and two pastes. The reading was never the work; the deciding was, and that stays yours.

4. Make it a station

Create a skill "line-cook": when mail lands in mail-drop/, run the
mask ritual, cook digest.md, then empty mail-drop when I confirm.
Save point "the line cook", mark the chore done in CHORES.md.

For the ambitious: the fully-plumbed version of this station — rules that file mail before you ever see it — is a different dish with real tradeoffs, and we cooked it honestly in the One Pantry recipe. Read it after this habit sticks. Export-first is not the training wheels; for work mail, it's the grown-up setting.

When it burns

• Export is miserable on your mail system — don't fight it; degrade gracefully. Even a screenshot-paste of the inbox list gives the triage 80% of what it needs. The ritual matters more than the format.
• The digest missed the day's actual most important mail — check: did it ever enter mail-drop? Triage can only rank what you exported. (The most important mail is often the one you already answered — which is why NEEDS ME feels short. Good sign, not a bug.)
• Masked drafts read stilted ("Dear client-A") — drafts are for you, so that's fine: you re-personalize when pasting. If it grates: "keep salutations generic — 'Hi,' works."
• You're tempted to run this on your personal inbox too — knock yourself out; it's your data. The seatbelt drill is identical, which is exactly why we practiced it on the scarier account first.
• A colleague asks "what app is that?" — the honest answer is good marketing: "no app — nothing leaves my machine, I export and it reads files." Remember the reaction for Lesson 10; that colleague just pre-ordered.

Order up

□ Mail entered the kitchen as an export — masked, HR skipped
□ digest.md: needs-you / can-wait / noise, with draft one-liners
□ At least one ranking rule taught and saved
□ The send button never left your hand
□ Skill "line-cook" standing by; CHORES.md third DONE

Next up — Lesson 05: The Meeting Prep. The transcript nobody reads, the action items nobody wrote down — thirty seconds after the call ends, both exist.

Stuck on a step? Question box below.