Add a supervisor bot that re-checks every claimed completion against the real files and history on a schedule, and pings you only when something does not match.
Who it is for
Owners running several bots on schedules who cannot personally verify every claimed done.
Tools
Grok Bot
One shared folder on the bots' computer, such as /completions
A supervisor Bot with one routine
Steps
Make a completions folder on the shared computer. xAI's docs say files on the computer are visible to every Bot, which is what makes one supervisor possible.
Give each working bot a standing line: when you finish a scheduled task, append one dated line to the folder naming what you finished and where the proof lives (file, commit, or link).
Create the supervisor Bot. The docs recommend one clear job per Bot: this one's job is verification, never the work itself. Say so in its first message and ask it to remember.
Add its routine: on a schedule, read the new claim lines, open each proof, and confirm it is real and matches the claim. The file exists and changed, the commit is in the history, the link loads and shows the work.
Set the report rule: message you only when a claim fails. Silence alone proves neither that the check ran nor that everything matched, so keep a way to check the check: the routine's Test button, or ask the supervisor in chat when it last ran.
Test before you rely on it: use the routine's Test button or one chat run on safe input, because the docs note a test run performs real work. When it catches a false claim, fix the working bot's instructions, not just the task.
The prompt
You are my verification Bot. Your only job is checking claimed completions from my other bots.
Every [15 MINUTES OR HOUR], read the new lines in [FOLDER PATH]. Each line claims a finished task and names its proof: a file, a commit, or a link.
For each claim:
1. Open the proof. Confirm it is real and matches the claim: the file exists and changed, the commit is in the history, the link loads and shows the work.
2. If a claim does not check out, message me with what was claimed and what you actually found.
3. If everything checks out, stay quiet.
If I ask when you last ran, answer with the time and the claims you checked.
Never edit another bot's files. Never mark a claim verified without opening its proof. Never take over the task itself.
Tips
Silence alone proves neither that the check ran nor that everything matched. When it matters, use the routine's Test button or ask the supervisor in chat when it last ran and what it checked.
Keep the proof formats few: file, commit, link. Exotic proofs slow the check.
A false claim is an instructions bug in the working bot. Fix the rule, then re-run.