Guides

How to use it

Longer walkthroughs, with numbered steps and a series when one is set.

Showcase

  1. Part 1. Five weekly AI builds you can copy this week

    Steal one recurring job from this Thursday showcase: client recaps, NDA filing, morning loose ends, Canvas grading, or a family meal plan.

Run a fleet of Bots

  1. Part 1. One job per Bot, or one Bot for everything? How to decide

    Cursor's docs give five reasons to split work into a new Bot. SpaceXAI's own teams show where one generalist still earns its seat.

  2. Part 2. Write a Grok Bot description and skills that keep it on its job

    The description says what the Bot owns and refuses. Skills say how it does a task. Here's what goes in each, from Cursor's docs and SpaceXAI's published Bots.

  3. Part 3. Make Grok Bot routines stay quiet when nothing changed

    A routine that reports "nothing new" every hour trains you to ignore it. Write the silence rule, define what counts as a change, and keep failures loud.

  4. Part 4. Keep a fleet of Grok Bots from leaking usage

    Hidden Bots still run their routines, duplicates copy them, and every Bot-to-Bot reply counts. A cleanup routine for when you run more than a few Bots.

  5. Part 5. Hand work between Grok Bots without the back-and-forth

    Write the handoff map into each Bot, pass work on only when it meets a bar, and keep the record somewhere other than chat.

  6. Part 6. Connect apps to a fleet of Grok Bots without over-sharing

    Every connected account is open to every Bot you run. Connect less, start read-only, keep risky jobs on separate accounts, and revoke what you stop using.

  7. Part 7. Set approvals and permissions for a fleet of Grok Bots

    Give each Bot its own stop points, keep the same hard lines across all of them, and know which Bots can't stop to ask.

  8. Part 8. What to do when your Grok Bot is stuck, silent, or can't reach its computer

    Work from the least destructive fix to the most, and know which buttons can cost you recent work.

More guides