Account health 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 Account health 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 (success-health). 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.

### Account health Team - Usage Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Mixpanel

Job:
Reads product usage and names accounts whose activity has fallen for three weeks running.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Account health Team - Usage Bot
- Title: Reads product usage and names accounts whose activity has fallen for three weeks running.
- Description: Reads product usage and names accounts whose activity has fallen for three weeks running. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Account health Team - Tickets Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Zendesk

Job:
Reads support volume per account and separates a bad week from a pattern.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Account health Team - Tickets Bot
- Title: Reads support volume per account and separates a bad week from a pattern.
- Description: Reads support volume per account and separates a bad week from a pattern. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Account health Team - Contacts Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Flags accounts where the main contact has gone quiet or left.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Account health Team - Contacts Bot
- Title: Flags accounts where the main contact has gone quiet or left.
- Description: Flags accounts where the main contact has gone quiet or left. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Account health Team - Call Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Says which accounts need a human conversation this week, ranked, with the reason.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Account health Team - Call Bot
- Title: Says which accounts need a human conversation this week, ranked, with the reason.
- Description: Says which accounts need a human conversation this week, ranked, with the reason. 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.

### Health desk group chat
Members (4, two to six Bots): Account health Team - Usage Bot, Account health Team - Tickets Bot, Account health Team - Contacts Bot, Account health Team - Call 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.

### Health read
Owner Bot: Account health Team - Call Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Rank accounts needing a human conversation this week. Give the reason and the evidence for each.

### Usage decline
Owner Bot: Account health Team - Usage Bot
Schedule: Every weekday at 08:00

Prompt to save (I will confirm the card):
List accounts with three consecutive weeks of falling activity. Never contact them.

## 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.
- Zendesk: Ask before send. Use Zendesk only after a human says yes in the chat. Say the post, wait for a yes.
- Mixpanel: Draft. Use Mixpanel read-only.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.

## 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 send to a customer without a human yes.
- Never promise a date engineering has not agreed.

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