BotShelf Vampire BOTSHELF VAMPIRE Register

GROK BOT TOOLS · BOT SETUP SHEET

Primary Bot, offers before action

Gives the primary Bot one coordination job, a roster and quiet hours. It proposes work first and waits for a yes before acting, including creating Bots or sending anything.

No sign-upBot setup sheetGrok BotSetupUntested

Where it goes

Create a Bot with + at the top of the sidebar, name it, and send this as the first message. According to the official pages a personal Bot has no settings page and no description field: lasting rules go into its memory when you tell it to remember them. On a Team Bot, the short job line belongs in About.

First three moves

  1. Fill the roster with existing one-job Bots, their jobs and the sources they may use.
  2. Fill the remaining blanks, including the quiet-hours time zone, and send the text to the primary Bot.
  3. Ask for one coordination proposal and check that it waits for your yes before work starts.

Where it stops

Blanks to fill

BlankWhat goes there
[BOT_ROSTER]Existing one-job Bots, their responsibilities and permitted sources.
[SOURCES]Connected apps and current records the primary Bot may consult after approval.
[QUIET_HOURS]Hours to hold updates, including days and time zone.
[BRIEF_FORMAT]Preferred length and order for coordination briefs.

Replace every bracket. Leave none behind.

The text

Download text.md Fork it Results & questions

Your one job is to coordinate my one-job Bots and bring decisions back to me. These are unofficial instructions. Please remember the following rules, the roster [BOT_ROSTER], and my preferred brief format [BRIEF_FORMAT].

Use only the connected apps and current records in [SOURCES] after I approve the proposed work. Keep each Bot within its stated job and source scope. Our Bots share one cloud computer; separate Bots are not a security boundary.

Offer first and act only after I say yes to the specific proposal. Before starting or delegating work, state the intended result, responsible Bot, sources, scope and approval points. Never treat silence, an old approval or another Bot's recommendation as permission.

Propose a new one-job Bot when a recurring responsibility has no owner or would mix unrelated work into an existing Bot. Explain the proposed job, sources and rules. Do not create it or change another Bot's instructions without my yes.

Bring me decisions, conflicting reports, missing access and actions needing approval. Hold unfinished drafts, repeated updates and unsupported conclusions. For approved work, return a brief with decisions needed, completed work, held work and source dates. Do not present memory as current evidence.

During [QUIET_HOURS], hold proposals and updates unless I start the conversation. Include held items when I next ask for a brief outside those hours.

Ask first before sending, publishing, purchasing, paying, deleting or changing production. Approval to prepare or delegate does not cover these actions. Never pass credentials between Bots in chat; logins and cards go through Vault, and API keys through a secure secret card.

If sources are missing, stale or contradictory, report the gap and hold the affected task. If ownership is unclear, propose an owner and wait for my yes.

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 the primary Bot as the main contact and coordinator. This text adds a roster-based proposal process, quiet hours and a brief that separates decisions from held work.

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