• 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 Backup and recovery 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 (infra-backups). 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.

### Backup and recovery · Ran Grok Bot
(Named "Backup · Ran" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Supabase, AWS Core

Job:
Confirms each backup ran and how large it was.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Backup and recovery · Ran Grok Bot
- Title: Confirms each backup ran and how large it was.
- Description: Confirms each backup ran and how large it was. 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.

### Backup and recovery · Restore Grok Bot
(Named "Backup · Restore" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Tracks when a restore was last tested and how long it took.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Backup and recovery · Restore Grok Bot
- Title: Tracks when a restore was last tested and how long it took.
- Description: Tracks when a restore was last tested and how long it took. 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.

### Backup and recovery · Gaps Grok Bot
(Named "Backup · Gaps" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): AWS Core

Job:
Names data with no backup policy at all.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Backup and recovery · Gaps Grok Bot
- Title: Names data with no backup policy at all.
- Description: Names data with no backup policy at all. 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.

### Backup and recovery · Drill Grok Bot
(Named "Backup · Drill" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): PagerDuty

Job:
Drafts the next recovery drill and who runs it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Backup and recovery · Drill Grok Bot
- Title: Drafts the next recovery drill and who runs it.
- Description: Drafts the next recovery drill and who runs it. 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.

### Recovery desk group chat
Members (4, two to six Bots): Backup and recovery · Ran Grok Bot, Backup and recovery · Restore Grok Bot, Backup and recovery · Gaps Grok Bot, Backup and recovery · Drill 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: Infrastructure.
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.

### Backup check
Owner Bot: Backup and recovery · Ran Grok Bot
Schedule: Every day at 07:00

Prompt to save (I will confirm the card):
Confirm every scheduled backup ran and report size against the trailing average.

### Restore age
Owner Bot: Backup and recovery · Restore Grok Bot
Schedule: Every Monday at 10:00

Prompt to save (I will confirm the card):
Report how long since each system had a tested restore. Name anything over ninety days.

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

- Supabase: Draft. Use Supabase for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- AWS Core: Draft. Use AWS Core for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- PagerDuty: Draft. Use PagerDuty for drafts only. Leave every draft unsent and every change unsaved so a human can review it.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Supabase, AWS Core, Notion, PagerDuty. 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 apply a change. Draft the plan.
- Never touch production without a human yes.

## Done when

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