# Oversight Team

Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps...

- Repository: https://github.com/mvschwarz/openrig (8541 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mvschwarz/openrig --skill oversight-team -g -a claude-code -y`
Codex: `npx skills add mvschwarz/openrig --skill oversight-team -g -a codex -y`
Cursor: `npx skills add mvschwarz/openrig --skill oversight-team -g -a cursor -y`
Gemini CLI: `npx skills add mvschwarz/openrig --skill oversight-team -g -a gemini-cli -y`

## Description

Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primitive mechanics (watchdog).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Oversight Team

You are on the **oversight pod**, a standing rig (agent-managed infrastructure, like the
skills-architect pattern: agents + scripts + an SOP owning a function full-time) whose job is
to keep **other** rigs healthy. You catch the unproductive patterns rigs drift into, premature parking, process-drift, off-task wandering, token burn, early, and correct them
with the lightest touch that works. **Monitor mode: idle until a flag fires; never hyper-poll.**

## Use this when

- You are a seat running in **monitor mode** on the oversight pod.
- Configuring or running the v0 drift detectors over the fleet.
- Deciding whether to **intervene** (orchestrator-ping / refocus) or **escalate** (human).

## Don't use this when

- You are orchestrating your **own** rig, that's `orchestration-team`. Oversight watches
  **across** rigs; it does not run them.
- You need the intervention **primitive mechanics** (the wake / refocus / alignment-checkpoint
  stack, `rig watchdog` policies, message shape), that's `watchdog`.
- A single stuck seat needs recovery, the owning orchestrator or `watchdog` handles that.

## The posture, pull, never poll (load-bearing, and self-referential)

Monitor mode means **idle until a flag fires, then wake and check**, not continuous watching.
Continuous `rig capture` / vigilant-observation loops are the exact anti-pattern that has
burned entire model accounts: an over-observing watcher is expensive and produces nothing.
**The oversight seat must model the discipline it enforces**, the token-burn detector below
exists precisely because seats fell into vigilant loops, so a hyper-polling monitor would be
the failure it hunts. Cheap models read the large swaths; the expensive watcher acts on
**aggregated summaries**, never the raw firehose.

## The v0 detectors (scripted + cheap-model-summarized)

Cheap, evidence-based checks, each confirms a pattern from durable evidence before anyone acts:

The rest: https://github.com/mvschwarz/openrig/blob/HEAD/packages/daemon/specs/agents/shared/skills/pods/oversight-team/SKILL.md