All use cases

Personal

Two lists: cloud Grok Bot for accounts, local model for private drafts

Not everything belongs in the cloud — private drafts and sensitive files should stay local.

Share

What hurt

ShareGrokBots (@ShareGrokBots), crediting @priddysharp, posted a five-step split: list work that touches your accounts vs work that must never leave the machine; give cloud Grok Bot the first list; keep the second on a local model; write a stop-and-hand-off rule into the bot; review the split after a week. Not affiliated with xAI.

What to install or create

Two lists → cloud vs local → stop rule → weekly review.

Bots

  • Cloud lane

    Email, calendar, research, cross-app work only.

Plugins

  • Gmail

    Optional

  • Calendar

    Optional

Routines

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

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/ShareGrokBots/status/2111232278147846615 (credit @ShareGrokBots, idea @priddysharp).
  2. 2Make two lists: account-touching work vs never-leave-the-machine work.
  3. 3Give cloud Grok Bot only the first list.
  4. 4Add a standing rule: if a task hits the private list, stop and hand off to local.
  5. 5After a week, move anything that was in the wrong bucket.

Approval fence

Hand-offs to local are automatic; you decide what stays on the private list.

What to tweak

Steal the private-list stop rule before you connect another app.

Source

ShareGrokBots.com @ShareGrokBots · 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