Agent Watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work...
Install
npx skills add BuilderIO/skills --skill agent-watchdog -g -a claude-code -y- Repository
- BuilderIO/skills4.6k
- Category
- AI and agents
- Updated
- 7d ago
- License
- MIT
- Context cost
- Mediumabout 1,802 tokens
- Runs scripts
- No, instructions only
What it does
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same problem to form your own hypotheses and approach, inspect what the agent actually changed and verified, compare the two investigations, report gaps and add-on directions, and optionally make scoped fixes when the user authorizes repair.
Agent Watchdog
Watch another agent's work like a reviewer with a pager who is also a second investigator: wait for completion when needed, reconstruct the request, run your own independent investigation of the same problem, verify the evidence, and close the gap between what was asked and what actually happened. You are not just grading their homework, you are a second solver whose findings get diffed against theirs so nothing is missed.
Choose The Mode
Infer the mode from the user's wording:
- Watch only: monitor a session, PR, branch, CI run, or transcript until it reaches a terminal state. Do not edit files.
- Audit: read the prompt, transcript, diff, tests, CI, comments, screenshots, or final claims, run the independent investigation below, and return a gap report plus add-on directions. Do not edit files.
- Audit and fix: audit first, then make narrow fixes for clear gaps. Avoid broad rewrites, branch movement, or speculative changes.
- Compare: when given multiple sessions or agents, compare their work against the same original request and reconcile the important differences.
If authority is unclear, default to audit-only and say what you would fix.
Resolve The Target
- Identify every artifact the user supplied: session ID, transcript path, thread URL, PR, branch, commit, CI run, issue, Slack link, or pasted summary.
- Use the host's native thread/history tools, local transcript files, repo logs, GitHub tools, or pasted content to resolve the artifact. Prefer the most direct source over summaries.
- If the artifact is still running and the user asked to watch, poll at a reasonable interval until it is done, blocked, stale, or clearly waiting on a human/external system.
- If the artifact cannot be resolved, ask for the missing identifier or path.
Reconstruct The Contract
Build a compact contract before judging the work:
