Design research 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 Design research 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 (design-research). 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.

### Design research Team - Sessions Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zoom

Job:
Tracks scheduled sessions and flags the ones with no notes filed.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design research Team - Sessions Bot
- Title: Tracks scheduled sessions and flags the ones with no notes filed.
- Description: Tracks scheduled sessions and flags the ones with no notes filed. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Design research Team - Themes Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Finds themes appearing across multiple sessions, not just one loud participant.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design research Team - Themes Bot
- Title: Finds themes appearing across multiple sessions, not just one loud participant.
- Description: Finds themes appearing across multiple sessions, not just one loud participant. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Design research Team - Evidence Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean

Job:
Attaches the actual quote and timestamp to every finding.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design research Team - Evidence Bot
- Title: Attaches the actual quote and timestamp to every finding.
- Description: Attaches the actual quote and timestamp to every finding. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Design research Team - Handoff Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Figma

Job:
Writes the findings note for the design team, separating what was observed from what was inferred.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Design research Team - Handoff Bot
- Title: Writes the findings note for the design team, separating what was observed from what was…
- Description: Writes the findings note for the design team, separating what was observed from what was inferred. 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.

### Research desk group chat
Members (4, two to six Bots): Design research Team - Sessions Bot, Design research Team - Themes Bot, Design research Team - Evidence Bot, Design research Team - Handoff 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.

### Notes check
Owner Bot: Design research Team - Sessions Bot
Schedule: Every weekday at 17:00

Prompt to save (I will confirm the card):
List sessions held without notes filed, oldest first.

### Theme pass
Owner Bot: Design research Team - Themes Bot
Schedule: Every Friday at 11:00

Prompt to save (I will confirm the card):
Find themes across at least three sessions. Attach a quote to each. Never generalise from one participant.

## 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.
- Zoom: Draft. Use Zoom for drafts only. Draft the event, do not send invites.
- Figma: Draft. Use Figma for drafts only. Write the page, never publish.
- 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).


## 6. Also

Standing instructions for every Bot on this team:

- Never overwrite a file someone else is working in.
- Draft feedback, never post it as final.

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