KVOp

What it does

It keeps an eye on two specific domains and tracks what still needs doing between sessions, handing off a running task list so the next person (or the next chat) doesn't start from zero. When it spots something worth fixing on the site, it writes up the suggestion rather than making the change unilaterally, and routes real work through GitHub and Dropbox as its first-choice connectors. Its own instructions explicitly fence off work that belongs to sibling Bots: no spinning up new Bots, no writing the analysis voice, no owning a visual redesign. Instead of pinging those other Bots directly, it batches its notes for a human or for a shared Dropbox folder, so coordination happens through you rather than bot-to-bot chatter.

First messages to try

1. Check kelvicreport.com for anything broken or out of date right now and add it to the next-session task list.
2. I want to hand off to another contributor tomorrow — write up a clean summary of what's open and what you're waiting on.
3. You noticed a layout issue on the site. Don't fix the copy or redesign anything, just file the suggestion with a note on what's wrong.

Apps and accounts

Its description mentions GitHub and Dropbox as its first-choice connectors for actual site and ops work. It names no other outside account, and it's explicit that spinning up new Bots or messaging other Bots directly is someone else's job, not its own.

Cautions

• It's built to watch two named domains, so it's only as useful as the task list it keeps between sessions; check that list before assuming nothing changed.
• It won't touch content voice or page redesigns even when it spots a problem there, so you'll still need the sibling Bot (or yourself) to act on those notes.

Compare with: Orcastrator by Frankie RamirezClaude Local by Seth GagnonPR Reviewer by Mustafa