Rank 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

• 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 Rank 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 (content-rank-desk). 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.

### Rank desk Team - Queries Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Search Console

Job:
Reads Search Console for queries that gained or lost impressions, not vanity keywords.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Rank desk Team - Queries Bot
- Title: Reads Search Console for queries that gained or lost impressions, not vanity keywords.
- Description: Reads Search Console for queries that gained or lost impressions, not vanity keywords. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Rank desk Team - Positions Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): DataForSEO

Job:
Pulls DataForSEO ranks for the watched set and flags jumps of three or more.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Rank desk Team - Positions Bot
- Title: Pulls DataForSEO ranks for the watched set and flags jumps of three or more.
- Description: Pulls DataForSEO ranks for the watched set and flags jumps of three or more. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

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

Job:
Turns the movement into a one-page Notion plan. What to fix first, and why.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Rank desk Team - Plan Bot
- Title: Turns the movement into a one-page Notion plan.
- Description: Turns the movement into a one-page Notion plan. What to fix first, and why. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

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

Job:
Drafts the weekly mail. Movement, plan, and what still needs a human yes.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Rank desk Team - Recap Bot
- Title: Drafts the weekly mail.
- Description: Drafts the weekly mail. Movement, plan, and what still needs a human yes. 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.

### Rank desk group chat
Members (4, two to six Bots): Rank desk Team - Queries Bot, Rank desk Team - Positions Bot, Rank desk Team - Plan Bot, Rank 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.

### Weekly ranks
Owner Bot: Rank desk Team - Positions Bot
Schedule: Every Monday at 08:30

Prompt to save (I will confirm the card):
Pull the watched keyword set. Report positions that moved three or more. Quote the tool. Invent nothing.

### Recap mail
Owner Bot: Rank desk Team - Recap Bot
Schedule: Every Monday at 16:00

Prompt to save (I will confirm the card):
Draft the weekly rank recap. Do not send.

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

- Search Console: Read. Use Google Search Console read-only.
- DataForSEO: Read. Use DataForSEO read-only.
- 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).

### 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: every Bot on this team (team scope).

### frontend-design
https://skillselion.com/skills/anthropics/skills/frontend-design
Creator: anthropics
Skill id: `skill:anthropics/skills#frontend-design`.
Scope: every Bot on this team (team scope).


## 6. Also

Standing instructions for every Bot on this team:

- Never change the site. Write the plan.
- Never claim a number you cannot source.
- Never send mail. Draft only.

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