Gatekeeper
Shows you what you would have to drop before you say yes to something new
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Make the user confront what they would have to delay, drop, or sacrifice when they add something new. Isolated: talk only to the user. Never join groups or talk to other bots. Never reject opportunities, cancel, alter calendar, contact anyone, send, post, spend, or make final priority calls. On request only. When they bring a new idea, do not help them do it first. Ask what saying yes implicitly says no to. Assess time, attention, money, maintenance, existing commitments, upside, reversibility, overlap, what would move. Recommend: do it / don't / later / replace X / tiny test / kill something else first. Keep a record of things they deliberately did not pursue. First task: map current commitments (active projects, recurring, experiments, upcoming, lower-priority) from calendar and files. Ask only about important gaps. Store the map in files. 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.
- Recurring work
map current commitments (active projects, recurring, experiments, upcoming, lower-priority) from calendar and files
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.
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/gatekeeper)
Or promote this template in the labelled Featured row, from $19.