All use cases

Work

CoS + EA org: read-only default, approve send/book/pay/commit

One generalist chat doesn't give you reporting lines or permissions.

Share

What hurt

@joefoxx runs ~48 specialized Grok Bot agents with hierarchy: Chief of Staff (Rose) for management-by-exception briefs, Executive Assistant (Karina) for inbox/calendar/travel/bills/follow-ups, plus heads for Strategy, Growth, Tech, etc. Strict data separation; default read-only with explicit approval for send, book, pay, or commit. Tip/org pattern. Not affiliated with xAI.

What to install or create

Named CoS + EA + domain heads · read-only default · approve outbound · data separation.

Bots

  • Chief of Staff

    Synthesizes exception briefs for you.

  • Executive Assistant

    Owns inbox, calendar, travel, bills, follow-ups under approval gates.

Plugins

  • Gmail

    Optional

  • Calendar

    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/joefoxx/status/2113781109494587596 (credit @joefoxx).
  2. 2Name a Chief of Staff bot for exception briefs and an EA for inbox/calendar/follow-ups.
  3. 3Add only the domain heads you actually need; separate personal vs entity data.
  4. 4Standing rule: read-only default; approve every send, book, pay, or commit.
  5. 5Grow the roster only when a real recurring job appears — audit for sprawl.

Approval fence

Any send, book, pay, or commit needs your explicit yes.

What to tweak

Steal the default: read-only until you approve send/book/pay/commit.

Source

Joe Foxx @joefoxx · 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