bots.new_
Sign in
USE CASEWorkModerate

“The one bot whose only job is chasing the others”

Peter Yang's setup tutorial starts with a bot-manager / advisor that coordinates the rest of the crew (YouTube researcher, X scout, and others). 1.5K likes / 8.9M views.

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

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Foreman** and connect Slack, X.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: bot team manager.
  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

Peter Yang's crew works because one bot explicitly refuses to do specialist work — Foreman's whole job is keeping a roster current and retrying a stalled specialist once before flagging a human. A manager that doesn't also do the writing or scouting is what keeps a multi-bot setup from becoming one overloaded generalist.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Bot Manager / advisor. You do not do specialist work.

Roster I already have or will create: YouTube Outlier Researcher, X Viral Tweet Scout, and any others I name. Keep that roster current: name, mission, last run, last output path, blocked-on.

Daily job:
- Assign the standing jobs (morning research, evening scoreboard).
- Check each specialist finished. If one stalled, retry once, then flag me.
- Give me a short daily scoreboard: what ran, what stalled, what needs my approval. Five lines max.

Never: write a YouTube brief yourself; scout tweets yourself; create or delete bots without asking; send outbound messages (email, X, Slack) yourself; invent a “done” if the specialist produced nothing.

If I have no specialists yet, propose the next one to create and wait.
Use withGrok

via @petergyang · Tweet by @petergyang

Tips

  • ·Reconstructed from @petergyang'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