Grok Bot Templates: personas, standing orders and handoffs

Here is a job I want a bot to do: [job, inputs, what good output looks like].
Write a bot persona with seven parts: name, title, one line, instructions, guardrails, ask-first rules, reporting. Keep instructions under 400 words with numbered steps and a fixed output format. List anything you had to assume.

Guardrails about actions, not attitude, are the ones a bot can follow.

Read these instructions: [paste].
For each action the bot can take in the world (send, post, spend, trade, deploy, delete, change settings), say whether it is FORBIDDEN, GATED (with the card it shows) or OPEN. Flag every OPEN action that cannot be undone.

Run it in a separate chat for an outside view.

# Grok Bot Templates: personas, standing orders and handoffs

A PaperChaseWebb pack, version 1.0. Written for Grok Bot: always-on bots with their own instructions, memory, scheduled routines and connected apps. Plain Markdown, so the persona bodies and rules also paste into other agents that take a system prompt, but the wording and the routine patterns are written for Grok Bot.

This pack does not build a bot for you. It is the set of files we use to set one up so it does useful work on a schedule, asks before anything it cannot take back, and reports in a way you will actually read. It comes from running a small team of bots for our own business every day and from two public breakdowns of Grok Bot business setups, both credited by link in `09-sources.md`. Everything here is written in our own words.

## Files

| File | What it is for |
|---|---|
| 01-anatomy.md | The seven parts of a bot that holds up: name, title, one line, instructions, guardrails, ask-first rules, reporting. A blank template |
| 02-persona-templates.md | 8 ready-to-paste personas: chief of staff, research and verification, SEO auditor, product builder, expense and receipts, social signal watcher, newsletter drafter, inbox drafter |
| 03-standing-orders.md | How to write scheduled routines: local-time cron, working-hours windows, flexible vs exact timing, watches that expire, quiet-by-default reports |
| 04-event-routines.md | Recipes for routines that wake on an event: a chat message, a pull request, an incoming email |
| 05-multi-bot-handoffs.md | One lead bot, desks that report results, blockers and decisions, a decision log and the four approval gates |
| 06-memory-hygiene.md | Profile vs journal, what to store, what never to store, and a monthly cleanup |
| 07-test-before-you-trust.md | A 20-point check and 10 test scenarios to run before a new bot touches real work |
| 08-prompts.md | 12 prompts for writing, tightening and auditing your bots |
| 09-sources.md | Every source we used, linked and credited |