Customer Pulse Briefing Grok Bot

• find-skills by vercel-labs

  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

NOTE: This is an EXAMPLE team from the public directory. Use it to learn the format.
Do not treat it as a production company recipe.

Set up a new Bot for me called Customer Pulse Briefing Bot. Walk me through anything you need, then save it.
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 (customer-pulse-briefing-bot). Source: https://github.com/ellelion/botteams.

## 1. Create this Bot

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.

### Customer Pulse Briefing Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail, Slack, Notion

Job:
Aggregates customer signals from Gmail and Slack, drafts a Notion priority queue, and routes messages for approval.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Customer Pulse Briefing Bot
- Title: Aggregates customer signals from Gmail and Slack, drafts a Notion priority queue, and rou…
- Description: Aggregates customer signals from Gmail and Slack, drafts a Notion priority queue, and routes messages for approval. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

## 2. No group chat, no sidebar section

This is one Bot. Do not create a group chat for it, and do not create a sidebar section: a section is for several chats that belong together.

## 3. Routines (confirm card required)

Ping the Bot with each routine so it can save them.
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.

### Weekday Pulse Briefing
Owner Bot: Customer Pulse Briefing Bot
Schedule: Weekdays 09:00

Prompt to save (I will confirm the card):
Read Gmail and Slack messages, draft a Notion priority queue, and do not send replies without explicit approval.

## 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.
- Slack: Ask before send. Use Slack only after a human says yes in the chat. Say the post, wait for a yes.
- 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).


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

- The named Bot exists
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected

Uninstall: delete the Bot in the Grok Bot sidebar.
There is no remote uninstall from this catalog.