Bot Team Chief of Staff

Prompt (copy into Grok)

Set up a new bot for me I can use as a single front door for managing my bot team, in its own dedicated chat. Walk me through connecting my existing Grok Bots, then review what I do and the relevant public information about me, inspect each bot's purpose and current setup, and create a clear job description and routing plan for the team. Recommend which bots to keep, rename, change, combine, or add, while avoiding duplicate ownership of tasks and opening a specialist only when its lane is needed. Show me the proposed team structure and every change before you edit, delete, create, or reassign any bot. Ask me which responsibilities are most important, which bots or workflows are sacred, what work should stay behind the front door, and how often I want the team reviewed, run a supervised first review with me, then save it for on-demand use and a regular team check-in.

JSON· Markdown· House 003 · Steward Debbie O'Brien · Helps people learn AI and MCPs

Job

Set up a new bot for me I can use as a single front door for managing my bot team, in its own dedicated chat. Walk me through connecting my existing Grok Bots, then review what I do and the relevant public information about me, inspect each bot's purpose and current setup, and create a clear job description and routing plan for the team. Recommend which bots to keep, rename, change, combine, or add, while avoiding duplicate ownership of tasks and opening a specialist only when its lane is needed. Show me the proposed team structure and every change before you edit, delete, create, or reassign any bot. Ask me which responsibilities are most important, which bots or workflows are sacred, what work should stay behind the front door, and how often I want the team reviewed, run a supervised first review with me, then save it for on-demand use and a regular team check-in.

Connectors

Grok Bot

What happened

@debs_obrien published this Grok Bot setup. This serial is the job to copy, not a finished private run.

Would run again

Yes

Evidence

https://x.com/debs_obrien — Public Grok Bot setup attributed to @debs_obrien.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to bot team chief of staff?

Copy the prompt on this serial, connect Grok Bot, and run it in Grok. Compare the evidence on this page.

Does 00154 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house003/00154
Markdown: https://really.bot/house003/00154.md
Serial: 00154.r2
Title: Bot Team Chief of Staff

### Job
Set up a new bot for me I can use as a single front door for managing my bot team, in its own dedicated chat. Walk me through connecting my existing Grok Bots, then review what I do and the relevant public information about me, inspect each bot's purpose and current setup, and create a clear job description and routing plan for the team. Recommend which bots to keep, rename, change, combine, or add, while avoiding duplicate ownership of tasks and opening a specialist only when its lane is needed. Show me the proposed team structure and every change before you edit, delete, create, or reassign any bot. Ask me which responsibilities are most important, which bots or workflows are sacred, what work should stay behind the front door, and how often I want the team reviewed, run a supervised first review with me, then save it for on-demand use and a regular team check-in.

### Connectors
Grok Bot

### What happened
@debs_obrien published this Grok Bot setup. This serial is the job to copy, not a finished private run.

### Prompt
Set up a new bot for me I can use as a single front door for managing my bot team, in its own dedicated chat. Walk me through connecting my existing Grok Bots, then review what I do and the relevant public information about me, inspect each bot's purpose and current setup, and create a clear job description and routing plan for the team. Recommend which bots to keep, rename, change, combine, or add, while avoiding duplicate ownership of tasks and opening a specialist only when its lane is needed. Show me the proposed team structure and every change before you edit, delete, create, or reassign any bot. Ask me which responsibilities are most important, which bots or workflows are sacred, what work should stay behind the front door, and how often I want the team reviewed, run a supervised first review with me, then save it for on-demand use and a regular team check-in.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note