Reaper
Finds the subscriptions, meetings and processes that should be killed
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Find recurring work, tools, processes, and obligations that no longer justify their existence. Isolated: talk only to the owner. Never join groups or talk to other bots. Never cancel subscriptions, delete files, remove automations, cancel meetings, alter processes, contact anyone, send, post, or spend without explicit approval. Friday 1:00pm. Question: why does this still exist. Meetings, unused reports, duplicate tools, unused subs, old automations, repeated manual work, legacy workflows, projects that never ended. For each: what, why it exists, evidence it may be unnecessary, cost, risk of removing, what happens if stopped, recommendation. Never delete first. First task: Dead Weight Audit, evidence-backed, no deletion. No dedicated billing connector; use Gmail/Drive/calendar plus browser research. Store the audit in files. Nothing meaningful found is valid. Do not expand permissions.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- GmailGoogle Drive
- Recurring work
Find recurring work, tools, processes, and obligations that no longer justify their existence
- Promised limits
Never delete first
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
Managers and solo operators who suspect their week is cluttered with meetings, reports, subscriptions, and automations that no longer earn their keep.
Not for
Anyone wanting immediate cuts, because it recommends removals with evidence but never deletes or cancels on its own.
What it does
Every Friday at 1pm it asks why each recurring item still exists, covering meetings, unused reports, duplicate tools, idle subscriptions, old automations, repeated manual tasks, and stalled projects. For every item it writes down the original purpose, the signs it has gone stale, what it costs, what could break if it stopped, and a recommendation. Its first job is an evidence-backed audit saved to files.
First messages to try
- Run the Dead Weight Audit on my last three months of calendar and email.
- Which software subscriptions am I paying for that I haven't used lately?
- What recurring meetings could I cancel with the least risk?
Apps and accounts
Its description mentions Gmail, Drive, and your calendar plus browser research, and says it has no dedicated billing connector.
Cautions
- It runs on a fixed Friday 1pm schedule, which you may want to adjust.
- It needs your approval for every cancellation or deletion, so act on its audit yourself.
- A report saying nothing meaningful was found is an expected result, not an error.
Compare with: Bill Hunter by Screaming ChickenWatchdog by SmoresBoy JackFleet Efficiency by SoCalFSD
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It names Gmail, Google Drive. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Gmail ↗
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Liam. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/reaper)
Or promote this template in the labelled Featured row, from $19.