When should you use it?
- Several bots write on your behalf
- Drafts sound generic
- You use different tones per audience
Not for: Legal or medical wording; Messages you never review
What do you need, and what do you get?
You need
- Samples of your sent writing
- Notes on tone by channel
- A few test prompts
You get
- A voice bot other bots call
- A tone-by-channel guide
- Drafts closer to your style
How does it work, step by step?
- Collect samplesExport a few dozen sent emails, messages and posts you are happy with.
- Create the writerGive one bot the samples and the job of drafting for everyone.
- Run eval roundsAsk for drafts, mark what is off, and save each correction.
- Map tonesWrite which tone fits work mail, family chats and public posts.
- Route all draftsTell the other bots to request text from the writer before sending.
The prompt
Our own prompt, inspired by u/steve228uk on r/GrokBot and written to work in Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are my writer. Learn my style from {writing_samples_folder} and the tone rules in {tone_guide}. When another bot asks for text, return a draft plus one line naming the tone rule you used. Keep it short and plain unless the guide says otherwise. Never send anything yourself. Log each correction I make in {tone_guide} under the right channel.
Inspired by u/steve228uk on r/GrokBot: Here's how Grok Bot is doing all the stuff I hate…. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Private messages used as samples can leak into drafts for other people; prune them.
- Tone guides go stale; refresh samples every few months.
- Nothing goes out without your look.
Our take
Centralizing voice is a smart move most multi-bot setups miss. If five bots each guess at your tone, you fix the same quirks five times; one writer with a curated sample set means each correction sticks everywhere. Pick samples deliberately. A few casual family texts in the training set can bleed into a client email, so separate personal and professional samples and label them. Keep a short channel-by-person tone sheet next to the samples, and have the writer state which rule it applied so mismatches are easy to catch. Route all outward drafts through this bot, including ones started by helpers, so nothing bypasses the voice check. Refresh samples every few months from recent writing you are proud of. Never put passwords, private addresses or confidential client details into the sample set; strip those before training. You still approve anything that sends, including posts and email. Re-run a few golden sample prompts after any instruction change.
Where the time goes back: You correct your voice once instead of in every bot.
FAQ
How long did training take?
Why one writer?
Source and credit
Inspired by u/steve228uk on r/GrokBot. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Here's how Grok Bot is doing all the stuff I hate…
- Creator
- u/steve228uk on r/GrokBot
- Published on
- Original date
- Aug 23, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.