Payroll run Team

• find-skills by vercel-labs

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• handoff by mattpocock

  Looking up counts on Skillselion. · 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 → Plugins.

From https://botteams.io (bookkeeping-payroll). 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.

### Payroll run Team - Headcount Bot
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 Team - Headcount 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.

### Payroll run Team - Variance Bot
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 Team - Variance 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.

### Payroll run Team - Expenses Bot
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 Team - Expenses 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.

### Payroll run Team - Calendar Bot
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 Team - Calendar 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.

### Payroll run Team - Brief Bot
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 Team - Brief 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.

## 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 Team - Headcount Bot, Payroll run Team - Variance Bot, Payroll run Team - Expenses Bot, Payroll run Team - Calendar Bot, Payroll run Team - Brief 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.

### Variance pass
Owner Bot: Payroll run Team - Variance 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 Team - Calendar 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.

## 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.
- Xero: Read. Use Xero read-only. Never move funds.
- Ramp: Read. Use Ramp read-only. Never move funds.

## 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 move money. Read the ledgers and report.
- Never file anything with a tax authority.

## 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: Payroll run Team. Move the group chat and Bots into it.
- In Settings → Plugins, 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.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".

## Done when

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