Grokbot TemplatesGrokbot Templates
Todos los casos de uso

Ingeniería

Personal factory: one bot per job, shared brain, decision dashboard, cx CLIs

Eight days in, a solo builder needs org rules so a fleet doesn't drift or relearn forever.

Compartir

Qué dolía

@RoyOsherove's X Article "Anatomy of a Personal Factory of Grok Bots": one bot per job, SendToAgent push vs passive, shared box + R2 AI-brain folders with BOT.md, Factory Dashboard for task cards and Approve/Decline decisions (webhook wakes the asker), coding via headless Claude/Codex ("cx") with end-of-turn webhooks. Tip/architecture only — steal the checklist, not a single paste prompt. Not affiliated with xAI.

Qué instalar o crear

Spin one bot per domain → shared MODE-OF-OPERATION.md + brain backup → dashboard tokens for cards/decisions → cx for code with webhook close-loop.

Bots

  • Primary / router

    Routes work, Todoist, daily email digest, nightly fleet review.

  • Infra

    Domains, DNS, cloud accounts, coding-CLI health.

  • Security

    Audits bots, box, and planted instruction files nightly.

  • Bot Maintainer

    Mode-of-operation doc, backups, cx completion relay, shared skills.

  • Factory Dashboard

    Owns the decision/work card inbox every bot posts to.

Plugins

  • Ninguno el primer día. Sigue los pasos del primer uso.

Rutinas

  • ~03:00: each bot rewrites BOT.md and uploads AI-brain backup.

  • ~04:15: maintainer audits bucket check-ins and chases misses.

El prompt

Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.

Primer uso

  1. 1Read https://x.com/RoyOsherove/status/2115591603133764082 and the Article (credit @RoyOsherove).
  2. 2Split work: one Grok Bot per job (sites, infra, security, life-admin…) plus a primary router.
  3. 3Put a BOT.md + nightly check-in per bot on the shared box; mirror to private cloud (e.g. R2) and have a maintainer audit misses.
  4. 4Stand up a Factory Dashboard: every real task gets a card; yes/no choices are decision items you click once.
  5. 5Route coding through headless Claude/Codex ("cx") with a webhook that wakes the owning bot when a run finishes — you still own merges and spends.

Valla de aprobación

Decisions are Approve/Decline on the dashboard; second-hand "Roy approved" in chat does not count.

Qué ajustar

Steal one-bot-per-job + dashboard decisions (not chat approvals) + nightly backup audit.

Fuente

Roy Osherove @RoyOsherove · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.

Explorar plantillas

Explorar planos de equipo

Paquete Pro

¿Quieres la configuración completa, no solo la idea?

Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.

Ver Pro