Contract register 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 Contract register 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 (legal-contracts). 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.

### Contract register Team - Register Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Docusign

Job:
Keeps the register of signed agreements and their key terms.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Contract register Team - Register Bot
- Title: Keeps the register of signed agreements and their key terms.
- Description: Keeps the register of signed agreements and their key terms. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Contract register Team - Obligations Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Extracts what the company must actually do, with dates.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Contract register Team - Obligations Bot
- Title: Extracts what the company must actually do, with dates.
- Description: Extracts what the company must actually do, with dates. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Contract register Team - Dates Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Holds renewal and notice dates and warns before a notice window closes.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Contract register Team - Dates Bot
- Title: Holds renewal and notice dates and warns before a notice window closes.
- Description: Holds renewal and notice dates and warns before a notice window closes. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Contract register Team - Store Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive

Job:
Checks the executed copy is filed where it should be.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Contract register Team - Store Bot
- Title: Checks the executed copy is filed where it should be.
- Description: Checks the executed copy is filed where it should be. 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.

### Contract desk group chat
Members (4, two to six Bots): Contract register Team - Register Bot, Contract register Team - Obligations Bot, Contract register Team - Dates Bot, Contract register Team - Store 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.

### Notice windows
Owner Bot: Contract register Team - Dates Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Name contracts whose notice window opens or closes in the next sixty days.

### Obligation pass
Owner Bot: Contract register Team - Obligations Bot
Schedule: Every month on the 1st at 10:00

Prompt to save (I will confirm the card):
List obligations falling due this month and who owns each.

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

- Docusign: Draft. Use Docusign for drafts only. Write the page, never publish.
- 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.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.

## 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 sign or send anything.
- Say clearly that this is not legal advice.

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