# Check claimed bot completions for real

> Researched. Small business · Intermediate · Operations. Updated 2026-11-03.

Canonical page: https://www.aisetupsthatwork.com/setups/check-claimed-bot-completions-for-real/

## What it does
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's 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
1. 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.
2. 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).
3. 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.
4. 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.
5. 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.
6. 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.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
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.
```

## Guardrails
- What it touches: Connected mail, calendar, sheets, or chat. Scoped to this job (Grok Bot; One shared folder on the bots' computer, such as /completions).
- Needs your OK: Send, pay, publish, and account changes stay with you. Treat agent output as drafts first.
- Safety level: Read-only
- Letting the supervisor fix things. Verification and repair in one bot hides the failures you most need to see.
- Claims without proof locations. Reject the line format, not just the claim.
- Checking too rarely. A daily check on hourly work means a full day of unverified dones.

## 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.

## Estimates (labeled, not measured)
- Time saved: Not stated in sources.
- Money saved: Not stated in sources.
- Tool cost: Prices: Not stated in sources.

## Sources
Summaries use the public sources below, not independent verification.
- xAI: https://docs.x.ai/grok-bot/bots (Create and manage Bots: give each Bot one clear job with approval boundaries, and set it in the first message with a request to remember (read 2026-11-03))
- xAI: https://docs.x.ai/grok-bot/skills-routines-and-automations (Create a routine: plain-word schedules, the Test button, and the warning that a test run performs real work (read 2026-11-03))
- xAI: https://docs.x.ai/grok-bot/computer-and-apps (One computer, shared by all your Bots: files are visible to every Bot, so a supervisor can read the other bots' output (read 2026-11-03))

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-check-claimed-bot-completions-for-real

Related:
- [Organize your bots like an org chart](https://www.aisetupsthatwork.com/setups/organize-your-bots-like-an-org-chart/index.md)
- [Audit your bot instructions every week](https://www.aisetupsthatwork.com/setups/audit-bot-instructions-weekly-with-librarian-bot/index.md)
- [Catch a long agent run drifting off course](https://www.aisetupsthatwork.com/setups/catch-a-long-agent-run-drifting-off-course/index.md)
