Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.
# Grok Bot Teams installer
Set up a team for me called Client agency Team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings → Plugins.
From https://botteams.io (agency). Source: https://github.com/ellelion/botteams.
## 1. Create these Bots
Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.
### Client agency Team - Intake Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, HubSpot
Job:
Reads inbound agency mail. Sorts new work from noise. Never sends. Does not run a client website.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Intake Bot
- Title: Reads inbound agency mail.
- Description: Reads inbound agency mail. Sorts new work from noise. Never sends. Does not run a client website. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Client agency Team - Accounts Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar, HubSpot
Job:
Keeps a calm list of active clients and next meetings. Drafts updates, never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Accounts Bot
- Title: Keeps a calm list of active clients and next meetings.
- Description: Keeps a calm list of active clients and next meetings. Drafts updates, never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Client agency Team - Delivery Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar, Notion
Job:
Tracks delivery promises against Calendar. Drafts status notes. Never sends. No site ops.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Delivery Bot
- Title: Tracks delivery promises against Calendar.
- Description: Tracks delivery promises against Calendar. Drafts status notes. Never sends. No site ops. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Client agency Team - Billing Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe, Docusign
Job:
Watches Stripe retainers and failed invoices. Alerts and drafts only. Does not send money.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Billing Bot
- Title: Watches Stripe retainers and failed invoices.
- Description: Watches Stripe retainers and failed invoices. Alerts and drafts only. Does not send money. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Client agency Team - Follow-ups Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts follow-ups for open account threads. Never sends.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Follow-ups Bot
- Title: Drafts follow-ups for open account threads.
- Description: Drafts follow-ups for open account threads. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Client agency Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.
Job:
Writes the floor recap. What moved, what is blocked, what needs a human send. Drafts only.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Client agency Team - Recap Bot
- Title: Writes the floor recap.
- Description: Writes the floor recap. What moved, what is blocked, what needs a human send. Drafts only. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
## 2. Create this group chat
Open a group chat with two to six of the Bots above. Do not add more than six.
### Agency floor group chat
Members (6, two to six Bots): Client agency Team - Intake Bot, Client agency Team - Accounts Bot, Client agency Team - Delivery Bot, Client agency Team - Billing Bot, Client agency Team - Follow-ups Bot, Client agency Team - Recap Bot
## 3. Routines (confirm card required)
Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.
### Intake sweep
Owner Bot: Client agency Team - Intake Bot
Schedule: Every 3 hours during waking hours
Prompt to save (I will confirm the card):
Sweep inbound agency mail. Sort new work. Never send. Skip site-ops threads.
### Billing watch
Owner Bot: Client agency Team - Billing Bot
Schedule: Every weekday at 10:00
Prompt to save (I will confirm the card):
Check Stripe for retainer charges and failed invoices. Report in Agency floor. Do not refund or send funds.
### Floor recap
Owner Bot: Client agency Team - Recap Bot
Schedule: Every weekday at 17:00
Prompt to save (I will confirm the card):
Recap accounts, delivery, billing alerts, and drafts waiting on a human send.
## 4. Connectors and how far they go
Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings → Plugins first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Stripe: Read. Use Stripe read-only. Never move funds.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Docusign: Draft. Use Docusign for drafts only. Write the page, never publish.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
## 5. Skills
Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).
### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).
### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).
## 6. Also
Standing instructions for every Bot on this team:
- Never send client mail. Draft only.
- Never change a signed scope without asking.
## Human steps
These are yours. The Bot cannot do them.
- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Client agency Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Gmail, Calendar, Stripe, Docusign, Notion. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".
## Done when
- Named Bots exist
- Named group chat exists ("Agency floor group chat", two to six Bots)
- I have created section "Client agency Team"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected
Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.