Grokbot TemplatesGrokbot Templates
Todos los casos de uso

Trabajo

Tip only: split always-on bots by domain; turn functions into shared skills

Role-chart fleets (CoS / Strategist / Researcher / Reviewer…) solve org charts — not context integrity or maintenance cost.

Compartir

Qué dolía

Simon Lin (@SteamedBun1111) argued that official-style role-based Grok Bot teams (7–8 bots) fit division of labor, not always-on clusters. Role handoffs compress context; every global rule must be synced bot-by-bot. Tip-only checklist — no invented prompt. Not affiliated with xAI.

Qué instalar o crear

Split bots by domain/project end-to-end. Encode research/design/analysis/etc. as shared skills. Coordinate via shared state (roster + workspace), not lossy chat handoffs.

Bots

  • Domain owner

    Owns one line of work from intake to delivery in a single context; edits only its roster row.

Plugins

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

Archivos

  • Shared roster (scope per bot) + persistent workspace the next bot can read directly.

Rutinas

  • Ninguna en el primer uso. Mira primero una pasada manual.

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/SteamedBun1111/status/2106542096458940794 (credit @SteamedBun1111).
  2. 2List your always-on jobs by domain/project — not by job title (research vs review).
  3. 3Give each domain one bot that owns intake → delivery so preferences and rejected paths stay in one context.
  4. 4Turn repeated functions (research, design, analysis, presentation, prototype) into shared skills reused across bots — not extra headcount.
  5. 5Put scope in a shared roster (each bot edits only its row) plus a workspace the next bot can read; avoid compressing tradeoffs into chat handoffs.

Valla de aprobación

No auto-send. You still approve publish/spend; this tip only changes how you split seats.

Qué ajustar

Steal the three-line rule: domain bots, shared skills, shared state — especially when the cluster stays on every day.

Fuente

Simon Lin @SteamedBun1111 · 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