botteams.ai

Editorial standards team

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

Verified4 Bots· 2 routinesDraft reviewEvery weekday at 11:00 · Editorial · ClaimsFor drafts marked ready, flag claims without a source and numbers without a date.Style passEvery weekday at 11:30 · Editorial · StyleCheck drafts against the house style sheet. Quote each break. Never rewrite the draft yourself.Watch this team

Editorial standards team

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

Bots

  • Claims Grok Bot
  • Style Grok Bot
  • Links Grok Bot
  • Handoff Grok Bot
Group chat

Editorial desk group chat

  • Claims Grok Bot
  • Style Grok Bot
  • Links Grok Bot
  • Handoff Grok Bot
Connectors
  • Notion
  • Google Drive
  • Gmail
Job
  • Claims Grok BotGrok Bot

    Flags every factual claim without a source and every number without a date.

    • Notion
  • Style Grok BotGrok Bot

    Checks a draft against the house style sheet and lists the breaks, quoting each one.

    • Notion
  • Links Grok BotGrok Bot

    Checks links resolve and that nothing points at a competitor by accident.

    • Google Drive
  • Handoff Grok BotGrok Bot

    Writes the note the human editor reads first: what is solid, what needs a decision.

    • Gmail
Routines2
  • Draft review

    Owner: Claims Grok BotEvery weekday at 11:00

    For drafts marked ready, flag claims without a source and numbers without a date.

  • Style pass

    Owner: Style Grok BotEvery weekday at 11:30

    Check drafts against the house style sheet. Quote each break. Never rewrite the draft yourself.

Skills4
Notes

Sidebar section

Content

Four Bots ahead of the editor. Marks up drafts, never rewrites them.

Run Editorial standards 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 Editorial standards 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-editorial). 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.

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

Job:
Flags every factual claim without a source and every number without a date.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Editorial standards · Claims Grok Bot
- Title: Flags every factual claim without a source and every number without a date.
- Description: Flags every factual claim without a source and every number without a date. 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.

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

Job:
Checks a draft against the house style sheet and lists the breaks, quoting each one.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Editorial standards · Style Grok Bot
- Title: Checks a draft against the house style sheet and lists the breaks, quoting each one.
- Description: Checks a draft against the house style sheet and lists the breaks, quoting each one. 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.

### Editorial standards · Links Grok Bot
(Named "Editorial · Links" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive

Job:
Checks links resolve and that nothing points at a competitor by accident.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Editorial standards · Links Grok Bot
- Title: Checks links resolve and that nothing points at a competitor by accident.
- Description: Checks links resolve and that nothing points at a competitor by accident. 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.

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

Job:
Writes the note the human editor reads first: what is solid, what needs a decision.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Editorial standards · Handoff Grok Bot
- Title: Writes the note the human editor reads first: what is solid, what needs a decision.
- Description: Writes the note the human editor reads first: what is solid, what needs a decision. 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.

### Editorial desk group chat
Members (4, two to six Bots): Editorial standards · Claims Grok Bot, Editorial standards · Style Grok Bot, Editorial standards · Links Grok Bot, Editorial standards · Handoff 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.

### Draft review
Owner Bot: Editorial standards · Claims Grok Bot
Schedule: Every weekday at 11:00

Prompt to save (I will confirm the card):
For drafts marked ready, flag claims without a source and numbers without a date.

### Style pass
Owner Bot: Editorial standards · Style Grok Bot
Schedule: Every weekday at 11:30

Prompt to save (I will confirm the card):
Check drafts against the house style sheet. Quote each break. Never rewrite the draft yourself.

## 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.
- Google Drive: Draft. Use Google Drive 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.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Notion, Google Drive, Gmail. 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 ("Editorial 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

  • 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
  • Newsletter desk

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

    • Notion
    • Gmail
    • Webflow
    • Google Calendar
  • 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