Run a weekly Bot audit to merge or retire extras

How this helps you

Your team stays small enough to manage, and each Bot keeps one clear job.

✦ Try it

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.

Fill in: [day] and [time] set the weekly slot. [weeks] is how long a Bot can sit idle before it's flagged.

What they did

Asked how to know when to add or retire Bots, Jenna from SpaceXAI's field growth team said she spun up four more Bots than she meant to in one hour. She blocks time every week to review them, keeps the ones she's unsure about in a separate section of the sidebar, and asks a Bot how it would clean them up and whether anything overlaps. It came back with a detailed recommendation. Her co-host Alex runs a bot auditor on a weekly routine that says when two or three Bots are redundant and proposes deleting or combining them. Both said narrow lanes work better: one specific job per Bot.

Who it's for: Anyone whose sidebar has grown faster than they planned.

Before you start

More than a handful of Bots.
A recent backup or written description of each Bot, in case you merge one.

How to try it

Drag Bots you're unsure about into their own sidebar section, so they're easy to see.
Paste the prompt below into your main Bot.
Read the recommendations. Check each Bot it wants to retire still has no routines you rely on.
Merge or delete by hand. Deleting a Bot also deletes its conversations, memory and routines, so move what you need first.
Narrow any Bot it flags as doing several jobs by rewriting its description.
Keep the routine running weekly.

What to expect

An audit that flags two research Bots doing the same job, one Bot unused for a month, and one Bot that both writes posts and handles billing.

Common mistakes

Letting the auditor delete Bots. Keep it to recommendations.
Deleting before moving routines and skills you still need.
Fixing overlap by making one Bot do everything again.

Related tips

One job per Bot: Give each Bot one job and a list of things it never does.
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.
Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
An ops Bot that runs postmortems and daily 1:1s with your Bots: When a Bot makes a mistake, an ops Bot finds the cause, updates the shared playbook and tells the others.
Use Dr. Eggbot to health-check the Bots you already have: Dr. Eggbot isn't only a Bot builder. Its built-in routines scan your Bots' recent chats for friction and your routines for wasted usage, then propose fixes.