Work
Write your bot's description as a contract, not a job title
You keep repeating the same three rules in every chat with the same bot.
What hurt
silentguy (@silentguyy66) wrote up where each kind of instruction belongs in Grok Bot, quoting xAI's own docs. The key point: the description is the only instruction the bot keeps between tasks. Not affiliated with xAI.
What to install or create
A description names ownership, sources, output and boundary ("Never contact a customer without approval"). A task message names outcome, sources, constraints, deliverable and review point. Test each instruction with one question: will this still be true next month? If yes, it goes in the description; if no, it stays in the message. Skills need a validation step, and a taught skill is only a draft.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/silentguyy66/status/2108957020187468171 (credit @silentguyy66).
- 2Open your last five chats with one bot and count the instructions you repeated.
- 3Rewrite its description as ownership, sources, output and boundary.
- 4Write your next task with outcome, sources, constraints, deliverable and a review point.
- 5For every skill, add how to validate the result and what needs approval.
Approval fence
Put "what needs approval" in the description itself, so it holds in every task.
What to tweak
Every instruction you type twice is a missing line in the description.
Source
silentguy @silentguyy66 · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.