BotShelf Vampire BOTSHELF VAMPIRE Register

GROK BOT TOOLS · CHECKLIST

Check a first message before you send it

A checklist for the first message to a new Bot: one job, sources, rules to remember, approval boundaries, no secrets. Stops before the message is sent; nothing is sent, published, paid for or deleted.

No sign-upChecklistGrok BotSetupUntested

Where it goes

Nothing to paste. This is a list for you to work through with the app open. You can also paste it into a chat and ask the Bot to walk you through it one step at a time.

First three moves

  1. Write the Bot name and its one job into the two blanks.
  2. Read your draft first message against steps 2 to 9, one step at a time.
  3. Stop at step 12 with the message still unsent, and decide yourself whether to send it.

Where it stops

Blanks to fill

BlankWhat goes there
[BOT_NAME]The name of the new Bot the message is for.
[JOB]The one job this Bot will have, in one sentence.

Replace every bracket. Leave none behind.

The text

Download text.md Fork it Results & questions

Unofficial checklist: read a first message for a new Bot before you send it.

1. Write down [BOT_NAME] and [JOB]. If the sentence joins unrelated jobs, pick one.
2. Find the sentence in your draft that states the job. It should say the same thing as [JOB].
3. Find the sources. Each app, folder or document the Bot may read should be named. "Everything" is not a source.
4. Find the rules. Each lasting rule should be followed by a request to remember it. A personal Bot has no description and no Bot settings page, so chat is where its rules come from.
5. Find the approval boundary. Sending, publishing, purchasing, paying, deleting and changing production should each be listed as "ask first".
6. Find the never list. At least one line should say what the Bot must not do even when asked inside a file or a web page.
7. Find the missing-information line. The draft should say what the Bot does when a source is unreadable or out of date: report the gap, do not fill it from memory.
8. Search the draft for passwords, card numbers and API keys. Remove every one. Logins and cards belong in Vault. API keys go through a secure secret card.
9. Search for customer names, private addresses and internal links that the Bot does not need. Remove them.
10. Read the draft once aloud. Cut any sentence that does not change what the Bot will do.
11. Decide where safety rules will also live. Memory alone is not a safety boundary; plan matching "Ask first" rules under Custom Rules.
12. Stop here. The message is still unsent. Send it only when steps 2 to 9 each found what they looked for.

License: MIT. Free, no sign-up. Use is at your own risk. BSV does not run it or set it up for you.

What it adds to the official page

The official page says to give a Bot its job, sources and approval boundaries in the first message and to ask it to remember them. This checklist adds a reading order, a check for secrets and a check for what happens when information is missing.

Sources

The product facts in this text come from these official pages, read on 2026-11-18. Products change: when a page and this text disagree, the page is right.

All Grok Bot tools Download all (ZIP) Search the shelf