Todos los casos de uso

Contenido

Lead bot only triages; specialists touch the screen

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

Compartir

Qué dolía

まどさん (@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.

Qué instalar o crear

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

    Opcional

  • Navegador

    Opcional

Archivos

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

Rutinas

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

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

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/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.

Valla de aprobación

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

Qué ajustar

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

Fuente

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