Chief of Staff
Morning email and calendar triage after a guided Gmail and Google Calendar setup
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Personal Chief of Staff that on first install walks you through full setup: Gmail, daily 9am top-3 email triage, Google Calendar, daily 9am meeting prep, builds the companion fleet (Email, Calendar, Relationships, LinkedIn), then Fitness Goals — Notion skipped. Triages priorities and coordinates bots without sending until you approve.
Description as published on the x.ai share page when last checked (2026-11-22).
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 CalendarNotionLinkedIn
- Recurring work
Gmail, daily 9am top-3 email triage, Google Calendar, daily 9am meeting prep, builds the companion fleet (Email, Calendar, Relationships,…
- Promised limits
Triages priorities and coordinates bots without sending until you approve
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
Someone who wants a single setup conversation to stand up a small fleet of specialist bots for email, calendar, relationships, and LinkedIn, rather than configuring each one by hand.
Not for
Anyone who wants to keep Notion entirely out of a Grok Bot setup, since the description names it as one of the steps even though it can be skipped.
What it does
On its first run the bot walks you through connecting Gmail and Google Calendar, then sets up a 9am routine that triages your top three emails and preps you for the day's meetings. From there it builds out a small group of companion bots covering email, calendar, relationships, and LinkedIn, with a fitness-goals step offered alongside them. Once setup is finished, it works as the coordinator across that group, surfacing what matters each morning while holding every send for your approval first.
First messages to try
- Walk me through the full setup now: Gmail, Google Calendar, the companion fleet, and fitness goals. Tell me before each step what access it needs.
- Skip the fitness goals and Notion steps for now. Set up just the morning email and calendar routine and show me what tomorrow's 9am brief will look like.
- Show me the companion fleet you built: what does each one (Email, Calendar, Relationships, LinkedIn) actually do, and which of them can send something without asking me first?
Apps and accounts
Its description mentions Gmail, Google Calendar, LinkedIn, and Notion as setup steps, so expect prompts to connect each account during onboarding. It also says Notion is skipped by default, so that one connection is optional rather than required.
Cautions
- A group of four or five companion bots reporting through one coordinator can use up your usage allowance faster than a single bot; watch the meter during the first week.
- Say which, if any, of the companion bots may draft or send on LinkedIn, since that's the one channel here that reaches people outside your own accounts.
Compare with: DOGE (Department of Grok Efficiency) by AvidChief of Staff by Vaibhav Arora
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 Calendar, Notion, LinkedIn. 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, Sravan v J. 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 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/chief-of-staff-morning)
Or promote this template in the labelled Featured row, from $19.