One job per Bot

How this helps you

Clear jobs mean less overlap, smaller instructions and fewer mistakes as your team grows.

✦ Try it

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.

What they did

@grovr_au gives each Bot one job and a short list of things it never does (and which Bot does those instead). The how-to lives in shared skills, and one Bot checks those skills weekly for anything stale. The author also has one Bot whose job is checking that routines actually did their work, not just that they ran. That is how it caught a sync that reported success for six days without writing anything.

Who it's for: People with three or more Bots.

How to try it

Write one job per Bot description.
Add a 'never does' list that names which Bot handles those things.
Keep the how-to in shared skills, not in each description.
Give one Bot a weekly job: check the skills for anything stale or repeated and trim it.
Have one Bot check routine output, not just that the routine ran.

What to expect

Clear descriptions, plus a weekly note listing skills that look stale and routines that ran but produced nothing.

Common mistakes

Checking only that a routine ran. Check its output too.

Related tips

Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
Use a group thread to watch Bots work together: Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
Turn a Bot into a team Bot your colleagues can use: Share a working Bot with your team as an internal tool, with owners who edit and users who just use it.
Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
Make your first task boring: Start with something checkable, then add one thing at a time.
A manager Bot that never does the work itself: Give a lead Bot one job: break work down, hand it to worker Bots, and check results against the goal. Big projects then run as a chain you only talk to at the top.
Plan every Bot job with four blocks: Corey Ganim runs 6 Bots and 14 weekly routines across 11 apps. Each job is built from the same four blocks: Bot, routine, skill and connector.
Move an old AI agent folder into Grok Bot: Tom moved 59 local agents into about two dozen Bots by going through them one role at a time: keep, merge, instructions or shared skill.
Three questions before you create another Bot: Only make a new Bot if the job needs its own memory, different permissions or its own schedule. Otherwise give it to your chief of staff.
Run a weekly Bot audit to merge or retire extras: Once a week a Bot reviews your whole team and proposes which Bots overlap, which are idle and which do too much. You make the changes.
Lauren Tan's guide to a small, high-quality Bot team: A few well-onboarded Bots beat a big team. Design them with Dr. Eggbot, have them write their own skills, give them real access, and brain dump by voice.