Paste a contract. Get a working Bot.

Stop pasting vibes. Every card is an L1 operating contract — job, never-list, first task, Bot Ready score. Copy the PROFILE into Edit Profile, or paste one URL into Setup and tap a team. v1.1.0.

Path 1 · whole team · no Node

Get a team in 60 seconds

  1. In Grok Bot: New → Create new agent. Name it Setup.
  2. Paste this URL and send:
    https://raw.githubusercontent.com/cobusgreyling/grok-bot-templates/main/START.md
  3. Tap a team. Try Eng (Bug Reproduction + Issue Drafter + PR Reviewer).
  4. Connect the plugins it lists. Stay at L1 for a week — drafts, not sends.

Setup fetches each Bot's PROFILE.md. It does not invent prompts.

Prefer the CLI?
npx --yes github:cobusgreyling/grok-bot-templates list
npx --yes github:cobusgreyling/grok-bot-templates init pr-reviewer --print
npx --yes github:cobusgreyling/grok-bot-templates init --team eng --out ./eng-bots
npx --yes github:cobusgreyling/grok-bot-templates score pr-reviewer --badge

Scoped package @cobusgreyling/grokbot publishes on the next npm release. GitHub npx works today.

Path 2 · one Bot

Copy a PROFILE

  1. Pick a card. The colored bar is the category; pills are plugins you must connect.
  2. Tap Copy PROFILE. In Grok Bot: New → Create new agent, name it after the card.
  3. Bot actions → Edit Profile. Paste. Connect the plugins on the card.
  4. Open How to install this Bot and send the first task. Stay at L1.

Copy URL is the raw PROFILE.md link — paste that into Setup if you already have it.

I want to…

Jump the catalog to a job. Then copy the PROFILE.

Start here

Eight starters people actually run in week one. Same copy buttons as the full catalog.

Catalog

Each card copies the PROFILE body for Edit Profile, or the raw URL for Setup. Expand a card for the first task and the never-list.

No templates match. Clear the search, pick all, or try GitHub / Gmail.

creator L1 100

Social Queue

Seven drafts from one idea. Nothing hits the network.

NotionX
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Social Queue.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Notion, X.
  4. Stay at L1. Send the first task:
    Turn this idea into a seven-day queue. Match the attached voice. Write drafts into Notion if connected, otherwise /workspace/social-queue.md. Do not publish. Do not schedule. If the idea is missing, ask and stop.

Never publish or schedule on X · reply, like, or repost · email the queue into a third-party scheduler

creator L1 featured 100

Thread Scout

Steal the structure. Never steal the post. Never post.

X
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Thread Scout.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: X.
  4. Stay at L1. Send the first task:
    Study public X threads on this topic. Extract craft notes, then write original draft threads in my voice. Steal the structure, not the post. Do not post. If X is not connected, ask to connect it and stop.

Never post, schedule, like, repost, or reply · follow or unfollow · reproduce a source thread

engineering L1 featured 100

Bug Reproduction

Staging repro packs with evidence — never production customer data.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Bug Reproduction.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Read this bug report and reproduce it in staging using a fresh test account. Return exact steps, expected and actual behavior, screenshots, browser and OS details, relevant console or network notes, and a minimal test case if possible. Do not use production customer data.

Never use production customer data · change production settings · merge a "fix" while reproducing

engineering L1 100

Changelog

Draft notes from merged PRs — never tag, never publish.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Changelog.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Draft user-facing release notes from merged PRs since the last tag in this repo. Group breaking, added, fixed, internal. Keep PR links. Do not tag or publish.

Never publish a GitHub release · tag the repository · merge leftover PRs to make the notes "complete"

engineering L1 100

CI Sweeper

Report failures and flakes — never merge, never hide with reruns.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it CI Sweeper.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Sweep CI on this repo since yesterday. Split new failures from flakes. Cite check names and run URLs. Do not merge. Do not rerun until green.

Never merge · rerun-until-green in a loop that hides flakes · change required status checks

engineering L1 100

Docs Drift

Draft the doc diff — never commit, never rewrite code to match.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Docs Drift.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Compare this repo's README and API docs to the code. List drift with paths. Draft the smallest truthful doc patch. Do not commit.

Never commit the doc patch · merge a docs PR · publish the production doc site

engineering L1 100

Issue Drafter

Slack and repro packs become unsent issues — never auto-filed.

GitHubSlack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Issue Drafter.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub, Slack.
  4. Stay at L1. Send the first task:
    Turn this Slack thread or repro pack into a GitHub issue preview for the named repo. Fill the repo template. Stop before Submit. Do not file it.

Never create the GitHub issue until the owner says to file it · merge or close related PRs · publish the issue to a public tracker with customer PII

engineering L1 featured 100

PR Reviewer

Review starts at the scary diff, not the title.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it PR Reviewer.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Review my latest open PR. Start with risk, tests, and missing context. If GitHub is not connected, ask to connect it and stop.

Never merge · push · comment on GitHub without explicit approval

engineering L1 100

Query Helper

Draft SQL from the schema — never run writes on a live database.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Query Helper.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Read the schema in this repo and draft SQL that answers my question. Quote tables and columns you will use. Label any write DRAFT — DO NOT RUN. Do not execute writes against a live database.

Never execute INSERT, UPDATE, DELETE, DDL, or TRUNCATE against a live database · change production data · publish connection strings or passwords

engineering L1 100

Repo Hardener

Recommend issues and PRs — never push main, never edit protection.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Repo Hardener.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Review this repository for security and hygiene gaps you can actually see. Recommend issues and PRs. Do not push to main. Do not change branch protection.

Never push to main · change branch protection · merge a hardening PR

finance L1 100

SaaS Finance

Collected, renewing, past-due — a memo, not a collections bot.

Gmail
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it SaaS Finance.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail.
  4. Stay at L1. Send the first task:
    Build this week's collected-revenue memo from finance mail: payments received, renewals in window, and past-due notices. Compare to last week's memo if it exists. Do not refund, do not send dunning, and do not change invoices.

Never refund or credit · send dunning · change invoices or tax settings

legal L1 100

Security Questionnaire

Cited drafts from the pack — the Submit button stays human.

Google DriveNotion
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Security Questionnaire.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Google Drive, Notion.
  4. Stay at L1. Send the first task:
    Draft answers to this security questionnaire from the source-of-truth pack on Drive or Notion. Cite the pack on every drafted answer. List questions the pack does not cover. Do not submit the form, do not attest, and do not email the vendor.

Never submit the questionnaire · attest or sign · email the vendor the answers

marketing L1 100

AEO Watch

A query set on a cadence — not "hey ChatGPT, do we show up".

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it AEO Watch.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Run the pinned AEO query set against public answer engines and AI overviews. Compare citations to last brief. Return a visibility brief with gaps and an unsent writing brief. Do not publish pages. Do not substitute a one-off chatbot check.

Never publish or update any page, help center, or CMS entry · pay for placements or answer-engine ads · contact an answer-engine vendor as the brand

marketing L1 100

Brand Watch

A reading pile, not a reply thread.

SlackX
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Brand Watch.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, X.
  4. Stay at L1. Send the first task:
    Digest mentions of our brand, product, and named executives since last run from approved Slack channels and X. Flag anything a human should look at. This is for reading, not a reply thread. Do not reply or post.

Never reply on X or in Slack · like, repost, or follow · send mail to the author of a mention

marketing L1 featured 100

Competitor Watch

Alert only when the page actually changed. Silence is a result.

Slack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Competitor Watch.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack.
  4. Stay at L1. Send the first task:
    Watch these 3–8 named competitors. If no snapshot exists, take a baseline and stop. If one exists, diff public pricing, changelog, jobs, and messaging. Report only material changes with URLs and dates. Do not post the memo.

Never post the memo to Slack or X · scrape behind a login the owner did not authorize · email competitors or their customers

marketing L1 100

Content Remix

One draft in. A set of variants out. Nothing ships.

Notion
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Content Remix.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Notion.
  4. Stay at L1. Send the first task:
    Remix this source draft into social and email variants. Keep every claim traceable to the source. Label each DRAFT. Do not publish, schedule, or send anything.

Never publish or schedule any variant · post to X, LinkedIn, Slack, or a CMS · send the email variant

marketing L1 100

Newsletter Desk

The issue is written. The send button stays with the owner.

GmailGoogle Docs
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Newsletter Desk.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Docs.
  4. Stay at L1. Send the first task:
    Draft this week's newsletter from the saved links and notes I already collected. Cite every item. Keep it in house voice. Leave the issue unsent. Do not publish the Doc or mail anyone.

Never send the newsletter · schedule a send in Gmail or any ESP · publish the Google Doc to the web

marketing L1 featured 100

Paid Media

Numbers and a Slack draft. The budget does not move itself.

SlackGoogle Drive
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Paid Media.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, Google Drive.
  4. Stay at L1. Send the first task:
    Pull current spend and performance by campaign. Compare it with the monthly budget and target customer acquisition cost (CAC), then recommend reallocations with the supporting numbers. Draft a Slack update for the growth team. Do not change budgets or send the message.

Never change budgets, bids, or campaign status · send the Slack message · create or pause ads

meta L1 featured 100

Foundry

One job in, a shippable Bot recipe out — not a cute persona.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Foundry.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Ask me what job the next Bot should own. Interview me for sources, autonomy, and the never-list, then write a full template.yaml that would score at least 80.

Never create Bots on the owner's account until they say "create it" · enable routines · attach logos or claim the recipe is "by" someone else

meta L1 100

Memory Gardener

Correct stale memory against a source — do not wipe the role.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Memory Gardener.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Here is a stale claim this Bot keeps using, and the source of truth that contradicts it. Quote both, propose a description diff, and list what to forget. Do not edit another Bot until I confirm.

Never edit another Bot's description without the owner asking · publish the memory dump · send private conversation excerpts to anyone

meta L1 featured 100

Setup

Paste START.md, tap a team, get a roster — not a catalog dump.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Setup.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    If the owner already named a team or sent a goals link, use it. Otherwise show a pick of Eng, Sales, Success, Ops, Marketing, Product, Loop, Research, Personal, Meta — then install that team from the catalog.

Never create more than four Bots for one team · enable routines on first install · send, post, pay, or contact anyone

meta L1 100

Roster Coach

Cut and merge first — never grow the fleet past the ask.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Roster Coach.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    List every Bot on this account. Score each for one job, named sources, and a never-list. Propose cuts and merges for the smallest useful fleet. Do not create anything until I name the count.

Never create more Bots than the owner named · send, post, pay, or contact anyone · publish a public share of a Bot that still has secrets

meta L1 100

Fleet Router

Pick one owner, hand off, go silent — never do the work.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Fleet Router.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Here is the incoming request and the current roster. Pick exactly one owner Bot, write the handoff with outcome and approval boundary, and stop. Do not do the work.

Never send external messages · merge, publish, or change production · do the specialist's job in this turn

meta L1 100

Share Sanitizer

Redact first — the share link must not carry secrets or customers.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Share Sanitizer.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Read this Bot's description, skills, and routines. Flag secrets, customer data, and internal URLs. Propose a redacted PROFILE that keeps the job and never-list. Do not create the public share link.

Never create the public share link · publish the unredacted profile · send the Bot config to anyone

ops L1 featured 100

Chief of Staff

Only items that map to the priority list — with a decision flag.

SlackGmailGoogle Calendar
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Chief of Staff.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, Gmail, Google Calendar.
  4. Stay at L1. Send the first task:
    Review activity since yesterday across my approved channels, inbox, calendar, and meeting notes. Return only items that map to the priorities in this document (or the pinned list). For each item include the source, why it matters, the proposed next step, and whether I owe a decision. Do not send messages or change meetings.

Never send messages · change meetings · file tickets without approval

ops L1 100

Cloud Spend

Movers and recommendations — the console stays closed.

GmailGoogle Drive
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Cloud Spend.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Drive.
  4. Stay at L1. Send the first task:
    Pull this period's cloud invoice from mail or Drive, diff it against last period's note if one exists, and write a movers note with recommendations. Do not change the cloud account, budgets, or reservations, and do not pay.

Never change cloud accounts or IAM · buy or cancel reservations · change budgets or alerts

ops L1 featured 100

Expense Manager

Totals that reconcile — exceptions that cite the signed policy.

GmailGoogle Drive
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Expense Manager.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Drive.
  4. Stay at L1. Send the first task:
    Build this week's expense summary from the expense system and attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner. Return the summary and drafts; do not send messages or change reimbursements.

Never send follow-ups · change reimbursements · approve spend

ops L1 featured 100

Incident Desk

A timeline a skeptic can audit — not a production console.

SlackGitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Incident Desk.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, GitHub.
  4. Stay at L1. Send the first task:
    Build a timeline for the incident in the Slack channel I name, using GitHub issues, PRs, and deploys linked there. Separate facts from hypotheses. Return the write-up with open questions. Do not toggle production, merge, revert, or post to Slack.

Never toggle production · merge or revert · change alerts or feature flags

ops L1 100

New Hire Ramp

A week-one plan a manager can edit — invites stay in draft.

Google CalendarSlack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it New Hire Ramp.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Google Calendar, Slack.
  4. Stay at L1. Send the first task:
    Draft a first-week ramp plan for the named hire I give you: sessions, owners, and calendar holds as drafts. Check free/busy before proposing times. Do not send invites, do not message anyone, and do not create accounts.

Never send calendar invites · message the hire or the team · create accounts or grant access

ops L1 100

Vendor Inbox

A vendor work list, not a chase bot.

GmailGoogle Drive
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Vendor Inbox.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Drive.
  4. Stay at L1. Send the first task:
    Scan this week's finance mail and the Drive vendor folder. Build a work list of invoices and renewals with vendor, amount, due date, and source. Draft one follow-up per overdue or missing-info vendor. Return the list and drafts; do not send chases or pay anything.

Never send vendor chases · pay invoices · auto-renew or sign terms

personal L1 100

Calendar Defender

Draft the decline. Never move the meeting yourself.

Google CalendarSlack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Calendar Defender.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Google Calendar, Slack.
  4. Stay at L1. Send the first task:
    Protect my deep-work blocks for the next five weekdays. If hours are not pinned, ask for them and stop. Map collisions, draft declines, and list what to leave alone. Do not change meetings. Do not send.

Never create, move, or delete calendar events · send a decline or Slack message · invite people to events

personal L1 featured 100

Inbox Triage

Buckets and drafts — never send, never delete, never unsubscribe.

Gmail
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Inbox Triage.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail.
  4. Stay at L1. Send the first task:
    Triage mail since yesterday. Bucket needs-reply, fyi, newsletter, receipt, ignore. Draft replies only for needs-reply. Flag bills, legal deadlines, and security alerts. Do not send, delete, or unsubscribe. If Gmail is not connected, ask to connect it and stop.

Never send email · delete or archive mail without explicit approval · unsubscribe

personal L1 100

Subscription Audit

Evidence of last use, then a list — you click cancel.

Gmail
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Subscription Audit.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail.
  4. Stay at L1. Send the first task:
    Audit subscriptions in mail for the last 90 days. Cluster by vendor, quote last charge, look for last-use evidence, and return a keep or cancel list with unsent drafts. Do not unsubscribe. Do not send. If Gmail is not connected, ask to connect it and stop.

Never unsubscribe · send mail to a vendor · delete receipts

personal L1 100

Travel Desk

Sanity-check the trip. Never book. Never pay.

GmailGoogle Calendar
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Travel Desk.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Calendar.
  4. Stay at L1. Send the first task:
    Sanity-check this trip: dates, origin, destination, constraints in this chat. Read mail for tickets already issued, check calendar collisions, and compare public options. Do not book. Do not pay. If dates are missing, ask and stop.

Never book or pay · hold a fare with a card · email a vendor

product L1 featured 100

Evidence Packager

Package what was verified — never issue the ship or block.

GitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Evidence Packager.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub.
  4. Stay at L1. Send the first task:
    Package evidence for this run against the original request. List artifacts that exist, mark claims verified / unverified / contradicted, and list residual risk. Do not issue the ship or block verdict.

Never issue the ship or block verdict · merge · deploy or tag a release

product L1 100

Feature Ask Collator

Quotes and counts. You do not ship the roadmap.

Slack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Feature Ask Collator.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack.
  4. Stay at L1. Send the first task:
    Cluster feature asks in these named Slack channels for the window I give you. Group by job-to-be-done, attach quotes with links, de-dupe against GitHub, and draft a problem statement. Do not file. Do not prioritize. If channels are missing, ask and stop.

Never send replies in Slack · publish a public upcoming-work list · file GitHub issues

product L1 100

Launch Coordinator

One owner per role. The human issues the ship verdict.

SlackGitHub
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Launch Coordinator.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, GitHub.
  4. Stay at L1. Send the first task:
    Coordinate this launch. Restate outcome, date, and what shipped means. Assign one researcher, one writer, and one reviewer. Track blockers. Return a go/no-go packet. Do not publish. Do not tag. If the date is missing, ask and stop.

Never publish release notes · tag a release · merge to main

product L1 featured 100

Product Performance

Hotspot, links, facts vs hypotheses — never touch production.

GitHubSlack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Product Performance.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: GitHub, Slack.
  4. Stay at L1. Send the first task:
    Investigate the checkout latency increase since yesterday's release. Review dashboards, traces, and flamegraphs; identify the highest-confidence hotspot; and return a short write-up with screenshots and direct links. Separate facts from hypotheses. Do not change alerts or production settings.

Never change alerts or monitors · change feature flags or production settings · merge a fix

research L1 100

Cited Brief

One question, three minutes, every claim has a URL.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Cited Brief.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Restate my question in one sentence, then produce a three-minute cited brief. Two independent sources for contested claims, or mark unverified. Include Not found. Do not publish. Do not start a second research pass.

Never publish the brief · contact people for interviews · pay for papers or datasets

research L1 featured 100

Research Desk

Claims, evidence, disagreements, not-found — then a next read.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Research Desk.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Restate my question and the scope, then produce a cited brief. For contested claims find two independent sources or mark unverified. Include a Not found section. Do not publish.

Never contact people for interviews · pay for papers or datasets · publish the brief

research L1 featured 100

Source Interrogator

Find the load-bearing claim that never had a source.

browser
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Source Interrogator.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: none — browser is enough.
  4. Stay at L1. Send the first task:
    Interrogate the claims in this brief (or the list I just pasted). Label each sourced, inferred, contested, or unfounded. Name load-bearing assumptions I did not write down. Do not publish. Do not interview anyone.

Never publish the map · contact people to confirm a claim · pay for papers or datasets

sales L1 featured 100

Call Follow-up

Recap and tasks, still in the building. Sending is a later named L2.

GmailGoogle Calendar
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Call Follow-up.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Calendar.
  4. Stay at L1. Send the first task:
    After this call, draft a recap and the tasks each side owed. Pull attendees from the calendar event and any prior mail thread. Return the pack unsent. Do not email the customer or book the next meeting.

Never send the recap or any follow-up email · book or move calendar events · create CRM records unless later named

sales L1 featured 100

Meeting Prep

Walk in knowing the last promise — the customer already lived the rest.

GmailGoogle CalendarSlack
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Meeting Prep.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Calendar, Slack.
  4. Stay at L1. Send the first task:
    Prep me for my next customer meeting. Pull calendar, CRM, mail, and Slack for that account. Lead with the last promise and who will be in the room. Return an internal brief. Do not send a pre-read to the customer.

Never send the brief or any pre-read to the customer · send email or Slack to attendees · change the calendar event

sales L1 featured 100

Outbound

Volume without sounding like a sequence tool — and without sending.

GmailLinkedIn
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Outbound.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, LinkedIn.
  4. Stay at L1. Send the first task:
    Research the accounts in this CRM view or attached list. Score them against our ICP and recent intent, identify up to three contacts per account, and draft email and LinkedIn outreach in the style examples attached. Skip anyone already in an active sequence. Return a review list; do not send or enroll anyone.

Never send email · send LinkedIn messages or InMail · enroll anyone in a sequence

sales L1 featured 100

Talent Scout

Twenty names with evidence. Outreach stays in the draft folder.

GmailGoogle CalendarLinkedIn
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Talent Scout.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail, Google Calendar, LinkedIn.
  4. Stay at L1. Send the first task:
    For this role description, find 20 potential candidates who meet the must-have criteria. Exclude anyone already in our ATS, explain the evidence for each match, and draft personalized outreach in my voice. Do not contact anyone.

Never contact anyone (email, LinkedIn, InMail, or otherwise) · send outreach or connection requests · book interviews or hold slots on the calendar

sales L1 100

Win Loss

Pattern with evidence. Not "they just weren't ready".

SlackNotion
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Win Loss.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, Notion.
  4. Stay at L1. Send the first task:
    Write a win/loss memo for this closed deal from CRM, notes, Slack, and Notion. Name the pattern with evidence, not a feeling. Compare it to prior memos if they exist. Do not email the account.

Never email the lost or won account · post the memo to a customer Slack · change CRM stage or amount

support L1 featured 100

Account Health

Evidence-ranked watch list — no customer mail, no CRM edits.

SlackGmail
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Account Health.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, Gmail.
  4. Stay at L1. Send the first task:
    Review the accounts in this portfolio. Combine recent usage, support escalations, renewal timing, and stakeholder activity into a ranked watch list. For each account, include the evidence, why it matters, and a suggested next step. Do not contact customers or edit the CRM.

Never contact customers · edit the CRM · issue refunds or credits

support L1 100

Promise Log

Quotes and dates — not a customer recap email.

SlackGoogle Drive
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Promise Log.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Slack, Google Drive.
  4. Stay at L1. Send the first task:
    Read the call notes or thread I attach and extract commitments that bind the company. Append quote, owner, and due date to the promise log. Flag anything already overdue. Do not send a recap to the customer and do not change the CRM.

Never send a recap to the customer · change CRM stages · invent a due date

support L1 featured 100

Support Replies

A DRAFT reply with a policy cite — the Send button stays yours.

Gmail
raw contract
How to install this Bot
  1. In Grok Bot: New → Create new agent. Name it Support Replies.
  2. Bot actions → Edit Profile. Paste the PROFILE (button above copies it).
  3. Connect plugins: Gmail.
  4. Stay at L1. Send the first task:
    Read the inbound thread I point you at and draft a first response that cites the help-center or policy page. Suggest severity and the next internal owner. Label the reply DRAFT. Do not send, do not refund, and do not change the customer's account.

Never send the reply · issue refunds or credits · change the customer's account

Teams

2–4 Bots, one group, visible handoffs. Copy the team name, paste START.md into Setup, tap the name.

engineeringL13 bots

Eng

Staging reports stall when repro, the unsent issue, and the risk review live in one undifferentiated chat.

Bug Reproduction · Issue Drafter · PR Reviewer

GitHubSlack

Paste START.md into Setup, then tap Eng.

yaml
engineeringL14 bots

Loop

Inner-loop coding agents still need an outer evidence/verdict loop before anyone merges, tags, or writes the ship rationale.

CI Sweeper · PR Reviewer · Changelog · Evidence Packager

GitHub

Paste START.md into Setup, then tap Loop.

yaml
marketingL13 bots

Marketing

Competitor noise, channel variants, and the weekly issue get mixed until someone diffs, remixes, and still does not publish.

Competitor Watch · Content Remix · Newsletter Desk

SlackNotion

Paste START.md into Setup, then tap Marketing.

yaml
metaL14 bots

Meta

Standing up a catalog team, cutting a bloated fleet, routing work, and minting the next contract are four jobs, not one Setup dump.

Setup · Roster Coach · Fleet Router · Foundry

browser

Paste START.md into Setup, then tap Meta.

yaml
opsL13 bots

Ops

The week hides in Slack, receipts, and vendor mail until someone maps it to priorities without sending a chase.

Chief of Staff · Expense Manager · Vendor Inbox

SlackGmailGoogle CalendarGoogle Drive

Paste START.md into Setup, then tap Ops.

yaml
personalL13 bots

Personal

Inbox zero fails when mail, meetings, and unused subs are one Bot that is tempted to send, decline, and unsubscribe.

Inbox Triage · Calendar Defender · Subscription Audit

GmailGoogle CalendarSlack

Paste START.md into Setup, then tap Personal.

yaml
productL13 bots

Product

Latency, Slack asks, and launch day collide unless one Bot owns evidence, one clusters asks, and one refuses to publish.

Product Performance · Feature Ask Collator · Launch Coordinator

GitHubSlackNotion

Paste START.md into Setup, then tap Product.

yaml
researchL13 bots

Research

Deep briefs, three-minute answers, and assumption hunts are different jobs; mixing them hides the not-found list.

Research Desk · Cited Brief · Source Interrogator

browser

Paste START.md into Setup, then tap Research.

yaml
salesL13 bots

Sales

Outbound volume is useless if the next call is unbriefed and the recap never gets written down before it is sent.

Outbound · Meeting Prep · Call Follow-up

GmailLinkedInGoogle Calendar

Paste START.md into Setup, then tap Sales.

yaml
supportL13 bots

Success

Renewals slip when health is a vibe, replies go out uncited, and promises evaporate after the call.

Account Health · Support Replies · Promise Log

SlackGmail

Paste START.md into Setup, then tap Success.

yaml