The noise leaves your inbox every evening

Why It Works

The email that mattered was not lost, it was under thirty that did not matter, and you found it two days late. That is an inbox doing a sorting job an assistant should be doing for you, and it is the one job an assistant can be trusted with on day one, because the rule is small. Take out the things that are noise by definition, calendar acceptances, notifications, marketing, out of office replies, and leave every single other thing exactly where it was. Done every evening, what you open in the morning is only the things that want something from you.

The skill files, it never deletes, and every email it moves gets a label so a wrong call is one click back. It never touches a person you know, anything you have replied to, anything about money, security, sign-ins or deliveries, or anything unread from a human. And it learns from you, because what you bin by hand is noise it missed and what you rescue is a wrong call, so it proposes a rule from each and you say yes or no.

Step One, Install It

Here from the video? This is the line. Open a new chat in Claude Code and paste it. Claude fetches the skill from the repo, puts it where skills live, checks it can read your inbox and change labels, interviews you one question at a time for the people it must never touch, creates the label, and runs once against your inbox as it stands so you see what it filed and what it held back before it ever runs alone. Filing an email is a label change, and the built-in Gmail connector cannot make one, so if the check fails it gives you three lines to run in your terminal, a free connection that takes five minutes once, and you paste the same prompt again.

If you would rather read it first, the skill is one file at github.com/oliwoodman/inbox-tidy-skill, and everything it may file and everything it never touches is written in it in plain English.

Step Two, Every Evening

A tidy you have to remember to start is one more thing in the inbox. Once the first run looks right, paste this and Claude creates the schedule itself, whatever your machine needs, and tells you what it made and how to switch it off. From then on it runs at six every evening whether you thought about it or not, and the look at what you binned runs inside it. In Claude on the web there is no schedule, so it will say so and give you the one line to send each evening instead.

One Honest Bit

A closed list leaves noise behind, and it is meant to. Leaving noise is a bad night. Filing something you needed to see is a broken feature, and the two mistakes do not cost the same, so the list stays small and grows only when you say yes. The first week you will find things it missed, which is the learning loop doing its job rather than the skill failing. It also stops at twenty five threads a run, because a night that wants to file fifty is a night something has gone wrong with the rules, not the inbox.

Never delete is the whole safety of this, and it is a rule the skill keeps rather than a feature that comes with the tool. Archived with a label is one search away for ever. Deleted is gone in thirty days, and the one time it matters you will not know until it is too late.

Where This Goes Next

The tidy is the last thing my evening run does, after the replies are drafted, because a thread that has left the inbox cannot be answered. Your inbox already has the replies written is that first half, and the meeting your AI books with you every morning is where the note of what it filed lands.

This is one job out of a set that all run off the same foundation. If the idea of an agent is still fuzzy, an AI agent is a chat with a job is the plain English version and the start of the series.