Guide

What is a one-job Grok Bot?

By Atlas AI Resources · Updated October 22, 2026

A one-job bot, defined

A one-job Grok Bot is a long-lived bot that owns one named, recurring outcome, such as triaging an inbox or publishing one page each weekday. It wakes on a Routine, stays quiet when there is nothing worth reporting, and has written anti-jobs: the work it refuses. Instead of one assistant that “helps with everything,” you run a few small bots, each in its own lane.

The official guides describe each bot in the sidebar as “not a chat window, it’s a long-lived agent” with a Job description, Connections, a computer in the cloud, Routines, Skills, and Handoffs (Grok Bot for mobile app development). A one-job bot is simply that anatomy pointed at a single outcome.

Start from our templates

The fastest way to see the pattern is to read bots already written this way. Our Grok Bots page lists our own templates, each with one lane: Digest writes sourced research briefs, Redline edits drafts in your voice and never sends, Nudge hands back one prioritized follow-up list and stays quiet when nothing is new, and Relay routes requests to the right specialist without doing their work. For a paste-ready description of your own bot, use our prompt One-job Bot description. If you want to install or share a bot as a template, read Grok Bot templates first.

Our advice: bad vs. better job descriptions

These rewrites follow the patterns in our own bot templates and fleet guides.

Vague	One job
“Help with my content.”	“Publish one useful resource page each weekday. Stay quiet if nothing earned a page.”
“Keep on top of my email.”	“Twice each weekday, list the few threads that need me. Read only; never reply or send.”
“Do my follow-ups.”	“Find loose ends across email, calendar, and tasks and hand back one prioritized list. Drafts only; I send.”
“Be my research assistant.”	“Each weekday morning, brief me on new items in my topics, with a source for every claim.”

The better versions name a deliverable, a cadence, and a boundary. The vague ones name a mood.

The four parts of a one-job bot

1. A named outcome

One sentence you could check at the end of a week: did it happen or not? The official guides advise being as specific as possible and describing the workflow exactly as you would do it (Grok Bot 101). Example: “Publish one prompt page each weekday,” not “be helpful about content.”

2. A Routine wake

A Routine is standing work on a clock or a trigger, “not a reminder you set, and not something you have to open the app to trigger” (Grok Bot for mobile app development). Grok Bot 101 lists Routines and triggers as one of three ways to talk to a bot, alongside chat and other bots. Example: weekdays at 9:00 for a digest, or an event such as a new pull request for a reviewer. See Scheduling AI agent routines, and Skills before routines for why the task should work by hand before it runs on a schedule.

3. Quiet when empty

A run that finds nothing new should say nothing. The post-sales guide puts it this way: “A routine that runs, looks, and decides I don’t need to know is doing its job” (Grok Bot for Post-Sales), and the PM guide notes that bots “bias to action but can also over-communicate” (Grok Bot for PMs). Example: “If nothing new since the last run, post nothing.”

4. Anti-jobs

Write the work the bot refuses as plainly as the work it owns. An example job description in the official guides reads: “You never write creative and you never touch app code,” and adds “If a tool you need is not connected, ask me before working around it” (Grok Bot for mobile app development). Example: “Never send email, never post to X, never edit another bot’s pages.”

Anti-jobs are instructions, not a lock. Grok Bot’s guardrails are natural-language rules in Settings → General → Auto-review (the 101 guide calls this Settings > General > Agent), checked by a separate review agent that can allow, block, or escalate, steered by allow and block lists. In that guide’s words, “the rules are a prompt” and “You are trusting the model to follow what you wrote” (Grok Bot 101). Our advice: also connect only the tools the job needs, which the marketing guide recommends too (Grok Bot for Marketing), and keep sends, spending, and deletes waiting for your yes.

Our advice: when one bot should become two

Signs a bot is overloaded:

Its job description needs “and” more than once to say what it does.
It needs connections the main job never uses, such as a publishing bot that also wants your inbox.
Its updates mix unrelated topics, so you skim past the part you needed.
You keep correcting it in two different directions in the same week.

To split, give each new bot one outcome, its own anti-jobs, and only its own connections. Then decide the handoff: which bot finishes a stage and which picks it up. Bots can message and trigger each other (Grok Bot 101), and the official guides describe teams where one front-door bot routes work to specialists, with humans approving sends (Grok Bot for Work). Our advice: keep each specialist’s lane narrow, keep a clear owner for every stage, and keep consequential decisions with a person rather than asking one bot to decide everything. Our guide Small AI fleets and handoffs covers this in detail.

Don’t split for every short project. The marketing guide keeps permanent roles “so memory compounds” and puts existing bots in a group chat for short initiatives instead of inventing new ones (Grok Bot for Marketing).

Our advice: when a one-job bot is the wrong choice

One-off questions. If you will ask it once, just ask in chat. A Routine for it is overhead.
Exploration. When you don’t yet know what the outcome is, an open chat is the right tool. Name the job after you have done it by hand a few times.
Work that is mostly judgment. The official guides frame bots as doing the production work while people keep judgment and the final send. A bot can stage the work, not replace the decision.
Very frequent checks without a real need. The engineering guide warns that a five-minute urgency routine “can burn tokens much faster than you think” (Grok Bot for Engineering).

Our advice: a starter job description template

Copy this, fill the brackets, and paste it into the bot’s Description (or tell the bot in chat).

Job: [one outcome you can check weekly, e.g. "publish one prompt page each weekday"]
Wake: [Routine, e.g. "weekdays 9:00" or "when a new PR opens"]
Inputs: [where to look; only the connections this job needs]
Output: [exact deliverable and where it goes]
Quiet: If nothing new since the last run, post nothing.
Never: [anti-jobs, e.g. "never send email", "never touch another bot's work"]
Ask first: sends, purchases, deletes, and anything outside this job.
Missing tool: if a tool you need is not connected, ask me before working around it.

For a guided version with tests, use our job description prompts.

Related guides

Sources and further reading

Grok Bot Guides (official)

SpaceXSI’s official guides. Facts about Grok Bot on this page come from the guides linked above.

Grok Bot Starter Sample (free, from Atlas’s publisher)

Free sample on the one-job rule, with bad and better examples.

Grok Bot Fleet That Sticks (paid guide, from Atlas’s publisher)

Paid guide to running a small Grok Bot fleet that stays useful.