Four Bots on the reseller channel. Flags conflicts, sends nothing.
Reseller channel Team
Keeps channel partners selling accurately, and makes deal registration something people actually do.
Bots
- Deals Grok Bot
- Enablement Grok Bot
- Performance Grok Bot
- Drafts Grok Bot
Channel desk group chat
- Deals Grok BotTracks registered deals and flags conflicts with direct sales.
- Enablement Grok BotNames partners using outdated materials or wrong pricing.
- Performance Grok BotReports which partners actually close, not just register.
- Drafts Grok BotDrafts partner communications.
HubSpot
Salesforce
Gmail
Notion
Deals Grok BotGrok Bot
Tracks registered deals and flags conflicts with direct sales.
Salesforce
Enablement Grok BotGrok Bot
Names partners using outdated materials or wrong pricing.
Notion
Performance Grok BotGrok Bot
Reports which partners actually close, not just register.
HubSpot
Drafts Grok BotGrok Bot
Drafts partner communications. Never sends them.
Gmail
Conflict check
Owner: Deals Grok BotEvery weekday at 09:00
Flag registered partner deals that overlap a direct opportunity.
Performance read
Owner: Performance Grok BotEvery month on the 1st at 10:00
Report registered versus closed per partner. Name partners registering but never closing.
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
Partnerships
Run Reseller channel 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 Reseller channel 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-reseller). 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.
### Reseller channel Team - Deals Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Salesforce
Job:
Tracks registered deals and flags conflicts with direct sales.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Reseller channel Team - Deals Bot
- Title: Tracks registered deals and flags conflicts with direct sales.
- Description: Tracks registered deals and flags conflicts with direct sales. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Reseller channel Team - Enablement Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Names partners using outdated materials or wrong pricing.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Reseller channel Team - Enablement Bot
- Title: Names partners using outdated materials or wrong pricing.
- Description: Names partners using outdated materials or wrong pricing. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Reseller channel Team - Performance Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Reports which partners actually close, not just register.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Reseller channel Team - Performance Bot
- Title: Reports which partners actually close, not just register.
- Description: Reports which partners actually close, not just register. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Reseller channel Team - Drafts Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts partner communications. Never sends them.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Reseller channel Team - Drafts Bot
- Title: Drafts partner communications.
- Description: Drafts partner communications. Never sends them. 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.
### Channel desk group chat
Members (4, two to six Bots): Reseller channel Team - Deals Bot, Reseller channel Team - Enablement Bot, Reseller channel Team - Performance Bot, Reseller channel Team - Drafts 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.
### Conflict check
Owner Bot: Reseller channel Team - Deals Bot
Schedule: Every weekday at 09:00
Prompt to save (I will confirm the card):
Flag registered partner deals that overlap a direct opportunity.
### Performance read
Owner Bot: Reseller channel Team - Performance Bot
Schedule: Every month on the 1st at 10:00
Prompt to save (I will confirm the card):
Report registered versus closed per partner. Name partners registering but never closing.
## 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.
- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Salesforce: Ask before send. Use Salesforce only after a human says yes in the chat. Say the post, wait for a yes.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.
- 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 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: Reseller channel Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Gmail, 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 ("Channel desk group chat", two to six Bots)
- I have created section "Reseller channel 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
- Co-marketing Team
Runs joint campaigns where both sides have to deliver, and makes the missing half obvious early.
Notion
Gmail
Google Calendar
LinkedIn
- Integration partners Team
Tracks technical partnerships through the part that actually breaks: the integration staying alive after launch.
GitHub
Linear
HubSpot
Notion
- Partner sourcing Team
Finds and qualifies potential partners against what the product actually needs, not against logo appeal.
ExaHubSpot
Notion
LinkedIn

