Engineering 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

• tdd by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• improve-codebase-architecture by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• prototype by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• setup-matt-pocock-skills 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 Engineering 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 (engineering). 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.

### Engineering desk Team - Triage Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): GitHub

Job:
Reads new GitHub issues and pull requests. Labels what is clearly routine, flags the rest. Never merges, never closes.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Engineering desk Team - Triage Bot
- Title: Reads new GitHub issues and pull requests.
- Description: Reads new GitHub issues and pull requests. Labels what is clearly routine, flags the rest. Never merges, never closes. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Engineering desk Team - Backlog Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Keeps the Linear backlog honest. Surfaces stale issues and sprint drift. Drafts updates, never reassigns work.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Engineering desk Team - Backlog Bot
- Title: Keeps the Linear backlog honest.
- Description: Keeps the Linear backlog honest. Surfaces stale issues and sprint drift. Drafts updates, never reassigns work. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Engineering desk Team - Errors Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Sentry

Job:
Watches Sentry for new and spiking issues. Reports the top offenders with a stack summary. Never resolves an issue.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Engineering desk Team - Errors Bot
- Title: Watches Sentry for new and spiking issues.
- Description: Watches Sentry for new and spiking issues. Reports the top offenders with a stack summary. Never resolves an issue. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Engineering desk Team - Deploys Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Vercel

Job:
Tracks Vercel deploys and build failures. Says what shipped and what broke. Never triggers or rolls back a deploy.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Engineering desk Team - Deploys Bot
- Title: Tracks Vercel deploys and build failures.
- Description: Tracks Vercel deploys and build failures. Says what shipped and what broke. Never triggers or rolls back a deploy. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Engineering desk Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Writes the engineering recap. What merged, what is failing, what needs a human decision.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Engineering desk Team - Recap Bot
- Title: Writes the engineering recap.
- Description: Writes the engineering recap. What merged, what is failing, what needs a human decision. 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.

### Engineering floor group chat
Members (5, two to six Bots): Engineering desk Team - Triage Bot, Engineering desk Team - Backlog Bot, Engineering desk Team - Errors Bot, Engineering desk Team - Deploys Bot, Engineering desk Team - Recap 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.

### Issue sweep
Owner Bot: Engineering desk Team - Triage Bot
Schedule: Every 3 hours during working hours

Prompt to save (I will confirm the card):
Sweep new GitHub issues and pull requests. Label routine items. Flag anything that needs a maintainer. Never merge or close.

### Error watch
Owner Bot: Engineering desk Team - Errors Bot
Schedule: Every weekday at 09:30

Prompt to save (I will confirm the card):
Report new and spiking Sentry issues since yesterday, worst first. Do not resolve or ignore anything.

### Engineering recap
Owner Bot: Engineering desk Team - Recap Bot
Schedule: Every weekday at 17:30

Prompt to save (I will confirm the card):
Recap merges, deploy failures, error spikes, and decisions waiting on a human.

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

- GitHub: Draft. Use GitHub for drafts only. Draft the PR or branch, never merge.
- Linear: Draft. Use Linear for drafts only. Write the page, never publish.
- Sentry: Draft. Use Sentry read-only.
- Vercel: Draft. Use Vercel for drafts only. Do not deploy to production.

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

### tdd
https://skillselion.com/skills/mattpocock/skills/tdd
Creator: mattpocock
Skill id: `skill:mattpocock/skills#tdd`.
Scope: every Bot on this team (team scope).

### improve-codebase-architecture
https://skillselion.com/skills/mattpocock/skills/improve-codebase-architecture
Creator: mattpocock
Skill id: `skill:mattpocock/skills#improve-codebase-architecture`.
Scope: every Bot on this team (team scope).

### prototype
https://skillselion.com/skills/mattpocock/skills/prototype
Creator: mattpocock
Skill id: `skill:mattpocock/skills#prototype`.
Scope: only Engineering desk Team - Deploys Bot.

### setup-matt-pocock-skills
https://skillselion.com/skills/mattpocock/skills/setup-matt-pocock-skills
Creator: mattpocock
Skill id: `skill:mattpocock/skills#setup-matt-pocock-skills`.
Scope: every Bot on this team (team scope).


## 6. Also

Standing instructions for every Bot on this team:

- Never merge or deploy. Draft only.
- Never touch production data.

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