Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Shared second brain: ABOUT, BRIEF, wiki, skills, HANDOFF

Reloading the whole chat to reuse yesterday's work burns tokens for nothing.

Share

What hurt

@Brankotrcek's second-brain setup for Grok Bot: keep working chat short; store reusable knowledge in shared files (ABOUT.md, BRIEF.md, raw/, wiki/, RULES.md, skills/, HANDOFF.md); route reuse/refresh/investigate (optionally via JEV); retrieve sections instead of loading everything. Author-quoted rebuild prompt included. Not affiliated with xAI.

What to install or create

Short chat · shared files · retrieve sections · optional JEV routing · handoff between bots.

Bots

  • Working bot

    Retrieves relevant files, does the work, updates wiki/handoff.

  • Optional router

    Chooses reuse / refresh / investigate with confidence.

Plugins

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

Files

  • ABOUT.md, BRIEF.md, raw/, wiki/, RULES.md, skills/, HANDOFF.md

Routines

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

The prompt

Rebuild around a shared second brain (author-quoted)

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

Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.

Rebuild my workflow around a shared second brain:

→ Review one recurring task and identify what I keep explaining or researching again.

→ Separate lasting knowledge from changing facts. Save reusable findings with sources and dates; check live information when the task needs it.

→ Keep the current brief and handoff short. Retrieve relevant passages instead of loading every file.

→ If JEV is connected, use it for defined routing decisions: reuse, refresh, or investigate. Escalate uncertain cases rather than forcing a choice.

→ Give each task one owner. Pass confirmed findings between bots so they don’t repeat the same research.

→ Preserve completed steps when something fails. Try one focused correction, then stop and report anything unresolved.

Show me the proposed files and one test task before scheduling routines.

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

First run

  1. 1Read https://x.com/Brankotrcek/status/2113789932946829365 (credit @Brankotrcek).
  2. 2Paste the author-quoted rebuild prompt and review the proposed file layout.
  3. 3Create ABOUT.md, BRIEF.md, raw/, wiki/, RULES.md, skills/, HANDOFF.md as agreed.
  4. 4Pick one recurring task and run it retrieving sections only — not the whole brain.
  5. 5Schedule routines only after the test task looks right.

Approval fence

Show proposed files and one test task before scheduling routines.

What to tweak

Steal the rule: next run inherits the work, not the entire conversation.

Source

Branko Trček @Brankotrcek · 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