Grok Bots Directory
Submit a Grok Bot

Grok Bot playbooks

A playbook is a routine a Grok Bot runs end to end. Each page explains the routine, names the original bot, and lists the templates that do the same job.

  1. 01

    Land first, sample aftermerge on proof, review later

    @poteto

    Land first, sample after is lauren's (@poteto) routine for code review at scale. Agents merge their own PRs once verifiers and CI pass, and she reads what landed the next morning.

  2. 02

    Chief of staffthe one Grok Bot you talk to, layers that delegate

    @poteto

    A chief of staff Grok Bot is the one bot you talk to in a layered bot team. For a big project you plan with it, and each layer below splits the work further until Cursor cloud agents do it.

  3. 03

    Poteto modeverification is the infrastructure

    @poteto

    Poteto mode is lauren's (@poteto) way of working with agents. You set up the environment well enough that you can trust their work when you are not watching, and a job is done when it is verified, not when it looks finished.

  4. 04

    Gardenermake each repeated mistake impossible

    @poteto

    A gardener is a routine that keeps a codebase clean while agents write most of it. It watches what lands. When the same mistake shows up again, it changes the repo so the next agent cannot make it.

  5. 05

    Dr Eggbota bot that designs your other bots

    @poteto

    Dr Eggbot is a routine for building Grok Bots. You describe a job, and a bot designer builds the bot for you.

  6. 06

    Haggle Botfind the savings, draft the counter

    Haggle Bot is a routine for renewals. It reads what your company actually spends, finds the money on the table, and drafts the counter, but never sends, signs, or spends without you.

  7. 07

    tinkabotwrap an API as a plugin

    @poteto

    tinkabot is a routine for packaging. Point it at an HTTP API and it comes back as an installable plugin with skills, not a pile of files.

  8. 08

    Atelierone look for every piece

    @arni0x9053

    An atelier is a routine for visual work. You pick one look once, and every piece you need is cut from that look.

  9. 09

    Bennytriage, reproduce, then fix

    @poteto

    Benny is a routine for bug reports. Each report moves down a line of triage, repro, and fix, and any stage can stop it.