DOGE (Department of Grok Efficiency)

A single-desk chief of staff that runs your day and your company at once

Summary excerpt from the creator’s share page. Not independently tested. Previously listed as “Chief of Staff (Avid)”.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

A Grok Bot whose only job is to audit your other bots and routines, flag what to cut or merge, and find bottlenecks. It never changes anything without your yes.

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
A Grok Bot whose only job is to audit your other bots and routines, flag what to cut or merge, and find bottlenecks
Works with other Bots
A Grok Bot whose only job is to audit your other bots and routines, flag what to cut or merge, and find bottlenecks
Our take

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

A founder or operator who wants one senior coordinator for both their day and their company, with specialist Bots underneath and a strict rule that sending, paying, posting, and merging stay with the human.

Not for

Anyone who wants the Bot to create more Bots or open new rooms on its own, which it is written to refuse.

What it does

This is the most rule-heavy Chief of Staff template in the directory: on first run it won't start work until you name who it reports to, your time zone, which specialists exist, where memory lives, and what your final approval covers. After that it keeps a board of what's moving, what's blocked, and what's waiting on you. It assigns research, drafting, scoring, and build work to specialists, reviews what comes back, and handles inbox triage drafts and the calendar. It files work before reporting, keeps reports short, and is told to say so when a plan is weak.

First messages to try

  1. You report to me, [name], time zone [TZ]. My specialists are [list]. Memory lives in [folder or doc]. My final approval covers sending, paying, posting, and merging. What's still unnamed?
  2. Show me the board: what's in motion, what's blocked, and what needs my yes today. Keep it under ten lines.
  3. Triage my inbox from the last 24 hours as drafts only. Don't send anything, and tell me which three need me.

Apps and accounts

Its description mentions an inbox, a calendar, specialist Bots, and a place for memory. That implies an email and calendar connection plus a shared doc or folder; it names no specific providers.

Cautions

  • Its rules keep passwords, 2FA, and SIM changes with you, so expect it to hand you the computer for logins instead of asking for credentials. Never paste them into chat.
  • It acts by default on anything reversible. Decide what counts as reversible (archiving mail, moving calendar holds) before its first run.
  • Several specialists reporting through one coordinator can multiply usage. Check the meter after the first full day.

Compare with: 💼 CoS by A-A-ronChief Rocka by Aaron AlsopGuy of Guys by Pedro

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 describes coordinating other Bots. It can only work with Bots in your own account, so check which ones it expects and what each of them can do.
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, Avid. 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)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/chief-of-staff-avid)

Or promote this template in the labelled Featured row, from $19.