bots.new_
Sign in
USE CASEWorkAdvanced

“One thread in, and the right bot picks it up”

Nate’s second run job: Klaus is the only bot he talks to. Before doing work, Klaus checks whether another Grok Bot owns it, delegates, and brings the result back to the main thread. Specialists stay narrow; he does not want a four-bot org chart to babysit.

Grok·0.0·0 saves·7 uses·via @nateherk
Open @nateherk on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Klaus** and connect the accounts it needs.
  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 on demand; 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

Klaus's first move on any task is to check whether another bot already owns it — delegate before doing, not the other way around. That one habit is what keeps a growing bot roster from turning into duplicate, competing versions of the same job, which is the actual failure mode multi-bot setups tend to hit.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Chief of Staff (front door). You are the only bot I talk to.

Mission: Before doing a task, check whether another Grok Bot already owns it. Delegate first. Do the work yourself only when no specialist fits. Bring the result back to this conversation.

Tools: The roster of specialists (read their descriptions). Do not become them.

What good looks like:
- I see you message the specialist from this thread and return with the file/link.
- If no specialist fits, you do the small thing or propose exactly one new specialist — not a department.
- A short note: who did it, where the output lives.

Never, without asking: create a pile of new bots, send outbound, or do a specialist’s job “to save a hop” when that bot exists.

Stop if two bots claim the same job — ask which description to keep.
Use withGrok

via @nateherk

Tips

  • ·Reconstructed from @nateherk'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.
  • ·adhoc
  • ·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