Work
Have your main bot read the official guides and propose house rules for your team
The official guides are full of good practices, but nobody has time to map them onto their own setup.
What hurt
After Ben Lang (@benln) tipped people to tell their main bot to go through the new guides and recommend best practices, Victor Kryukov (@vkryukov) did it and posted his bot's ranked list of eight practices, tied to his own setup. Not affiliated with xAI.
What to install or create
Ask your main bot to read the guides and rank what is worth adopting for your bots, most valuable first, with concrete proposals. His list starts with Auto-review rules (no purchase or booking without your OK, no deletes outside its computer), then turning corrections into rules, a weekly self-audit, quiet-by-default routines, and proof in coding PRs.
Bots
Main bot
Reads the official guides and ranks practices worth adopting for your setup.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
Ranked practices from the guides (author-quoted, links removed)
Quoted from @vkryukov — as published. Do not invent a second system prompt.
I read all 15 Grok Bot guides. These are the practices worth adopting, most valuable first: 1. Write Auto-review rules. The guides warn that a login one bot uses works for every bot. Our shared 1Password vault has no stated limits. Proposed rules: no purchase or booking without your OK unless a routine you approved does it, and no deletes outside my computer. They'd go in Auto-review rules. 2. Turn every correction into a rule. When you correct a bot, it writes the rule into its skill or memory right away. Improver would review real mistakes and tell the other bots about the fix. 3. Run a weekly self-audit. Improver would ask which routines fire but get ignored, what you've requested by hand three times, and what should exist but doesn't. Each answer becomes a yes or no for you. The X watch would also track what it already covered, so it reports only new tips. 4. Use your voice in emails you send. Build a style profile from your sent mail, then learn from how you edit my drafts before you press Send. 5. Watch for dropped promises and unanswered asks. Inbox Triage flags emails you sent that never got a reply, and promises you made, only when the next move is yours. It goes into the morning brief. 6. Default routines to quiet. If nothing changed, send nothing. Specialists report through me unless it's urgent. New routines start paused with a sample run until you turn them on. 7. Verify before claiming. Add standing rules to shared memory. Open the live thread before stating anything. Treat an empty search as unverified. Preview family calendar and Basecamp changes before saving them. 8. Require proof in coding PRs. Builder attaches test output and before and after screenshots. It fixes failing checks and merge conflicts before asking you to merge.
First run
- 1Read https://x.com/vkryukov/status/2107501842741752047 (credit @vkryukov).
- 2Tell your main bot: read the official Grok Bot guides and recommend the best practices for my bots, most valuable first, each tied to my setup.
- 3Compare its list with his eight below; ask it to drop anything you won't use.
- 4Approve the first one or two rules (Auto-review rules and quiet-by-default routines are good starts).
- 5Let it apply only those, show you what changed, and come back for the rest later.
Approval fence
Treat the list as proposals. Approve each rule yourself; the top one exists precisely so purchases, bookings, and deletes always wait for your OK.
What to tweak
Don't read the manual alone — let the bot read it against your setup and hand you yes/no proposals.
Source
Victor Kryukov @vkryukov · 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.