Project handover 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 Project handover 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-handover). 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.

### Project handover Team - Assets Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive

Job:
Checks final deliverables are in the client folder and named the way the studio names things. Reports what is missing.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Project handover Team - Assets Bot
- Title: Checks final deliverables are in the client folder and named the way the studio names thi…
- Description: Checks final deliverables are in the client folder and named the way the studio names things. Reports what is missing. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Project handover Team - Access Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive

Job:
Lists every shared file the client team can still reach so a human can decide what to revoke. Never changes a permission.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Project handover Team - Access Bot
- Title: Lists every shared file the client team can still reach so a human can decide what to rev…
- Description: Lists every shared file the client team can still reach so a human can decide what to revoke. Never changes a permission. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Project handover Team - Invoice Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe

Job:
Checks the final invoice exists in Stripe and matches the agreed number. Never issues or edits one.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Project handover Team - Invoice Bot
- Title: Checks the final invoice exists in Stripe and matches the agreed number.
- Description: Checks the final invoice exists in Stripe and matches the agreed number. Never issues or edits one. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Project handover Team - Retro Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Drafts the retro in Notion from the project record: what slipped, what worked, what to price differently next time.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Project handover Team - Retro Bot
- Title: Drafts the retro in Notion from the project record: what slipped, what worked, what to pr…
- Description: Drafts the retro in Notion from the project record: what slipped, what worked, what to price differently next time. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Project handover Team - Close Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Drafts the closing note to the client. Never sends it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Project handover Team - Close Bot
- Title: Drafts the closing note to the client.
- Description: Drafts the closing note to the client. Never sends it. 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.

### Handover desk group chat
Members (5, two to six Bots): Project handover Team - Assets Bot, Project handover Team - Access Bot, Project handover Team - Invoice Bot, Project handover Team - Retro Bot, Project handover Team - Close 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.

### Close checklist
Owner Bot: Project handover Team - Assets Bot
Schedule: Every weekday at 17:00

Prompt to save (I will confirm the card):
For projects marked delivered this week, check final assets are filed and correctly named. List what is missing.

### Access review
Owner Bot: Project handover Team - Access Bot
Schedule: Every Monday at 10:00

Prompt to save (I will confirm the card):
List client-shared files on closed projects. Report only. Never change a permission.

## 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.
- Google Drive: Draft. Use Google Drive for drafts only. Write the page, never publish.
- Stripe: Read. Use Stripe read-only. Never move funds.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.

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