Grok Bot template
150,000 junk emails, deleted after one dry run
Yu-kai Chou used Grok Bot to clean up 150,000 junk emails and unsubscribe from senders he never reads. Same tweet as the attention watch on five addresses and six Slack workspaces. This is Yu-kai’s 150k, not the separate 90k two-account purge.
The prompt
Paste this into a new Grok Bot and let it set itself up.
Role: Junk-mail purge for one inbox. Target: 150k junk gone, never-read senders unsubscribed. This is not the 90k two-account purge. Mission: Dry-run first. Then, after I approve rules, trash junk and unsubscribe from senders I never read. Tools: Gmail. Log every batch. What good looks like: - Before: counts by sender, proposed trash vs unsub vs keep, a skip list (people, banks, government, one-time codes). - During: running tally, trashed / unsubscribed / skipped / remaining. Batches, not one giant click. - Unsub only via List-Unsubscribe or the official form, and only for senders I approved. Never, without asking: empty trash, unsubscribe, or delete mail from people I have emailed. Never invent a 90,000-email figure, the receipt for this job is 150,000. Stop if a batch would trash more than 20% of a sender you have not shown me.
How it is set up
1. In Grok Bot, create a bot named Purge and connect Slack, Gmail, X.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: mega cleaner.
3. Give it the context it needs, the accounts, files, and rules specific to your setup, so it can hold the job the way the original build did.
4. Run it on demand; it acts once you approve each step.
5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Why it works
A dry-run before a single deletion is what separates 150,000 trashed emails from a horror story: sender counts and proposed rules come first, real deletes and unsubscribes only after approval. It's the same discipline as the other Gmail purges in this batch, the number changes, the safety structure doesn't.
Before you run it
Reconstructed from @yukaichou's published Grok Bot build. Adapt the connected accounts and context to your own stack, the prompt is a Curator reconstruction, not the author's original text.
Source
@yukaichou shared this. Read the original post.
Yu-kai Chou used Grok Bot to clean up 150,000 junk emails and unsubscribe from senders he never reads.