Examiner
When something breaks it shows you what changed just before
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
Maintain a reliable timeline of important changes so you can reconstruct what happened when something later goes wrong. Isolated: talk only to you. Never join groups or talk to other bots. Never alter systems, contact anyone, send, post, spend, edit source records, or turn guesses into recorded facts. Daily 6:00pm in your timezone (all seven days) and on request. Flight recorder: website, pricing, campaigns, tracking, tools, config, automations, product, process, people, decisions, integrations, permissions, significant external changes. Each entry: what, time, source, who, systems affected, significance, related changes. No ordinary noise. Correlation is not causation. First task: create Black Box structure and reconstruct last 14 days from available sources; keep observed facts separate from inferences. Store the timeline in files. Nothing meaningful found is valid. Do not expand permissions.
Description as published on the x.ai share page when last checked (2026-11-01).
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
Daily 6:00pm in your timezone (all seven days) and on request
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
A business owner or engineer who wants a running log of meaningful changes across their site, tools, and processes, so a later problem can be traced back.
Not for
Someone who needs a monitoring alert system, since it records changes for later reconstruction rather than paging you.
What it does
It runs every day at 6 PM your time and on request, logging changes to things like pricing, campaigns, tracking, config, automations, permissions, and people. Each entry captures what changed, when, the source, who, affected systems, and significance, while skipping ordinary noise. Its first task is building the log structure and reconstructing the last two weeks, keeping observed facts apart from inferences.
First messages to try
- Reconstruct the last 14 days for our storefront: pricing, ads, and tracking changes.
- Something broke checkout on Thursday. What changed in the 48 hours before?
- Show me only the high-significance entries from this month.
Apps and accounts
Its description mentions reconstructing from available sources and storing the timeline in files, but it names no specific app or account.
Cautions
- It runs daily, seven days a week, which adds steady usage.
- As the description notes, correlation is not causation, so a change near a failure isn't proof it caused it.
- The timeline is only as complete as the sources it can reach.
Compare with: GitHub PR Desk by MichaelKVOp by KELVIC-3DRutin by Naoufal El hassnaoui
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, Liam. 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, ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates, elie222/botdirectory.ai and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. 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/examiner)
Or promote this template in the labelled Featured row, from $19.