Policy desk 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

• triage 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 Policy desk 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 (workplace-policies). 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.

### Policy desk Team - Register Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Keeps the register of policies and their review dates.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Policy desk Team - Register Bot
- Title: Keeps the register of policies and their review dates.
- Description: Keeps the register of policies and their review dates. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Policy desk Team - Stale Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): SharePoint

Job:
Names policies past review or referring to things that changed.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Policy desk Team - Stale Bot
- Title: Names policies past review or referring to things that changed.
- Description: Names policies past review or referring to things that changed. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Policy desk Team - Findable Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean

Job:
Checks people can actually find a policy when they search for it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Policy desk Team - Findable Bot
- Title: Checks people can actually find a policy when they search for it.
- Description: Checks people can actually find a policy when they search for it. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Policy desk Team - Ack Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Tracks who has acknowledged which policy and drafts the reminder.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Policy desk Team - Ack Bot
- Title: Tracks who has acknowledged which policy and drafts the reminder.
- Description: Tracks who has acknowledged which policy and drafts the reminder. 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.

### Policy desk group chat
Members (4, two to six Bots): Policy desk Team - Register Bot, Policy desk Team - Stale Bot, Policy desk Team - Findable Bot, Policy desk Team - Ack 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.

### Review check
Owner Bot: Policy desk Team - Stale Bot
Schedule: Every month on the 1st at 09:00

Prompt to save (I will confirm the card):
List policies past their review date, longest overdue first.

### Acknowledgement
Owner Bot: Policy desk Team - Ack Bot
Schedule: Every Monday at 10:00

Prompt to save (I will confirm the card):
List people who have not acknowledged a required policy. Draft a reminder. Never 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.

- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- SharePoint: Draft. Use SharePoint for drafts only. Write the page, never publish.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- Glean: Draft. Use Glean read-only.

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

### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Skill id: `skill:mattpocock/skills#triage`.
Scope: only Policy desk Team - Findable Bot.


## 6. Also

Standing instructions for every Bot on this team:

- Never mail the whole company without a yes.
- Never book or cancel anything for anyone.

## 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: Policy desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Notion, SharePoint, Gmail, Glean. 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 ("Policy desk group chat", two to six Bots)
- I have created section "Policy desk 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.