Grok Bot multi-bot setups

Remember these as standing rules whenever you talk to other Bots: 1) Never reply to messages that only say got it, thanks, okay or on it. 2) Send one message per task or finished result. 3) End every handoff with: No reply needed. 4) Batch updates into one summary instead of several messages. 5) If three back-and-forth messages pass with no new work, stop and tell me.

From now on, whenever a task needs [client exposure and positions], don't work it out yourself. Message the [Exposure and Positions] Team Bot, ask it for the verified numbers, and use only what it returns. Show me which Bot the numbers came from. If it can't answer, tell me instead of estimating.

Find the [5] biggest stories about [topic] from the past week. Verify each one against the primary source and flag any claim that doesn't hold up. Rank them by [what matters to me], and save a briefing file called [file name] with a one-line hook and the source link for each. Do the checks in Chrome so I can watch.

Read this guide and help me improve my Bot team: [paste the guide or link]. First, here's a brain dump of who I am and the work I do: [voice note or notes]. Restate it in your own words so I can confirm you understood. Then list: the Bots I have and whether any should be merged, the copy-paste steps you could take over and what access you'd need, and three skills you should write for yourself from what I've told you. Don't create or delete any Bot until I say yes.

For anything more than a short question, don't write the code yourself. Hand it to a coding agent with an acceptance test. Check the proof. Open a pull request and report back. Never merge. When I correct an agent, propose where the fix belongs: code first, then a lint rule, then a rules file, with review last.

I'm promoting you to director of [area]. Build three new Bots that report to you: one to [job 1], one to [job 2], and one to [job 3]. They report directly to you, never to me. Ask each for proof of work and source links. Send me only what I need to know once a week on [day] morning, unless something is extremely urgent.

Before I publish this template, list every rule, memory, skill and routine it includes, and quote any line that mentions a person, client, email address, account, price or internal link. Suggest a neutral replacement for each one.

Turn on your health check routines and run them now across all my Bots: look at recent chats for places where I had to repeat myself or correct a Bot, and at routines that use a lot of usage for little result. For each Bot, propose specific fixes (a skill, a rule, a routine change) and the reason. Don't apply anything until I pick which ones.

Here is my old AI agent setup: [folder or repo]. Go through it one role at a time with me. For each agent, propose: keep as its own Bot, merge into another, or turn into a shared skill. For every Bot you propose, give its one-sentence job and what it must never do. Don't create anything until I approve each one.

Create a group chat called Daily standup with [Bot names]. Then set up a routine every weekday at [time]: ask the group what each Bot is working on today, what's due, and anything blocked or waiting on me. Summarise it in three lines for me at the end.

Make a team Bot copy of yourself for my team. List the skills and connections the copy will have, and anything that will not carry over.

Every weekday at 10am, look through [channels] for requests that should have come to you but did not tag you, and list them for me before acting.

I'm thinking of creating a new Bot for [job]. Check it against three tests. One: does it need its own memory, so its notes would clutter yours? Two: does it need different permissions from you, such as read-only access? Three: does it need its own schedule or trigger? If none apply, tell me how you'd handle it yourself as a skill or routine. If one applies, say which, and draft a one-line job description for the new Bot. Don't create anything yet.

Every [day] at [time], review all my Bots: their name, job, routines and when each was last used. Tell me which overlap, which haven't been used in [weeks] weeks, and which do more than one job. Propose what to merge, narrow or retire, with a reason for each. Don't delete, pause or change any Bot yourself.

Write a skill called [loop name]: ask [metrics Bot] for the last 24 hours of [metric] per [item], pick the bottom [3] (if tied, pick at random so it's exactly [3]), ask [designer Bot] for [3] replacements, ask [builder Bot] to swap them in and deploy, then send me a short brief of what changed.

Help me with [one thing]. Go one step at a time, wait for me after each step, and if a message looks like a scam, tell me why before I reply.

Document every Bot's job, rules, memory, skills and routines into a recovery doc in my Drive. Include a table of connections but no passwords or keys. Add a rebuild order where routines are recreated paused. Then set up a monthly routine to keep it current.

Rewrite your description around one job. Add a short list of things you never do, and which of my Bots handles each of those instead. Show me the draft before you save it.

You are my lead researcher. Every [interval], take the next [number] entries from [target list] and look for [buying signal] there. For each one, find the decision maker's name and work email from public sources. Hand each lead to @[writing Bot], who writes a short, personal first email as a draft in [email account]. Never send anything. Rules: one named recipient per email; if one person has several opportunities, cover them in one email; skip anyone we've emailed before; check my calendar and skip anything that falls in [busy weeks].

I want to make you my main Bot. Then tell me what each of my other Bots is working on and which ones you would hand work to.

You are my executive assistant. You own my day-to-day ops: [email triage, scheduling, small research jobs]. Ask me before you send, buy or delete anything. What do you need to know about me to start?

Do we have any outstanding invoices? If so, agree between you who does what to get them paid, and post the plan here before contacting any client.

Find a Bot template for [job] in the Grok Bot Marketplace and link it. Tell me what it does, which apps it needs, and which routines it will run, before I add it.

Rewrite your description: you are my [team] lead. You never do the work yourself. You break each request into small tasks, hand them to [Bot A], [Bot B] and [Bot C], check what comes back against the goal, and report to me. For big projects, write the plan in a [Notion] doc first and wait for my OK.

You are the operations Bot for [team]. You don't do project work. Every day at [time], check in with each of [Bots]: ask what they're working on, what is blocked, and whether they're following [playbook]. Send me a short summary of blockers only. When a Bot is sent to you after a mistake, find the root cause in its reasoning, propose a playbook change, and after I approve it, tell every Bot what changed.

Write a Project Ops skill for yourself. When I start a project: add it to my Notion Projects database, open a group chat named after it, and propose a roster. Reuse my existing Bots first, propose at most [5] Bots besides you, and only suggest a new Bot if nothing fits, after I say yes. Track tasks in my Tasks database. If a Bot gets stuck, it marks the task Blocked and pings me in the channel.

You are my chief of staff. When I ask for something, decide which of my Bots should do it, hand it over, and give me one short summary when it is done.