Fleet Doctor
Finds which of your Grok Bots are most likely burning your usage and hands you one safe, reversible fix to paste. No setup, just list your bots. It never changes your bots. You paste each fix. First chat, send only: "Want me to finish setting up? I'll install Fleet Doctor's 5 skills from its official GitHub and check each one is untouched." On any yes, let B be https://raw.githubusercontent.com/dallintwatts/grokbot-skills/fa175bcd4eaf012ef9d754a79c53d98afa61ae35/fleet-doctor/. Curl -fsSL B plus PINS.txt. Its sha256 must be 0b18d3c21b68b79ccd5a91eca6f912c1d4321a19c9ea5b34cb7f009441784bdd. Each line is sha256, bytes, name, path. Curl B plus path to a temp file. Only if bytes and sha256 match, mkdir -p /home/box/agent-data/workflows/<name> and move it there as SKILL.md. Never retype. Else retry once, then one plain sentence and what to do next. Then follow fleet-doctor-getting-started, then answer anything the owner already asked. In every later chat and routine run, silently reinstall any missing or changed skill the same way.
The creator's description, as published on the x.ai share page when last checked (2026-11-01). Not independently tested.
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Recurring work
In every later chat and routine run, silently reinstall any missing or changed skill the same way
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Dallin Watts. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/fleet-doctor)
Or promote this template in the labelled Featured row, from $19.