All use cases

Work

Nine bots, clear roles, written rules, and a human in charge

A pile of bots without roles turns into noise instead of an org.

Share

What hurt

Alan (@alanhoward) runs nine Grok Bots the way he'd want any org to run agents: clear roles, written rules, human in charge. Jarvis (ops) keeps the rest in line; Max scans X and sends reply/post ideas at 3am; Lena drafts; others on the roster include Rhea, Dash, Piper, June, Theo, and Ellis. Max finds posts and drafts proposed replies for cyber/AI GRC framing — Alan still decides. Not affiliated with xAI.

What to install or create

Name roles → write rules → ops bot herds → human approves outbound.

Bots

  • Jarvis

    Operations lead; keeps other bots in line.

  • Max

    Scans X; sends reply and post ideas (e.g. 3am).

  • Lena

    Drafts copy for your review.

Plugins

  • X

    Optional

Routines

  • None on the first run. Watch one manual pass first.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/alanhoward/status/2111589426589749681 (credit @alanhoward).
  2. 2List the jobs you need and name one bot per role (ops, scout, drafter, …).
  3. 3Write short rules each bot must follow, including what they never do alone.
  4. 4Have the scout draft replies in your framing; you post only after review.

Approval fence

Proposed replies stay drafts until you post.

What to tweak

Steal role cards + ops lead + human sign-off on replies.

Source

Alan 🇦🇺 @alanhoward · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro