Technical debt 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

• 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 Technical debt 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-debt). 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.

### Technical debt Team - Hotspots Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): GitHub

Job:
Finds files changed most often alongside bug fixes.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical debt Team - Hotspots Bot
- Title: Finds files changed most often alongside bug fixes.
- Description: Finds files changed most often alongside bug fixes. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

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

Job:
Links recurring production errors back to the code that keeps producing them.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical debt Team - Errors Bot
- Title: Links recurring production errors back to the code that keeps producing them.
- Description: Links recurring production errors back to the code that keeps producing them. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Technical debt Team - Register Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear, Notion

Job:
Keeps the debt register with a cost estimate per item.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical debt Team - Register Bot
- Title: Keeps the debt register with a cost estimate per item.
- Description: Keeps the debt register with a cost estimate per item. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Technical debt Team - Case Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Writes the argument for fixing one item, in time saved rather than elegance.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical debt Team - Case Bot
- Title: Writes the argument for fixing one item, in time saved rather than elegance.
- Description: Writes the argument for fixing one item, in time saved rather than elegance. 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.

### Debt desk group chat
Members (4, two to six Bots): Technical debt Team - Hotspots Bot, Technical debt Team - Errors Bot, Technical debt Team - Register Bot, Technical debt Team - Case 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.

### Hotspot scan
Owner Bot: Technical debt Team - Hotspots Bot
Schedule: Every Monday at 10:00

Prompt to save (I will confirm the card):
List files most often touched by bug fixes in the last quarter.

### Debt case
Owner Bot: Technical debt Team - Case Bot
Schedule: Every month on the 1st at 11:00

Prompt to save (I will confirm the card):
Write the case for the top debt item in time saved, not in taste.

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

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

### 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: Technical debt Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for GitHub, Linear, Sentry, 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

- Named Bots exist
- Named group chat exists ("Debt desk group chat", two to six Bots)
- I have created section "Technical debt 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.