Cloud cost 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

• seo-content-writing by aaaaqwq

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

• frontend-design by anthropics

  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 Cloud cost 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 (infra-cost). 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.

### Cloud cost Team - Growth Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Vantage

Job:
Names services whose cost grew without a matching traffic change.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Cloud cost Team - Growth Bot
- Title: Names services whose cost grew without a matching traffic change.
- Description: Names services whose cost grew without a matching traffic change. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Cloud cost Team - Idle Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): AWS Core

Job:
Finds provisioned resources doing nothing.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Cloud cost Team - Idle Bot
- Title: Finds provisioned resources doing nothing.
- Description: Finds provisioned resources doing nothing. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Cloud cost Team - Attribute Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Datadog

Job:
Attributes spend to a team or product where tagging allows.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Cloud cost Team - Attribute Bot
- Title: Attributes spend to a team or product where tagging allows.
- Description: Attributes spend to a team or product where tagging allows. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Cloud cost Team - Brief Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Writes the monthly cost brief with three specific actions.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Cloud cost Team - Brief Bot
- Title: Writes the monthly cost brief with three specific actions.
- Description: Writes the monthly cost brief with three specific actions. 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.

### Cost desk group chat
Members (4, two to six Bots): Cloud cost Team - Growth Bot, Cloud cost Team - Idle Bot, Cloud cost Team - Attribute Bot, Cloud cost Team - Brief 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.

### Growth scan
Owner Bot: Cloud cost Team - Growth Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Name services whose cost grew over ten percent without a traffic change.

### Idle sweep
Owner Bot: Cloud cost Team - Idle Bot
Schedule: Every Wednesday at 10:00

Prompt to save (I will confirm the card):
List idle or unattached resources with their monthly cost. Never delete anything.

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

- AWS Core: Draft. Use AWS Core for drafts only. Do not deploy to production.
- Datadog: Draft. Use Datadog read-only.
- Vantage: Draft. Use Vantage for drafts only. Do not deploy to production.
- 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).

### seo-content-writing
https://skillselion.com/skills/aaaaqwq/claude-code-skills/seo-content-writing
Creator: aaaaqwq
Skill id: `skill:aaaaqwq/claude-code-skills#seo-content-writing`.
Scope: only Cloud cost Team - Growth Bot.

### frontend-design
https://skillselion.com/skills/anthropics/skills/frontend-design
Creator: anthropics
Skill id: `skill:anthropics/skills#frontend-design`.
Scope: only Cloud cost Team - Growth Bot.


## 6. Also

Standing instructions for every Bot on this team:

- Never apply a change. Draft the plan.
- Never touch production 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: Cloud cost Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for AWS Core, Datadog, Vantage, 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 ("Cost desk group chat", two to six Bots)
- I have created section "Cloud cost 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.