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.