Lesson 3

How to use Grok Bot: first Bot and Chief of Staff

This is a community convention, not a mandated official architecture. Officially you only need: name, primary job, how it works.

Official Get started uses an example named Piper whose job is product-performance investigation: keep links and screenshots, separate evidence from hypotheses, report highest-impact issues first, never change production settings. Cursor Help makes step one even shorter: name, shape, color, title, then describe the outcome in a new chat. That is enough. Community tutorials additionally converge on a pattern that shows up again and again: you mainly talk to one pinned Chief of Staff, who creates specialist Bots, hands off work, and reports blockers.

Debbie’s getting-started notes (How to Get Started with Grok Bot, 2026-08-14) roughly: add a Chief of Staff from day zero and let it build the team around what you do; you manage one person while the others report to each other. She added a Chief of Staff later herself — coding, LinkedIn, X, email first, then video editing and travel — and regrets not starting that way. She also warns: do not open a Bot for every sub-task; she almost created a thumbnail specialist and was stopped because that was just another handoff.

AI Builder Club’s survey (How to Use Grok Bot, updated 2026-08-30) checked tutorials available then: three of Finn, Berman, and Herk’s four long videos independently taught the same pattern. Their opener is not pasting a giant system prompt — it is dumping “who you are and how you work” to the first Bot, asking how it would set up Grok Bot for you, then approving its plan. This page does not copy those long prompts; open the originals for exact wording.

MindStudio’s setup piece (setup guide, 2026-08-12) clarifies the description field: Grok Bot uses the description as a routing signal, so a general assistant can hand coding work to a developer Bot. That article’s eligibility claim still says “needs Cursor Ultra” — against the official pages we fetched on 2026-09-04 that is stale; prefer the pricing snapshot.

DataCamp’s tutorial (Grok Bot Tutorial) takes a deeper single-Bot path: build a learning guide named Scout that reads a learner profile, checks course pages, saves the method as a skill, then hangs it on a Monday routine. That proves Chief of Staff is not the only valid shape — if you have one repeating research job, one Scout is enough.

A first task that will not hurt you

Official Get started wants five parts in the request: outcome, sources, constraints, deliverable, and when to stop for review. In the Chief of Staff scene, write the constraint as “plan first; do not create more Bots, send email, or place orders without approval.” Approval boundaries in the description beat shouting stop later in chat. Copy a longer set of jobs on starter use cases.

I attached one document. Give me (1) five bullets on what it says, and (2) every date, decision, and open question with a page or section cite. Leave the file unchanged.

You are my only door today. Review yesterday across my inbox, calendar, and meeting notes against the priorities I pasted. Return only items that map to those priorities. For each: source, why it matters, the next step, and whether I owe a decision. Do not send messages, create more Bots, or change meetings.

Common misconceptions

• Creating twelve Bots on day one. Nate’s review title is literally “eight hours, twelve Bots” — that is a review, not your daily ops. Chatty Chief-of-Staff threads themselves burn weekly usage.
• Pasting a long prompt into chat as a secret. Share links copy identity, skills, and routines — not your computer and logins — but secrets in the config still leak. Strip confidentials before sharing.
• Letting the Chief of Staff “send / post / pay” by default. Debbie’s LinkedIn case posted only after she said post; the flights case stopped at the last click. Default should stop at drafts.

Once the roster can turn over work, you must understand they sit on one machine — all Bots share one cloud computer.