Grok Bots Directory
Submit a Grok Bot

Dr Eggbot: a bot that designs your other bots

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

Start with the original

dr eggbot by lauren

lauren (@poteto) calls dr eggbot her bot that helps you create high quality bots, and shared it from her own account with one line: "pov u installed dr eggbot". Its job is designing Grok Bots directly: a few preference questions, then CreateAgent, then a check against the live profile. In her pstack guide she suggests asking it for an engineer bot that creates a verification skill, plus a daily routine that maintains it.

Coding bots it designs follow the poteto-mode bar. Non-coding bots get one job, one voice, and explicit anti-jobs. On first run it sets up pstack and the two standing healthchecks, and it never creates anything from a healthcheck report until you pick. The directory also lists the same bot shared by another account; this page links lauren's own share.

More templates by lauren (@poteto)

The playbook

The playbook is designing other Grok Bots. You tell a bot designer what job you want covered. It asks a few preference questions, writes a tight persona, and creates the new bot in your account.

The design bar is narrow on purpose. A coding bot gets the poteto-mode bar: one job, unslopped, verified, with pstack for coding. A non-coding bot gets one job, one voice, explicit anti-jobs (the things it never does even when asked), and no leftover tools. A drafter does not send. A mentions scout does not post, and stays quiet when there is nothing to say. The designer creates the bot itself and does not default to a shareable template.

How a Grok Bot runs Dr Eggbot

  1. Ask a few questions

    Only the preferences that shape the bot: its one job, what it must never do, its voice, and whether it wakes on demand, on a routine, or both.

  2. Write the persona

    CreateAgent takes only a name and a description, so the description is the whole persona: the job, the anti-jobs, and the voice, with nothing padded.

  3. Create it with CreateAgent

    The designer creates the bot directly instead of handing you text to paste.

  4. Verify it

    It reads the live profile back. Stricter versions also give the new bot one real task and one it should refuse before handing it over.

  5. Keep the fleet healthy

    Two standing checks run on your bots: a weekday transcript scan for friction and a Monday routine audit for wasted tokens. Both stay quiet when there is nothing to propose.

Inspired templates8

These templates list designing other Grok Bots as their own job in their title, profile, skills, or memory. Bots that only hand work to Dr Eggbot, or only mention it in a post, are not listed.

dr eggbot

Designs high-quality Grok Bots. Asks a few preference questions, then creates them. Coding bots get the poteto-mode bar; non-coding bots get one job, one voice…

  • Memories8
  • Skills3
  • Routines0
Tamago

品質の高い Grok Bot を設計し作成する担当です。人に見せる日本語には faithful-japanese を常時適用し、作成する Bot にも同じ基準を入れます。

  • Memories4
  • Skills2
  • Routines2
Hatch

Designs high-quality Grok Bots. Asks a few preference questions, then creates them with CreateAgent. Coding bots get poteto-mode; others get one job, one voice…

  • Memories10
  • Skills2
  • Routines2
Bot Builder

Designs focused Grok Bot fleets (CoS + specialists), crawl→walk→run, and a Sunday skill/roster back-check — for owners who want specialized bots instead of one…

  • Memories3
  • Skills3
  • Routines1
GrokBot Builder

GrokBot Builder

by

Brainstorms specialist Grok Bots with you, then creates them with a clear job, approval boundaries, and starter habits — idea to working teammate in one chat.…

  • Memories2
  • Skills1
  • Routines0

More playbooks

All playbooks