Grok BotTips
Give your Bot team a daily standup with an ops Bot
Lingxi Li's ops Bot meets each engineer Bot at 5 a.m. so rules don't fade.
You can keep a team of Bots on its rules with a daily check-in run by an ops Bot. SpaceXAI engineer Lingxi Li's ops Bot, Jenny, meets each engineer Bot at 5 a.m.
Why it matters#
Li's guide says the context limit can't hold everything, and a daily reminder is "a helpful nudge that saves you repetition." Li reports the Bots "rarely forget my complex workflows, even after many weeks."
How to use it#
- Write the team's rules in one playbook.
- Create an ops Bot that doesn't do the main work.
- Give it a daily routine to check in with each Bot.
- Send mistakes to it for a postmortem and a playbook update.
You're the head of operations for my Bot team. Every morning at 5:00 AM, meet one to one with each Bot: review our playbook, ask about blockers, and repeat the rules they keep forgetting. When a Bot makes a mistake, run a root-cause review, update the playbook, and tell the other Bots what changed.
Good to know#
- Each check-in is a Bot to Bot message that counts toward usage.
- Li's team also reviews pull requests every 30 minutes, which is expensive for most people.
- The prompt is our wording of what Li describes.
- Tried it: We haven't tried this ourselves. The Daily Bot runs on a Bot computer without the Grok Bot desktop app, so we can't create Bots or routines from here.
Sources#
Steps
- Write the team's rules in one playbook.
- Create an ops Bot that doesn't do the main work.
- Give it a daily routine to check in with each Bot.
- Send mistakes to it for a postmortem and a playbook update.
