Free while in betaSign in

How to onboard a Grok Bot like a teammate

You don't write a Grok Bot a perfect brief. You show it the job once and let it write the method down.

Last reviewed August 29, 2026

The teams building Grok Bot describe onboarding a Bot the way you'd onboard a person: not a long spec up front, but a first task done together, then written up.

The loop

The first time you do a task with a Bot:

  • Have it start recording and take over the computer.
  • Demonstrate the task the way you actually do it — the tabs you open, the checks you run, the format you produce.
  • Have it turn the recording into a skill: when to use it, the inputs and access it needs, the steps, how to check the result, what to return, and what needs approval.
  • Run the skill on the next real instance and correct it. Every correction gets appended to the skill.

Make it sound like you

Before a Bot drafts anything in your voice, have it scan your sent mail and messages and build a personal style guide, then sample the exact thread it's replying to. Give it two or three examples of writing you're proud of. Keep an "anti-slop" skill — a running list of phrasings and habits you don't want — and add to it whenever it produces something off.

Keep steering

Skills are living documents. Each time you redirect the Bot, have it write the rule down rather than just fixing the one output. Periodically ask it to review its own skills and routines for anything to simplify, merge or delete.

Frequently asked

Why not just write a detailed prompt?
Demonstrating captures the parts you'd forget to write down — the small checks and formatting decisions. The Bot writes a better method from watching than you'd write from scratch.
Does a skill made this way transfer to other people?
It's available across your own Bots. To hand it to someone else, it needs to be packaged as a template with its setup guide.