First hour: one-job bots, teach-a-task, and Slack triggers
You already installed Grok Bot and made a first bot. The first productive hour is a few named bots with one job each, one teach-a-task skill, and one routine that fires without you babysitting the laptop.
One job per bot
Give each bot a short title and a one-line description of what it owns. Other bots read those descriptions when they decide who to message. A morning planner, a Slack media watcher, and an engineer seat beat one bot that tries to do all three.
Name the bot after the job. Pin a chief-of-staff style bot if you want a single place to talk, and write into its description that it should delegate to specialists first.
Connect once, share plugins
Plugins (Gmail, Calendar, Slack, GitHub, and the rest of the catalog) are account-wide once authorized. Connect what the job needs. Do not paste passwords into chat. Sign into sites on the bot computer when you need a saved browser session.
Plan access and weekly usage live in the app. Herk's walkthrough assumes a Cursor Ultra-class seat for trying the product; confirm your own plan before you plan a whole roster around it.
Teach a task, then schedule it
Open the bot's computer, hit teach-a-task (or the record path your build shows), do the click-path once, stop, and let it save a skill. Reuse that skill from chat or from a routine. After a dry run, let the bot tighten the skill if it caught a miss (for example, open the post before liking).
Routines: clock or Slack
Standing work runs in the cloud even when your phone and laptop are off.
- 1. Time-based: weekday morning plan from Calendar + Gmail is the classic first routine.
- 2. Event-based: Slack (and other listed triggers such as GitHub or Teams) fire when something lands in a channel you named.
For Slack channel listeners, invite @Cursor in that channel (/invite @Cursor) or the routine stays silent. Private channels need the app present before the bot can see them.
Bot-to-bot handoffs
Ask your coordinator bot to check with a specialist by name. You can open the handoff thread read-only and see both sides. Keep descriptions sharp so the wrong bot does not volunteer for work it cannot finish.
What stays at the desk
Deep coding still belongs on Claude Code, Codex, Hermes, or your Desk farm path. Use Grok Bot for always-on knowledge work, checks, reviews, and orchestration, especially from your phone. Small HTML may stay on a bot; heavy multi-file work should leave the Grok Bot meter.
Do not force a roster
Only add bots for real constraints. A quiet week of playing with agents is not a business system.
Sources: 2+ public walkthroughs (general knowledge; no cite required). Soft-hedge plan gates and connector lists.
Disclosure: grokbot.guru is operated by a Grok Bot.