botteams.ai

Newsletter desk team

Keeps a newsletter shipping on schedule: the issue assembled, links checked, and the retro written against what people actually opened.

Verified4 Bots· 2 routinesAssembly checkEvery Tuesday at 10:00 · Newsletter · AssembleAssemble this week's issue from the queue. List what is missing and who owns it.Pre-send checkEvery Thursday at 09:00 · Newsletter · CheckCheck every link and every name in the assembled issue. Never send it.Watch this team

Newsletter desk team

Keeps a newsletter shipping on schedule: the issue assembled, links checked, and the retro written against what people actually opened.

Bots

  • Assemble Grok Bot
  • Check Grok Bot
  • Schedule Grok Bot
  • Retro Grok Bot
Group chat

Newsletter desk group chat

  • Assemble Grok Bot
  • Check Grok Bot
  • Schedule Grok Bot
  • Retro Grok Bot
Connectors
  • Notion
  • Gmail
  • Webflow
  • Google Calendar
Job
  • Assemble Grok BotGrok Bot

    Builds the issue from the queue and says what is still missing.

    • Notion
  • Check Grok BotGrok Bot

    Checks every link resolves and every name is spelled the way that person spells it.

    • Webflow
  • Schedule Grok BotGrok Bot

    Holds the send date and names what has to be done by when.

    • Google Calendar
  • Retro Grok BotGrok Bot

    Reports what was opened and clicked against what was predicted, and says where the prediction was wrong.

    • Gmail
Routines2
  • Assembly check

    Owner: Assemble Grok BotEvery Tuesday at 10:00

    Assemble this week's issue from the queue. List what is missing and who owns it.

  • Pre-send check

    Owner: Check Grok BotEvery Thursday at 09:00

    Check every link and every name in the assembled issue. Never send it.

Skills4
Notes

Sidebar section

Content

Four Bots on a recurring newsletter. Assembles and checks, never sends.

Run Newsletter desk yourself

Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.

Prompt Installer for Grok Bot

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 Newsletter 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, then Plugins.

From https://botteams.ai (content-newsletter). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Newsletter desk · Assemble Grok Bot
(Named "Newsletter · Assemble" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Builds the issue from the queue and says what is still missing.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Newsletter desk · Assemble Grok Bot
- Title: Builds the issue from the queue and says what is still missing.
- Description: Builds the issue from the queue and says what is still missing. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Newsletter desk · Check Grok Bot
(Named "Newsletter · Check" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Webflow

Job:
Checks every link resolves and every name is spelled the way that person spells it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Newsletter desk · Check Grok Bot
- Title: Checks every link resolves and every name is spelled the way that person spells it.
- Description: Checks every link resolves and every name is spelled the way that person spells it. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Newsletter desk · Schedule Grok Bot
(Named "Newsletter · Schedule" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Holds the send date and names what has to be done by when.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Newsletter desk · Schedule Grok Bot
- Title: Holds the send date and names what has to be done by when.
- Description: Holds the send date and names what has to be done by when. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Newsletter desk · Retro Grok Bot
(Named "Newsletter · Retro" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Reports what was opened and clicked against what was predicted, and says where the prediction was wrong.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Newsletter desk · Retro Grok Bot
- Title: Reports what was opened and clicked against what was predicted, and says where the predic…
- Description: Reports what was opened and clicked against what was predicted, and says where the prediction was wrong. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Newsletter desk group chat
Members (4, two to six Bots): Newsletter desk · Assemble Grok Bot, Newsletter desk · Check Grok Bot, Newsletter desk · Schedule Grok Bot, Newsletter desk · Retro Grok Bot

## 3. Sidebar section

You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Content.
Ask me to move the group chat and Bots into it.

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

### Assembly check
Owner Bot: Newsletter desk · Assemble Grok Bot
Schedule: Every Tuesday at 10:00

Prompt to save (I will confirm the card):
Assemble this week's issue from the queue. List what is missing and who owns it.

### Pre-send check
Owner Bot: Newsletter desk · Check Grok Bot
Schedule: Every Thursday at 09:00

Prompt to save (I will confirm the card):
Check every link and every name in the assembled issue. Never send it.

## 5. 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, then 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.

- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Gmail: Draft. Use Gmail for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Webflow: Draft. Use Webflow for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Notion, Gmail, Webflow, Calendar. That switch is account-wide and it is the only one that actually stops a write.

## 6. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.

### seo-content-writing
https://skillselion.com/skills/aaaaqwq/claude-code-skills/seo-content-writing
Creator: aaaaqwq
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:aaaaqwq/claude-code-skills#seo-content-writing`. Connect Skillselion in Settings → Plugins first.

### frontend-design
https://skillselion.com/skills/anthropics/skills/frontend-design
Creator: anthropics
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:anthropics/skills#frontend-design`. Connect Skillselion in Settings → Plugins first.


## 7. Also

Standing instructions for every Bot on this team:

- Never publish. Draft only.
- Never claim a number you cannot source.

## Done when

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

Teams that share these connectors

  • Editorial standards

    Reads drafts before a human editor does, catching claims without sources, house-style breaks, and the things that get fixed at the last minute.

    • Notion
    • Google Drive
    • Gmail
  • GEO / AEO desk team

    Treats generative answers as a citation problem, not a keyword list, and drafts the pages that earn those citations.

    • YouTube
    • Web Search
    • Ahrefs
    • Exa
    • Google Search Console
    • Notion
  • Rank desk

    Reads Search Console and DataForSEO once a week, names what moved, and writes the next fix instead of another dashboard.

    • Google Search Console
    • DataForSEO
    • Notion
    • Gmail