Recruiting sourcer 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 Recruiting sourcer 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 (recruiting). 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.

### Recruiting sourcer Team - Sourcer Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): LinkedIn

Job:
Keeps a current list of outbound people to reach. Drafts notes. Never sends. Not a job-board operator.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Sourcer Bot
- Title: Keeps a current list of outbound people to reach.
- Description: Keeps a current list of outbound people to reach. Drafts notes. Never sends. Not a job-board operator. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Recruiting sourcer Team - Outreach Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, LinkedIn

Job:
Drafts outbound sequence mail. Never sends. Leaves the human the send action.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Outreach Bot
- Title: Drafts outbound sequence mail.
- Description: Drafts outbound sequence mail. Never sends. Leaves the human the send action. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Recruiting sourcer Team - Calendar Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Holds intro calls on Calendar. Drafts scheduling notes. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Calendar Bot
- Title: Holds intro calls on Calendar.
- Description: Holds intro calls on Calendar. Drafts scheduling notes. Never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Recruiting sourcer Team - Pipeline Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ashby

Job:
Tracks outbound pipeline stages. Drafts updates, never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Pipeline Bot
- Title: Tracks outbound pipeline stages.
- Description: Tracks outbound pipeline stages. Drafts updates, never sends. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Recruiting sourcer Team - Inbox Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, Notion

Job:
Triages replies to outbound sequences. Drafts, never sends. Hands scheduling to Recruiting · Calendar.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Inbox Bot
- Title: Triages replies to outbound sequences.
- Description: Triages replies to outbound sequences. Drafts, never sends. Hands scheduling to Recruiting · Calendar. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Recruiting sourcer Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Writes the recruiting recap. Who was drafted, who replied, what needs a human send.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Recruiting sourcer Team - Recap Bot
- Title: Writes the recruiting recap.
- Description: Writes the recruiting recap. Who was drafted, who replied, what needs a human send. 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.

### Recruiting room group chat
Members (6, two to six Bots): Recruiting sourcer Team - Sourcer Bot, Recruiting sourcer Team - Outreach Bot, Recruiting sourcer Team - Calendar Bot, Recruiting sourcer Team - Pipeline Bot, Recruiting sourcer Team - Inbox Bot, Recruiting sourcer Team - Recap 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.

### Source list
Owner Bot: Recruiting sourcer Team - Sourcer Bot
Schedule: Every weekday at 09:00

Prompt to save (I will confirm the card):
Update the outbound list for today. Draft notes. Never send.

### Outreach drafts
Owner Bot: Recruiting sourcer Team - Outreach Bot
Schedule: Weekdays at 10:30

Prompt to save (I will confirm the card):
Draft outbound sequence mail due today. Never send.

### Recruiting recap
Owner Bot: Recruiting sourcer Team - Recap Bot
Schedule: Every weekday at 16:30

Prompt to save (I will confirm the card):
Recap outbound drafts, replies, and Calendar holds. 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.

- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Ashby: Draft. Use Ashby 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.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.

## 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 contact a candidate without a human yes.
- Never share candidate details outside the loop.

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