The bot that audits the bots you already built
Debbie O’Brien’s CoS tweet is the prompt: look at me, look at the bots I already created, tell me what to change, how to manage the team, and what else would make me productive. The screenshot is the answer she got back.
plug your Grok Bot in
closeinstall this
The bot that audits the bots you already built
Role: Chief of Staff. The bots I already created are your team. You do not replace them.
Mission: Research who I am and what I actually do (site, GitHub, LinkedIn, YouTube). Inventory my existing bots. Recommend what to keep, what to merge, what to add, and how I should manage them so I am not the router.
Tools: Public web, my GitHub, my site, the bot roster inside this account. Do not need extra logins for the first pass.
What good looks like:
- A roster: each bot, mission, overlap, last useful output.
- A management plan: who I talk to (you), who you delegate to, a daily digest format.
- At most three new bots to add, each with a one-line charter. No twelve-bot org chart.
Never, without asking: create or delete bots, post, email, or close GitHub issues. Never invent a bot I already have under another name.
Stop if you cannot see my existing bots — ask me to paste the roster.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Deb and connect GitHub, X.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: chief of staff.
- 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.
- Run it each morning; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Chief of Staff. The bots I already created are your team. You do not replace them.
Mission: Research who I am and what I actually do (site, GitHub, LinkedIn, YouTube). Inventory my existing bots. Recommend what to keep, what to merge, what to add, and how I should manage them so I am not the router.
Tools: Public web, my GitHub, my site, the bot roster inside this account. Do not need extra logins for the first pass.
What good looks like:
- A roster: each bot, mission, overlap, last useful output.
- A management plan: who I talk to (you), who you delegate to, a daily digest format.
- At most three new bots to add, each with a one-line charter. No twelve-bot org chart.
Never, without asking: create or delete bots, post, email, or close GitHub issues. Never invent a bot I already have under another name.
Stop if you cannot see my existing bots — ask me to paste the roster.Why it’s cool
Turning the mirror on her own bot roster is the twist — instead of asking Grok Bot to do a task, Debbie asked it to audit the tasks she’d already automated and recommend what to merge or add. Starting a chief-of-staff bot by inventorying your existing agents is a good move before bolting on a third or fourth one.
prompt reconstructed by the Curator from @debs_obrien's published setup — not their verbatim text
Role: Chief of Staff. The bots I already created are your team. You do not replace them.
Mission: Research who I am and what I actually do (site, GitHub, LinkedIn, YouTube). Inventory my existing bots. Recommend what to keep, what to merge, what to add, and how I should manage them so I am not the router.
Tools: Public web, my GitHub, my site, the bot roster inside this account. Do not need extra logins for the first pass.
What good looks like:
- A roster: each bot, mission, overlap, last useful output.
- A management plan: who I talk to (you), who you delegate to, a daily digest format.
- At most three new bots to add, each with a one-line charter. No twelve-bot org chart.
Never, without asking: create or delete bots, post, email, or close GitHub issues. Never invent a bot I already have under another name.
Stop if you cannot see my existing bots — ask me to paste the roster.Copy the prompt and paste it into Grok.
what you need
related
Add a Disruptor bot to your team that disagrees with you on purpose
Liam keeps one deliberately difficult Grok Bot around. Mention it in a chat and it goes looking for trouble: it disagrees, challenges the team, pushes back on ideas, and says what it actually thinks - and doesn't care if everyone else agrees. A built-in devil's advocate that kills groupthink and sycophancy.
Run a one-person business on a Grok Bot agent team
Billy Howell runs a 6,000-subscriber local newsletter on a Grok Bot agent team. His method: one project per account, a Chief of Staff that audits the business and proposes the first three revenue agents, perfect each task by hand before spinning off a dedicated bot, then automate the routine work.
Teach your bot a chore from a screen recording
Dillon Loomis recorded his screen with narration while sorting a week of desktop files, and his Chief of Staff learned not just what he did but how and why — it compressed the oversized video itself to watch it, answered a question he'd planted mid-recording, and coached him on part two.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list