Todos los casos de uso

Trabajo

Each prompt eats 1% of usage? Check your lead bot's transcript

When one lead bot handles everything, every prompt pays to reread its huge history.

Compartir

Qué dolía

Ken (@Ken_LinkWell) found every prompt was costing about 1% of his usage. The cause: his lead bot had a massive transcript because everything went through him. He shared the four-step fix. Not affiliated with xAI.

Qué instalar o crear

Recreate the lead bot fresh and keep the old one as an archive, rebuild its routines, move most of them to the specialist bots that own the jobs, and leave the lead with only a few: morning brief, nightly wrap, and his assessment webhooks.

Bots

  • Lead bot (rebuilt)

    Keeps only the morning brief, nightly wrap, and a few webhooks.

  • Specialist bots

    Own the routines for their own jobs.

Plugins

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

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/Ken_LinkWell/status/2107063418645807437 (credit @Ken_LinkWell).
  2. 2Check how much usage a simple prompt to your lead bot costs, and how long its chat history is.
  3. 3If it is huge, create a fresh lead bot and park the old one as an archive.
  4. 4Rebuild its routines, moving each one to the specialist bot that owns that job.
  5. 5Leave the lead with two or three routines (e.g. morning brief, nightly wrap) and re-check usage per prompt.

Valla de aprobación

Archive, don't delete, the old lead bot until the new setup has run cleanly for a while.

Qué ajustar

Keep the hub thin. Work and routines live with the bot that owns the job.

Fuente

Ken @Ken_LinkWell · 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

Routine cost control: stop running out of usage by Wednesday

A one-hour audit, a quiet Usage officer and a fix playbook (cadence, silence, event triggers, fresh chats, scripts over clicks) that cut waste without losing the jobs your bots do.

Ver el paquete de configuración