Shoopy @0xShoopy ·
Grok Bot: how to build an AI crew that learns by watching you work
Grok Bot: how to build an AI crew that learns by watching you work
What you need
- Connected apps
- Gmail first, then Google Calendar, then Drive or Slack, one tool at a time.
- Routines
- Weekday schedules for recorded tasks, plus a Friday audit.
- Skills
- Skills the bots save for themselves, such as “File a receipt”.
What prompted it
Writing a prompt for a task that spans several apps takes longer than doing the task, and handing a bot too much too early makes it impossible to tell skill from luck.
What Grok Bot did
- Start with a small daily errand you can check in 30 seconds. The Chief bot read the inbox and sorted the threads without changing anything.
- Show the bot a task once instead of describing it. It names the task, breaks it into steps and turns the parts that change into settings.
- Give each bot a four-paragraph charter, including what to do when unsure, and a name that sounds like a job.
- Connect one tool at a time, since every bot on the account shares the connections.
- When a bot reaches a login, it hands you the screen; you sign in and it carries on.
- Let bots do anything reversible and stop at anything that sends, spends or deletes.
- Schedule routines with a volume limit, send held decisions to one approval thread, and audit every routine on Fridays.
Evidence and limits
- Original post checked on X (Oct 18, 2026)
- Outcome reported by the author
- Not reproduced by anyone else yet
- Write a kill condition for every routine before it causes a problem.
- Turn off routines nobody would miss; the author says about half end up that way.
