Founder hiring 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

• grill-me by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• triage 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 Founder hiring 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 (founder-hiring). 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.

### Founder hiring Team - Inbound Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ashby

Job:
Sorts applications and names the ones worth a conversation, with the reason.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Founder hiring Team - Inbound Bot
- Title: Sorts applications and names the ones worth a conversation, with the reason.
- Description: Sorts applications and names the ones worth a conversation, with the reason. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Founder hiring Team - Waiting Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ashby

Job:
Flags candidates waiting on a reply longer than three days.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Founder hiring Team - Waiting Bot
- Title: Flags candidates waiting on a reply longer than three days.
- Description: Flags candidates waiting on a reply longer than three days. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

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

Job:
Holds interview slots and flags any not yet booked.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Founder hiring Team - Slots Bot
- Title: Holds interview slots and flags any not yet booked.
- Description: Holds interview slots and flags any not yet booked. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Founder hiring Team - Notes Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion, Gmail

Job:
Chases the interview note and drafts the decision summary.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Founder hiring Team - Notes Bot
- Title: Chases the interview note and drafts the decision summary.
- Description: Chases the interview note and drafts the decision summary. 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.

### Hiring room group chat
Members (4, two to six Bots): Founder hiring Team - Inbound Bot, Founder hiring Team - Waiting Bot, Founder hiring Team - Slots Bot, Founder hiring Team - Notes 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.

### Waiting candidates
Owner Bot: Founder hiring Team - Waiting Bot
Schedule: Every weekday at 09:00

Prompt to save (I will confirm the card):
List candidates waiting more than three days for a reply, oldest first.

### Note chase
Owner Bot: Founder hiring Team - Notes Bot
Schedule: Every weekday at 18:00

Prompt to save (I will confirm the card):
List interviews held today with no note filed.

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

### grill-me
https://skillselion.com/skills/mattpocock/skills/grill-me
Creator: mattpocock
Skill id: `skill:mattpocock/skills#grill-me`.
Scope: every Bot on this team (team scope).

### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Skill id: `skill:mattpocock/skills#triage`.
Scope: only Founder hiring Team - Inbound Bot.


## 6. Also

Standing instructions for every Bot on this team:

- Never send mail. Draft only.
- Never move funds.

## 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: Founder hiring 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 ("Hiring room group chat", two to six Bots)
- I have created section "Founder hiring 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.