Talent 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

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 Talent 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 (recruiting-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.

### Talent sourcing Team - Search Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): GitHub, LinkedIn

Job:
Finds candidates by what they have built rather than by title.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Talent sourcing Team - Search Bot
- Title: Finds candidates by what they have built rather than by title.
- Description: Finds candidates by what they have built rather than by title. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Talent sourcing Team - Screen Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): GitHub

Job:
Reads public work and says specifically why someone is worth contacting.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Talent sourcing Team - Screen Bot
- Title: Reads public work and says specifically why someone is worth contacting.
- Description: Reads public work and says specifically why someone is worth contacting. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Talent sourcing Team - Dedupe Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ashby

Job:
Checks nobody is contacted twice or was rejected recently.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Talent sourcing Team - Dedupe Bot
- Title: Checks nobody is contacted twice or was rejected recently.
- Description: Checks nobody is contacted twice or was rejected recently. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

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

Job:
Keeps the sourced list per role with the reason attached.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Talent sourcing Team - List Bot
- Title: Keeps the sourced list per role with the reason attached.
- Description: Keeps the sourced list per role with the reason attached. 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): Talent sourcing Team - Search Bot, Talent sourcing Team - Screen Bot, Talent sourcing Team - Dedupe Bot, Talent sourcing Team - List 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 pass
Owner Bot: Talent sourcing Team - Search Bot
Schedule: Every weekday at 10:00

Prompt to save (I will confirm the card):
Find candidates for open roles based on public work. Give a specific reason each.

### Duplicate check
Owner Bot: Talent sourcing Team - Dedupe Bot
Schedule: Every weekday at 10:30

Prompt to save (I will confirm the card):
Flag sourced candidates already contacted or recently rejected.

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

- LinkedIn: Ask before send. Use LinkedIn only after a human says yes in the chat. Say the post, wait for a yes.
- GitHub: Draft. Use GitHub for drafts only. Draft the PR or branch, never merge.
- Ashby: Draft. Use Ashby for drafts only. Write the page, never publish.
- 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: Talent sourcing Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for GitHub, 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 ("Sourcing desk group chat", two to six Bots)
- I have created section "Talent 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.