How to write a Grok Bot job description that still works next month

Most weak Grok Bots are not underpowered. They are under-specified. The profile says “helps with marketing” and every Monday the Bot has to re-ask what a good recap looks like.

A job description in Grok Bot is the contract. The conversation is the work order. If you mix them, memory fills with one-off exceptions and the Bot gets worse at the role you thought you hired it for.

The five parts of a job that holds

Write the description so a new contractor could start on Wednesday:

1. Outcome — the thing that exists when the week is over. A watch list, a recap, a digest, a draft PR. Not “be helpful.”
2. Sources — where truth lives. Salesforce is true for stage. The wiki is true for product names. Chat is not true for pricing.
3. Artifact and place — the file, the channel, the ticket. “Leave it in Finance/AP” beats “send me something.”
4. Working style — cadence, format, how much prose. “Four-minute recap, one cut, one double-down.”
5. Hard no — send, pay, merge, page, scrape behind a login. Put the no in the description even if you also use product approvals.

Example:

Own the weekly campaign recap. Pull Google Ads, HubSpot, and GA4. Write to Marketing/Recaps using last week’s template. Recommend one cut and one scale-up. Never change budgets or publish.

What does not belong in the description

• This week’s account list.
• A Slack thread you are angry about.
• API keys, customer dumps, or internal URLs you would not put on a public share page.

xAI’s share flow copies identity, description, skills, and routines into a public link. Write the description as if that link could leak. Keep secrets off the profile.

Description vs message

| Put it here | Example | | --- | --- | | Description | Never send external mail without approval. | | Message | Draft follow-ups for these twelve accounts. |