Four Bots on whether knowledge can actually be found.
Findability Team
Measures whether people can find what exists, and fixes the naming that stops them.
Bots
- Failed Grok Bot
- Naming Grok Bot
- Duplicates Grok Bot
- Recap Grok Bot
Findability desk group chat
- Failed Grok BotReports searches that returned nothing useful.
- Naming Grok BotNames documents whose title does not match what anyone would search for.
- Duplicates Grok BotFinds several documents answering the same question differently.
- Recap Grok BotReports what people looked for and could not find.
GleanNotion
Google Drive
Failed Grok BotGrok Bot
Reports searches that returned nothing useful.
Glean
Naming Grok BotGrok Bot
Names documents whose title does not match what anyone would search for.
Notion
Duplicates Grok BotGrok Bot
Finds several documents answering the same question differently.
Google Drive
Recap Grok BotGrok Bot
Reports what people looked for and could not find.
Glean
Failed search
Owner: Failed Grok BotEvery Friday at 14:00
List searches that returned nothing useful this week, most frequent first.
Duplicate scan
Owner: Duplicates Grok BotEvery Monday at 11:00
Find documents answering the same question differently. Name all copies.
find-skills by vercel-labsLooking up counts on Skillselion. · Fetch at run · View on Skillselion
handoff by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Knowledge
Run Findability yourself
Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.
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 Findability 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 (knowledge-search). 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.
### Findability Team - Failed Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean
Job:
Reports searches that returned nothing useful.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Findability Team - Failed Bot
- Title: Reports searches that returned nothing useful.
- Description: Reports searches that returned nothing useful. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Findability Team - Naming Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Names documents whose title does not match what anyone would search for.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Findability Team - Naming Bot
- Title: Names documents whose title does not match what anyone would search for.
- Description: Names documents whose title does not match what anyone would search for. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Findability Team - Duplicates Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive
Job:
Finds several documents answering the same question differently.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Findability Team - Duplicates Bot
- Title: Finds several documents answering the same question differently.
- Description: Finds several documents answering the same question differently. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Findability Team - Recap Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean
Job:
Reports what people looked for and could not find.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Findability Team - Recap Bot
- Title: Reports what people looked for and could not find.
- Description: Reports what people looked for and could not find. 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.
### Findability desk group chat
Members (4, two to six Bots): Findability Team - Failed Bot, Findability Team - Naming Bot, Findability Team - Duplicates Bot, Findability 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.
### Failed search
Owner Bot: Findability Team - Failed Bot
Schedule: Every Friday at 14:00
Prompt to save (I will confirm the card):
List searches that returned nothing useful this week, most frequent first.
### Duplicate scan
Owner Bot: Findability Team - Duplicates Bot
Schedule: Every Monday at 11:00
Prompt to save (I will confirm the card):
Find documents answering the same question differently. Name all copies.
## 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.
- Glean: Draft. Use Glean read-only.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Google Drive: Draft. Use Google Drive 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 delete a page. Archive it and say so.
- Draft edits, never publish over someone.
## 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: Findability Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Glean, Notion, Google Drive. 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 ("Findability desk group chat", two to six Bots)
- I have created section "Findability 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.Teams that share these connectors
- Decision log Team
Records what was decided and why, so the same argument is not had twice a year later.
Notion
Linear
GleanSlack
- Onboarding docs Team
Keeps the documents a new joiner actually reads in their first week correct, because those are the ones that mislead.
Notion
GleanGoogle Drive
Slack
- Runbooks Team
Keeps operational runbooks correct, since a wrong runbook is read at the worst possible moment.
Notion
PagerDuty
GitHub
Glean

