Proposal desk 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 Proposal desk 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 (sales-proposals). 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.

### Proposal desk Team - Build Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Salesforce

Job:
Drafts the proposal from the opportunity record.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Proposal desk Team - Build Bot
- Title: Drafts the proposal from the opportunity record.
- Description: Drafts the proposal from the opportunity record. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Proposal desk Team - Check Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Checks pricing and terms against what was actually discussed.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Proposal desk Team - Check Bot
- Title: Checks pricing and terms against what was actually discussed.
- Description: Checks pricing and terms against what was actually discussed. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Proposal desk Team - Track Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Docusign

Job:
Tracks proposals out and flags the quiet ones.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Proposal desk Team - Track Bot
- Title: Tracks proposals out and flags the quiet ones.
- Description: Tracks proposals out and flags the quiet ones. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Proposal desk Team - Draft Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Drafts the nudge for a proposal gone quiet. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Proposal desk Team - Draft Bot
- Title: Drafts the nudge for a proposal gone quiet.
- Description: Drafts the nudge for a proposal gone quiet. Never sends. 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.

### Proposal desk group chat
Members (4, two to six Bots): Proposal desk Team - Build Bot, Proposal desk Team - Check Bot, Proposal desk Team - Track Bot, Proposal desk Team - Draft 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.

### Terms check
Owner Bot: Proposal desk Team - Check Bot
Schedule: Every weekday at 10:00

Prompt to save (I will confirm the card):
Check draft proposals against what was discussed. Flag any pricing that does not match.

### Quiet watch
Owner Bot: Proposal desk Team - Track Bot
Schedule: Every weekday at 16:00

Prompt to save (I will confirm the card):
List proposals with no response for five days, oldest first.

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

- Salesforce: Ask before send. Use Salesforce only after a human says yes in the chat. Say the post, wait for a yes.
- Docusign: Draft. Use Docusign for drafts only. Write the page, never publish.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- 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 email a prospect. Draft only.
- Never discount without a human yes.

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