Grokbot TemplatesGrokbot Templates
All use cases

Content

Lead bot only triages; specialists touch the screen

A mega lead bot that both routes and executes becomes the bottleneck and the risk.

Share

What hurt

まどさん (@madogiwacowork) runs Grok Bot as a personal AI-employee org for content + work ops. Stealable spine: the lead bot does NOT give advice itself — it only triages to specialists (career, side hustle, writing, images, video); cross-domain asks go to a roundtable; principle: the lead never touches the screen — operator seats do. Weekly stack: weekday 10-min mutual-engagement queue (candidates + 2–3 line summaries; human replies — no auto-reply); biweekly infection-status HTML pack from a public X list → approve → PPT; X long-form calendar finish day-before / publish only from X app; Slack bridge for draft handoffs; skills for 5-reviewer content loop + 5:2 article thumbnails. Tip/architecture with optional shared template — no invented system prompt.

What to install or create

Lead = triage + roundtable only. Specialists own screen work. Publish and replies stay human-gated.

Bots

  • Lead (triage only)

    Route to specialists or roundtable. Never touches the screen.

  • Specialist seats

    Career / side hustle / writing / images / video — execute after triage.

Plugins

  • X

    Optional

  • Browser

    Optional

Files

  • Weekday engagement queue summaries (2–3 lines each) for human reply.

Routines

  • Weekday ~10 min: mutual-engagement queue candidates + short summaries; you reply.

  • Biweekly: public X list → infection-status HTML → your approve → PPT share.

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/madogiwacowork/status/2100001127505031314.
  2. 2Create a lead bot whose only job is triage + roundtable — ban screen use in its description.
  3. 3Stand up specialist bots for the domains you actually run (writing, images, etc.).
  4. 4Add one weekday engagement-queue routine that drafts candidates + 2–3 line summaries; you reply.
  5. 5Keep publish / auto-reply off; optional shared template link is in the source tweet if you want the full desk.

Approval fence

No auto-reply on engagement queue. X publish only from the app after you approve. Spend/send behind your yes.

What to tweak

Steal lead-never-touches-screen. Routing is not execution.

Source

まどさん @madogiwacowork · 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