Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Bots decide; scripts repeat; verifier checks — stop burning tokens on rehearsal

Routines re-reason the same commands and burn tokens every wake.

Share

What hurt

@Solomonrojie shares a SpaceXAI-style split: lead Bot decides and handles exceptions; scripts collect/transform/check; a verifier checks the deliverable. Judgment only at plan→execute, unclear failures, and before external actions. Author-quoted refactor prompt keeps BRIEF.md, file logs, and approval before send/publish/delete. Not affiliated with xAI.

What to install or create

Paste refactor prompt → review proposed split → scripts + BRIEF.md + verifier → approve before routine.

Bots

  • Lead bot

    Defines the task, approves approach, handles exceptions.

  • Verifier bot

    Checks deliverable against brief and test results.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • None on the first run. Watch one manual pass first.

The prompt

Refactor workflow: bots decide, scripts repeat (author-quoted)

Quoted from @Solomonrojie — as published. Do not invent a second system prompt.

Refactor this recurring workflow so scripts handle repeatable operations and Bots handle decisions:

1. Inspect the current process. Identify deterministic steps, judgment calls, required access, and the finished result. Show me the proposed split before changing anything.

2. Create BRIEF.md with the goal, inputs, acceptance checks, and approval boundaries. Turn stable operations into reusable scripts. Save detailed logs to files and return concise summaries.

3. Where I control the executor, propose filesystem and network restrictions for commands and self-hosted MCP servers. Test an allowed action and a deliberately blocked action. Report anything the environment cannot enforce.

4. Use a separate verifier when an independent check is useful. Give it the brief and evidence. Preserve successful steps, stop after two failed repair attempts, and report what remains unresolved.

Show me the changes and one completed test run before enabling a routine.

First run

  1. 1Read https://x.com/Solomonrojie/status/2114128321449693673 (credit @Solomonrojie).
  2. 2Pick one recurring workflow that re-explains the same steps every run.
  3. 3Paste the author-quoted refactor prompt.
  4. 4Review the proposed bot/script split and BRIEF.md before any change.
  5. 5Require one completed test run — then your yes — before scheduling a routine.

Approval fence

Show proposed split and one test run before enabling a routine; approve send/publish/delete/production changes.

What to tweak

Steal the split: bots for decisions, scripts for repetition, you for consequential actions.

Source

Solomon Rojie @Solomonrojie · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro