# Grok Bot best practices > Give each Bot one job, prove a task before you automate it, keep approvals on consequential actions, and strip secrets before you share. Cited from official xAI and SpaceXAI docs. Updated: 2026-09-23 Official xAI docs already tell you how to keep a Grok Bot inside a job. This page collects that guidance. It is not extra Grokdex policy. ## Give each Bot one job [Create and manage Bots](https://docs.x.ai/grok-bot/bots) says to create a separate Bot when the work has a distinct goal, set of tools, working style, approval boundary, or recurring schedule. Start with the smallest useful roster. Add another Bot only when the specialist role is stable. Put standing rules in the description. Official example: "Never send external messages without approval." Put the day's work in the message. Official example: "Draft follow-ups for these twelve accounts." [Use cases](https://docs.x.ai/grok-bot/use-cases) says the best roles own a repeatable outcome, not a loose category of questions. Start with read-and-prepare work. Review the result. Then add approved actions or a routine. ## Do not treat Bots as a security boundary Every Bot on your account shares one cloud computer. Files, browser sessions, and command-line credentials are available across the roster. [Approvals, security, and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy) and the [Grok Bot Terms](https://x.ai/legal/grok-bot-terms) both say not to treat separate Bots as isolated security boundaries. Sign out of a service when it should no longer be available. Remove sensitive temporary files after the work is complete. Keep durable project files in `/workspace` with clear folders. That workspace path is in [Use the computer and apps](https://docs.x.ai/grok-bot/computer-and-apps). ## Keep consequential actions behind approval Tell the Bot which actions it can take and where it must stop. Official examples of explicit boundaries include sending messages, publishing, purchases, deleting or overwriting data, changing permissions, production changes, and accepting legal terms. An approval controls the proposed action. It does not reverse work already completed. Do not approve an action whose target or effect you cannot identify. On desktop, **Allow once** continues that action and **Deny** blocks it. **Always allow** can save a matching rule. On iPhone and Android the matching controls are **Approve once** and **Deny**. Those labels are in [Approvals, security, and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy). If Auto Review is on, open **Settings**, then **General**, then **Auto-review**. **Ask first** rules always stop matching actions for you. **Allow automatically** rules proceed only when review finds no other reason to stop. If both match, **Ask first** wins. Write narrow rules. Avoid "allow everything in the browser." The default for commands on your local Mac or Windows computer is **Ask every time**. Use **Never allowed** unless a Bot has a specific reason to work on local files. That setting does not stop the cloud computer. ## Prove the task, then save a skill, then schedule [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations) splits the work in two. A skill is how to do a task. A routine tells one Bot when to run, on a schedule or, where supported, after an event. Start with a one-time task. Make it reliable. Save the method as a skill. Only then automate it. A useful skill states when to use it, required inputs, the sequence, how to validate, what to return, and what requires approval. When **Teach a task** is available, you can record a browser workflow from the computer view for up to ten minutes. It does not record microphone audio. The learned skill is a draft. Add decision rules and approval boundaries that one demo may miss. If the control is not visible, ask the Bot to create a skill from written instructions. The [FAQ](https://docs.x.ai/grok-bot/faq) says that rollout may be gradual. Use **Test run** after creating or editing a routine. A test run performs real work. It can navigate websites, change files, and call connected tools. Use safe inputs. Keep write actions behind approval. Include a no-data and stale-data policy. A Bot can own up to 50 routines. Deleting a routine has no undo. ## Ask for evidence you can check [Files and results](https://docs.x.ai/grok-bot/files-and-results) says a strong result should be independently reviewable. Ask for source links, screenshots, timestamps, file names, a short action log, and an explicit list of anything the Bot could not verify. For consequential work, ask it to separate facts, assumptions, completed actions, actions waiting for approval, and unresolved questions. For important decisions, ask the Bot to check the current source rather than relying on memory. That warning is in the [FAQ](https://docs.x.ai/grok-bot/faq) and [Create and manage Bots](https://docs.x.ai/grok-bot/bots). ## Strip secrets before you share Official [Share a Bot](https://docs.x.ai/grok-bot/bots#share-a-bot) says the public link lets anyone view the Bot's shared configuration, including identity, description, skills, and routines. Remove API keys, internal URLs, customer data, and anything else you would not put in a public document. Adding a shared Bot creates a copy on the recipient's account. It does not give them your computer, logins, or conversation history. Shared Bots are created by other users, not by SpaceXAI. Adding one accepts the [third-party bot terms](https://x.ai/legal/bot-sharing-terms). SpaceXAI's [Templates for Grok Bot](https://x.ai/bot/guides/templates-for-grok-bot) describes a **Share as Template** flow. Clicking that button does not publish by itself. You then choose team or public, then publish, then copy the link. Treat a template as a recipe, not a clone. First-party plugins and skills can be included. Secrets and personal or private skills are not. Recipients may need to reinstall plugins. Custom MCP servers and scripts are not in the template. Review the details and integrations before you choose **Add Bot**. On Grokdex, paste only a public `https://x.ai/bot/…` link you are allowed to make public. See [How to list a Grok Bot on Grokdex](https://grokdex.net/guides/how-to-list). ## Sources - [Create and manage Bots](https://docs.x.ai/grok-bot/bots) - [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations) - [Approvals, security, and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy) - [Files and results](https://docs.x.ai/grok-bot/files-and-results) - [Use cases](https://docs.x.ai/grok-bot/use-cases) - [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq) - [Templates for Grok Bot](https://x.ai/bot/guides/templates-for-grok-bot) - [Grok Bot Terms](https://x.ai/legal/grok-bot-terms) - [Third-party bot terms](https://x.ai/legal/bot-sharing-terms) Grokdex is independent. It is not affiliated with xAI or SpaceXAI. ## Related - [All guides](https://grokdex.net/guides) - [How to use a Grok Bot](https://grokdex.net/guides/how-to-use-a-grok-bot) - [How to list a Grok Bot on Grokdex](https://grokdex.net/guides/how-to-list) - [How to publish a public share for Grokdex](https://grokdex.net/guides/how-to-publish-a-public-share)