Independent guide to useful Bots · Across platforms
Bot Cabinet
Hermes profiles · Grok Bot build briefs

One Bot job. Two ways to build it

Choose a job and follow its Grok Bot setup instructions. Each brief includes the role, a first task, review checks, and proposed Skills and Routines. Hermes profiles are available separately.

Choose a Bot Read the official Grok Bot guide
Hermes AgentDownloadable profile
Grok BotManual setup · not yet tested

Create the Bot in Grok Bot and copy the instructions from its brief. These downloads are not native template links. Bot Cabinet has not tested these setups in the app.

Source review · September 20, 2026 · Not runtime-tested

Find an existing template

Grok Bot now has an official marketplace and native template links. Browse for the job you need before creating a Bot yourself. Cabinet's downloads here remain manual build briefs, not native templates.

Inspect the setup before adding it

xAI's September 8 guide describes templates as reusable recipes. Review included context and integrations. Plugins may need setup; custom scripts and non-standard integrations may need separate transfer. Start with sample data and check the result before connecting sensitive accounts.

Read what native templates include and omit
Use a Bot in another app

Choose the setup for your app

Each app needs its own setup. The instructions describe the job; you connect the tools and check the result.

Bot instructions

The job and setup checklist

  • Job, scope, and intended result
  • Role instructions, approval rules, and limits
  • A first task and checks for the answer
  • Skill and Routine recipes
Platform setup

Use the format the platform supports

  • Hermes: download and inspect the prepared profile
  • Grok Bot: create the Bot from the build brief
  • Connect only the tools the job needs
  • Test before adding a Skill, Routine, or public link
Operator guide · Checked September 24, 2026

Set up, test, and manage Grok Bots

A practical reference for choosing a Bot, saving a Skill, adding a Routine, protecting account access and handing work between Bots.

Download the PDF
01

Choose a Bot, Skill or Routine

  • Use a Bot for one ongoing job, with its own instructions and history.
  • Use a Skill for a method you want to repeat.
  • Use a Routine only when a tested method needs a schedule or event trigger.
  • Do the task once, correct it, save the method, then automate it.
02

Tell the Bot what to make

  • Say which sources to use, what answer or file to make, what it must not do, and when to ask for review.
  • Send a new message when you need to redirect work already in progress.
  • Stop ends the current work; it does not undo actions already completed.
  • Review drafts before sending, publishing, purchasing, deleting or changing production systems.
03

Protect accounts and files

  • Take control of the computer for passwords, passkeys, two-factor codes, CAPTCHAs and payment confirmation.
  • Never paste passwords or one-time codes into ordinary chat.
  • All of your Bots share one cloud computer, including its files, browser sessions and logins.
  • Connect only what the job needs. Set Ask first rules for sending, spending, publishing, deleting or changing account access.
04

Add a Routine carefully

  • Confirm which Bot runs it, when it runs, its time zone, what it reads and makes, when it asks for approval, and what it does if a source is missing.
  • A test run performs real work. Use safe inputs and keep write actions behind approval.
  • A Bot can own up to 50 routines. Grok Bot keeps the 20 most recent run records for each routine.
  • Pause a Routine when its website, connector or source format changes.
05

Use a group only when it helps

  • A group chat can include two to six Bots.
  • Give the group one goal and name the Bot responsible for the next step.
  • Use separate Bots for different roles or an independent check. They still share one computer and its files and logins.
  • At each handoff, tell the next Bot what to do, which sources to use, what to make, what to avoid, and when to ask for review.
06

Fix the smallest failing part

  • If a Routine misses a run, check whether it is enabled, who owns it, its time zone, its source and its run history.
  • If a private Skill is missing, check Marketplace, then Your plugins, then Manage plugins and skills.
  • If computer work stalls, retry the step before rebuilding the computer.
  • Change one instruction, rerun the same safe test, and save both answers so you can compare them.
Useful shortcuts
Cmd/Ctrl+K
Search or open the command palette
Cmd/Ctrl+N
Start a new Bot or chat
Cmd/Ctrl+F
Find in the current chat
Cmd/Ctrl+B
Compact the sidebar
Cmd/Ctrl+Shift+F
Search Bots
/
Choose a Skill
@
Mention a Bot, group, Routine or connector
Five-line handoff

Outcome · Sources · Constraints · Deliverable · Review point

Bot Cabinet is independent and is not affiliated with xAI or Cursor. Product behavior can change. Check the current documentation before connecting sensitive accounts or allowing consequential actions.
Grok Bot overview Skills and Routines Approvals, security and privacy Chat and collaboration Troubleshooting
20 practical starting points

Choose a job

Use these instructions to create a Bot manually in Grok Bot. App testing is still pending.

Before you share

What a Grok Bot public link includes

Grok Bot can publish a preview link after you build and test a Bot. Another person can inspect that page and add a copy to their own account.

The shared configuration

The public preview can include the Bot's identity, description, Skills, and Routines. Remove secrets, customer information, and internal links before sharing.

The recipient gets a copy

Your computer access, logins, and conversation history stay with your account.

Your Bots share one computer

Bots on the same Grok account share its cloud computer, files, browser sessions, and sign-ins. Treat that access as available to every Bot in your roster.

Create and share Bots Skills and Routines Approvals, security, and privacy