• find-skills by vercel-labs

  … · Fetch at run · View on Skillselion

• handoff by mattpocock

  … · Fetch at run · View on Skillselion

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 Payroll run 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, then Plugins.

From https://botteams.ai (bookkeeping-payroll). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Payroll run · Headcount Grok Bot
(Named "Payroll · Headcount" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Xero

Job:
Lists starters, leavers, and contract changes since last run, and flags anyone whose pay should change this month.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Payroll run · Headcount Grok Bot
- Title: Lists starters, leavers, and contract changes since last run, and flags anyone whose pay…
- Description: Lists starters, leavers, and contract changes since last run, and flags anyone whose pay should change this month. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Payroll run · Variance Grok Bot
(Named "Payroll · Variance" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Xero

Job:
Compares this run to last, line by line, and explains every difference over one percent. Never approves a run.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Payroll run · Variance Grok Bot
- Title: Compares this run to last, line by line, and explains every difference over one percent.
- Description: Compares this run to last, line by line, and explains every difference over one percent. Never approves a run. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Payroll run · Expenses Grok Bot
(Named "Payroll · Expenses" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ramp

Job:
Reads Ramp for expense claims that should sit in payroll rather than the card ledger.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Payroll run · Expenses Grok Bot
- Title: Reads Ramp for expense claims that should sit in payroll rather than the card ledger.
- Description: Reads Ramp for expense claims that should sit in payroll rather than the card ledger. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Payroll run · Calendar Grok Bot
(Named "Payroll · Calendar" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Holds the cutoff, approval, and payment dates and says which one is next.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Payroll run · Calendar Grok Bot
- Title: Holds the cutoff, approval, and payment dates and says which one is next.
- Description: Holds the cutoff, approval, and payment dates and says which one is next. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Payroll run · Brief Grok Bot
(Named "Payroll · Brief" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Writes the one-page brief the approver reads before signing off. Never signs off.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Payroll run · Brief Grok Bot
- Title: Writes the one-page brief the approver reads before signing off.
- Description: Writes the one-page brief the approver reads before signing off. Never signs off. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Payroll desk group chat
Members (5, two to six Bots): Payroll run · Headcount Grok Bot, Payroll run · Variance Grok Bot, Payroll run · Expenses Grok Bot, Payroll run · Calendar Grok Bot, Payroll run · Brief Grok Bot

## 3. Sidebar section

You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Bookkeeping.
Ask me to move the group chat and Bots into it.

## 4. 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.

### Variance pass
Owner Bot: Payroll run · Variance Grok Bot
Schedule: Every month on the 24th at 09:00

Prompt to save (I will confirm the card):
Compare this payroll run to last month line by line. Explain every difference over one percent. Never approve.

### Cutoff notice
Owner Bot: Payroll run · Calendar Grok Bot
Schedule: Every month on the 20th at 09:00

Prompt to save (I will confirm the card):
Name the payroll cutoff, approval, and payment dates for this month and who owns each.

## 5. 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, then 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. Leave every draft unsent and every change unsaved so a human can review it.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Xero: Read. Use Xero read-only. Read and summarise it. Do not create, edit, send, move, or delete anything in Xero.
- Ramp: Read. Use Ramp read-only. Read and summarise it. Do not create, edit, send, move, or delete anything in Ramp.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Gmail, Calendar, Xero, Ramp. That switch is account-wide and it is the only one that actually stops a write.

## 6. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.


## 7. Also

Standing instructions for every Bot on this team:

- Never move money. Read the ledgers and report.
- Never file anything with a tax authority.

## Done when

- Named Bots exist
- Named group chat exists ("Payroll desk group chat", two to six Bots)
- I have created section "Bookkeeping"
- 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.