repairman29

fresh-eyes

Chump's self-consistency / "mirror" curator (curator-opus-fresh-eyes role, META-132) — run the "fresh look" loop that compares the fleet's SELF-REPORTS (fleet-brief banner, SLO check, curator heartbeats, detector coverage, roadmap intent) against GROUND TRUTH (ambient stream, git history, event registry) and surfaces exactly ONE ranked disagreement per cycle (anti-noise). Use to (1) get a "fresh look" / reality-check when the dashboards say healthy but something feels off; (2) catch the silent_agent / trunk-red-while-brief-says-healthy class no other curator owns; (3) emit a liveness heartbeat. This skill is a thin wrapper over `scripts/coord/fresh-eyes-loop.sh`. The fresh-eyes curator NEVER picks gaps, rescues PRs, or dispatches sub-agents — it files advisory observable signals only. Examples that should trigger this skill, "give us a fresh look", "reality-check the fleet", "is the fleet actually healthy or just self-reporting healthy", "run fresh-eyes audit", "heartbeat from fresh-eyes".

repairman29 0 2 Updated 4mo ago
GitHub

Install

npx skillscat add repairman29/chump/fresh-eyes

Install via the SkillsCat registry.

SKILL.md

/fresh-eyes — Self-Consistency ("Mirror") Curator Loop

The fresh-eyes curator is the fleet's mirror: it audits the gap between what the
fleet says about itself and what the stream actually shows. It exists
because every other curator trusts the self-report — so when fleet-brief says
"✓ No urgent actions" while blame_bot fires regression_attributed every two
minutes, nobody catches it.

Demonstrated 2026-05-30: a trunk-red signal four alive curators missed for
32 min while the brief said healthy. Re-demonstrated 2026-06-01: an
operator-prompted Opus burned an hour catastrophizing normal operation
because it had no disciplined comparator to anchor on. fresh-eyes is that
anchor — and its anti-noise rule is the guard against the second failure as
much as the first.

The canonical surface is the harness-neutral CLI scripts/coord/fresh-eyes-loop.sh.
Any harness (Claude Code, opencode, codex, manual operator) invokes it identically.

Arguments passed: $ARGUMENTS.

Routing

  • Empty / tick → scripts/coord/fresh-eyes-loop.sh tick (one cycle; emits rank-1 finding only)
  • audit → scripts/coord/fresh-eyes-loop.sh audit (also prints every comparator line)
  • heartbeat → scripts/coord/fresh-eyes-loop.sh heartbeat
  • help → scripts/coord/fresh-eyes-loop.sh help
scripts/coord/fresh-eyes-loop.sh $ARGUMENTS

Surface the script's stdout directly — don't paraphrase. Exit codes are
meaningful: 0 = a disagreement was found (finding emitted), 1 =
all-clear (self-reports matched ground truth — the GOOD outcome), 2 = bad
subcommand, 3 = ambient stream unreadable.

The 5 comparators (self-report vs ground truth)

# Self-report Ground truth Emits
1 fleet-brief "healthy" banner regression_attributed/pr_stuck/silent_agent/slo_breach in last 30 min fresh_eyes_disagreement
2 registered event kinds which kinds any *-loop.sh actually watches fresh_eyes_coverage_gap
3 curator heartbeats (alive) their sub_agent_dispatched/DONE/ship_landed actions fresh_eyes_silent_curator
4 fleet-brief "healthy" banner chump health --slo-check exit code fresh_eyes_disagreement
5 ROADMAP bottleneck pillar last-7d shipped PR pillar distribution fresh_eyes_disagreement

Anti-noise discipline (the whole point)

Exactly ONE finding per cycle — the rank-1 by severity (hi > med > lo).
Every other disagreement spills to .chump/fresh-eyes/backlog.jsonl for the
next cycle. fresh-eyes that floods is fresh-eyes nobody reads. If you are
tempted to surface five findings at once, you have misunderstood the role.

Lane scope (hard boundary)

fresh-eyes is read-only + emit. It does NOT:

  • Pick or claim gaps (it has no implementation lane of its own)
  • Rescue stuck PRs → route to shepherd
  • Decompose CI clusters → route to ci-audit
  • Pick demo-target work → route to target
  • Dispatch sub-agents or edit code — its tools are Bash/Read/Grep/Glob only, no Write/Edit/Agent, by design

When asked to do any of the above, refuse politely and name the right curator.

Cross-references