Partner sourcing 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

• prototype 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 Partner sourcing 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 (partnerships-sourcing). 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.

### Partner sourcing Team - Find Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Exa

Job:
Researches companies whose product genuinely complements ours.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Partner sourcing Team - Find Bot
- Title: Researches companies whose product genuinely complements ours.
- Description: Researches companies whose product genuinely complements ours. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Partner sourcing Team - Qualify Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Scores fit on overlap of audience and product, and says no clearly.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Partner sourcing Team - Qualify Bot
- Title: Scores fit on overlap of audience and product, and says no clearly.
- Description: Scores fit on overlap of audience and product, and says no clearly. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Partner sourcing Team - Contacts Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): LinkedIn

Job:
Finds the right person rather than the most senior one.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Partner sourcing Team - Contacts Bot
- Title: Finds the right person rather than the most senior one.
- Description: Finds the right person rather than the most senior one. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Partner sourcing Team - Pipeline Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Keeps the partner pipeline current and flags stalls.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Partner sourcing Team - Pipeline Bot
- Title: Keeps the partner pipeline current and flags stalls.
- Description: Keeps the partner pipeline current and flags stalls. 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.

### Sourcing desk group chat
Members (4, two to six Bots): Partner sourcing Team - Find Bot, Partner sourcing Team - Qualify Bot, Partner sourcing Team - Contacts Bot, Partner sourcing Team - Pipeline 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.

### Sourcing pass
Owner Bot: Partner sourcing Team - Find Bot
Schedule: Every Wednesday at 10:00

Prompt to save (I will confirm the card):
Find five companies whose product complements ours. Say why for each.

### Stall check
Owner Bot: Partner sourcing Team - Pipeline Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
List partner conversations with no movement in three weeks.

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

- Exa: Draft. Use Exa read-only.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- LinkedIn: Ask before send. Use LinkedIn only after a human says yes in the chat. Say the post, wait for a yes.

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

### prototype
https://skillselion.com/skills/mattpocock/skills/prototype
Creator: mattpocock
Skill id: `skill:mattpocock/skills#prototype`.
Scope: only Partner sourcing Team - Find Bot.


## 6. Also

Standing instructions for every Bot on this team:

- Never mail a partner without a human yes.
- Never agree to terms.

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