Learn

Your first hour after you add a Bot

You added a recipe, or you created a Bot and gave it a job. The first hour is for reading what landed and running one small task. It is not the hour to turn on a schedule.

1. Confirm you actually added a Bot

Copying a prompt on bot.ski does not add a Bot. The template preview’s add control does, once the Grok Bot app finishes the copy. If you only have text on the clipboard, go to Add, import, and copy prompt before you follow the rest of this list.

If the link you used might be old, stop and read when a share link is stale. Read the details on the preview you opened. Do not invent an id.

2. Read what landed

A template copy brings identity, description, skills, and routines. It does not bring the other person’s computer, logins, or conversation history. Open the description and look for sends, spends, deletes, and public posts. Put a missing boundary in the description, not only in one chat message. Anti-jobs and what to ask first is the longer page.

3. It joins your computer

The cloud computer belongs to your account. Every Bot you run, including the one you just added, can use its files, browser sessions, and command-line credentials.

The new Bot does not get a private machine. A separate chat or a separate screen is not a separate vault.

Connectors you install are account-wide too. Do not sign a client into that browser if another Bot on the account should not see the session. Details: Shared computer security for beginners.

4. One small task, then stop

A clear first request names:

The outcome
The sources
What it must not do
What it should hand back
When it should stop for you

A five-minute start that needs no website login: attach a document and ask for a short summary, a list of dates and open questions, and a citation for each item. Tell it not to change the file.

If a site asks for a password, a code, or a CAPTCHA, take over Agent Computer and type it there. Do not paste passwords into the chat.

5. Do not schedule it yet

A skill is how to do a task, and private skills are one library your Bots share. A routine tells one Bot when to run, and it can keep going after you close the laptop. A test run performs real work.

Watch one successful task first. Save a skill only when the pattern is stable. Create a routine after that, and read how to put your bot on a schedule.

Sources

Fetched 2026-09-23 CT.

Get started
https://docs.x.ai/grok-bot/get-started
Fetched 2026-09-23 CT.
A strong first task names the stop point
Create and manage Bots
https://docs.x.ai/grok-bot/bots
Fetched 2026-09-23 CT.
What a shared copy includes
Official computer and apps
https://docs.x.ai/grok-bot/computer-and-apps
Fetched 2026-09-23 CT.
The new Bot uses the account computer
Skills and routines
https://docs.x.ai/grok-bot/skills-routines-and-automations
Fetched 2026-09-23 CT.
Test before a routine; a test run does real work