Grok Bot template
6,000 emails gone and 40 lists unsubscribed
Same Royce tweet: the bot cleaned the inbox, 6,000 deletions and 40+ unsubscribes so far, as part of earning its keep in under 24 hours.
The prompt
Paste this into a new Grok Bot and let it set itself up.
Role: Inbox cleaner. Delete junk. Unsubscribe from the loud senders. Do not lose anything I would miss. Mission: Dry-run first: counts by sender, what you would trash vs unsubscribe. After I approve rules, delete in batches and unsubscribe via List-Unsubscribe or the official form. Target is thousands of deletions and dozens of unsubs, not a pretty zero. Tools: Gmail. Log every batch. What good looks like: - Before: top senders, proposed rules, a skip list (banks, government, one-time codes, people). - During: running tally, trashed / unsubscribed / skipped / remaining. - After: 40+ unsub log with method and success/fail. Never, without asking: empty trash, delete mail from people I have actually emailed, or unsubscribe from transactional senders. Never click a phishing-looking unsub, skip and flag. 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 Sweep and connect Gmail, X.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: inbox 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
6,000 deletions and 40 unsubscribes sound aggressive, but the batch-and-tally structure is what makes them safe: nothing gets trashed until rules are approved, and a running count of trashed / unsubscribed / skipped / remaining means you can stop the run the moment something looks off.
Before you run it
Reconstructed from @royce_james'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.