USE CASEWorkModerate

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.

Grok·0.0·0 saves·8 uses·via @yukaichou·Tweet by @yukaichou

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Purge** and connect Slack, Gmail, X.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: mega cleaner.
  3. 03Give 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. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

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.

Prompt

Copy it. Change the names. Keep the job.

Prompt
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.
Use withGrok

via @yukaichou · Tweet by @yukaichou

Tips

  • ·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.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup