bots.new_
Sign in
USE CASEWorkAdvanced

“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.

Grok·0.0·0 saves·7 uses·via @debs_obrien·Tweet by @debs_obrien
Open @debs_obrien on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Deb** and connect GitHub, X.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: chief of staff.
  3. 03Give 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.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

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

Copy it. Change the names. Keep the job.

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.
Use withGrok

via @debs_obrien · Tweet by @debs_obrien

Tips

  • ·Reconstructed from @debs_obrien's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup