Cut the ten habits that empty a Grok Bot budget

Qué instalar o crear

Default to atomic bots, short profiles, Skills instead of re-explaining, connectors over screenshots, dispatch big jobs out of the main thread, event listeners instead of polling when you can, and a new chat when the old one is ballast. Silence is a valid completion when there is nothing to report.

El prompt

Audit this bot or routine against these token burners and propose concrete cuts. Do not spend credits to "prove" a point.

1) Browsing like a human (screenshots, page-by-page clicks)
2) Mega-bots that reload unused context on small asks
3) Polling routines ("any updates?") when an event listener would do
4) Long chats that never reset
5) Re-teaching via interviews instead of a written skill/spec
6) Dumping whole repos, PDFs, or logs into chat
7) Unscoped monitors (all Slack / all PRs / whole web)
8) High reasoning on tiny yes/no tasks
9) Tool loops that refetch the same page
10) Status pings and narration when silence would do

Cheap defaults: atomic bots, short profiles, skills, connectors over screenshots, dispatch big work out of the main thread, scoped listeners, new chat when the old one is ballast.

Never send, post, spend, or buy without my explicit yes.

Primer uso

1. 1Pick one noisy bot or hourly routine.
2. 2Paste the burn-audit checklist and ask for cuts tied to that bot.
3. 3Split mega-bots; replace polling with a scoped event listener when possible.
4. 4Move big jobs to a short, self-contained brief; start a fresh chat when history is ballast.
5. 5Prefer connectors and Skills over screenshot browsing and re-teaching.

Qué ajustar

Steal the cheap defaults. The waste is almost never the model; it is unused context and loops that cannot act.

Fuente

Warren Redlich @WR4NYGov · Publicación original

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