BotShelf Vampire BOTSHELF VAMPIRE Register

GROK BOT TOOLS · CHECKLIST

Check a Bot before sharing

Checks a Bot’s sharing material and team access for private information. Stops before sharing, publishing, sending, payment, deletion or production changes.

No sign-upChecklistGrok BotSharingUntested

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. Fill in the Bot and intended audience before reviewing any sharing material.
  2. Inspect the identity and description for private details, using About for a Team Bot.
  3. Work through the skills, routines, apps and files before making any sharing decision.

Where it stops

Blanks to fill

BlankWhat goes there
[BOT_NAME]The Bot whose sharing material you will review.
[AUDIENCE]The intended audience: public users or a defined team group.

Replace every bracket. Leave none behind.

The text

Download text.md Fork it Results & questions

Unofficial checklist: read everything that travels with a Bot before you share it.

1. Write down [BOT_NAME] and [AUDIENCE]. A public link and access for a defined team are different decisions.
2. Remember what sharing copies: the Bot's identity, description, skills and routines. Your computer and logins are not copied.
3. Read the name, label and picture. Remove anything that names a customer, a person or an internal project.
4. Read the description. A Team Bot has one under About. A personal Bot has none, so read the standing rules you gave it in chat instead.
5. Open each skill. Remove secrets, customer data and internal addresses, including those inside examples and output formats.
6. Open each routine. Remove the same from its sources, matching rules and result destinations.
7. For a Team Bot, list its apps, secrets, skills and files and hold the list against [AUDIENCE]. Everyone who chats with it shares all of them.
8. For each shared connector, ask what the account behind it can reach. Teammates act through that account, including making changes. Share only an account with nothing sensitive.
9. Check that no login, card number or API key sits in a skill, a routine or the description. Logins and cards belong in Vault. API keys go through a secure secret card.
10. Read the approval rules the audience will get. Sending, publishing, purchasing, paying, deleting and production changes should be "Ask first".
11. Know the way back: deleting a Bot also removes the copy shared from it, and its link stops working. Deleting is permanent.
12. Stop here. Share or publish only after every finding above is closed. Keep a Team Bot as a Draft until then.

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 pages describe public configuration copies and shared Team Bot resources. This checklist adds a review order, a private record of unresolved gaps and a stop before sharing.

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