New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Oversight Team

by mvschwarz in mvschwarz/openrig

A skill your agent uses 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…

Apache-2.0Auto-check passedAgent Workflows

Install Oversight Team

skills CLI
$ npx skills add mvschwarz/openrig --skill oversight-team -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig oversight-team --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/pods/oversight-team .claude/skills/oversight-team && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
oversight-team
GitHub stars
6.2k
Token cost
~1.6k tokens
SKILL.md length
745 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses 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…

  • Works in 3 steps: Orchestrator-ping — nudge the pod's own… → The refocus primitive — watchdog's… → Escalate to the human — via the existing…
  • You are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy)
  • SKILL.md covers Use this when, Don't use this when, The posture — pull, never poll… and The v0 detectors (scripted +…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Oversight Team is an agent skill from mvschwarz/openrig. 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…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • You are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy)
  • Running the drift detectors
  • Choosing whether to intervene vs escalate

Example prompts

  • “/oversight-team”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Orchestrator-ping — nudge the pod's own orchestrator to realign. They run their rig; you
  2. The refocus primitive — watchdog's Refocus level: a reactive north-star reminder
  3. Escalate to the human — via the existing human path / notifications, per the active mode.

What it can do on your machine

Read from SKILL.md and the folder at commit a29dfbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Oversight Team loads about 1.6k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 745 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~135
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a29dfbc, republished under its Apache-2.0 licence (© mvschwarz). 745 words, ~1,571 tokens.

Download SKILL.mdSave it as .claude/skills/oversight-team/SKILL.md (or your agent's skills folder).
name
oversight-team
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).

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:

  • Premature park — an in-progress qitem with an idle owner and no handoff. Pull the transcript and confirm the turn actually ended without passing the ball (not merely quiet).
  • Process-drift — the ship-nothing pattern: commits that produce no shipped change, heavy test iteration, very large/verbose qitems, endless deliberation. Detectable from git history
    • queue sizes. (This is process winning over product; correct it toward shipping.)
  • Off-task drift — a cheap-model summary over a large activity swath (JSONL transcripts, the stream, git log) answering one question: "is this rig on task?" If a pod drifts too long, intervene.
  • Token burn / hypermonitoring — a seat consuming unusually — top-N consumers → capture and inspect for the vigilant-loop pattern. Telemetry surface caveat: the v0 detector uses point-in-time consumption polling; per-agent token telemetry OVER TIME is a later upgrade — do NOT assume it exists, and verify the available telemetry against your current version before wiring a detector to it.
Show full SKILL.md (332 more words)Show less

Interventions — least-disruptive first

  1. Orchestrator-ping — nudge the pod's own orchestrator to realign. They run their rig; you prompt, you do not seize.
  2. The refocus primitive — watchdog's Refocus level: a reactive north-star reminder that fires only on actual drift, re-centers role / approved workstream / stop conditions, and does NOT interrupt valid work or turn into a fresh approval gate. Use watchdog for the message shape and the cadence discipline.
  3. Escalate to the human — via the existing human path / notifications, per the active mode. Reserve for what an agent-level nudge cannot fix.

Do not (the discipline)

  • Don't hyper-poll / vigilant-loop — you become the token burn you hunt.
  • Don't seize another rig's work — ping its orchestrator; oversight corrects patterns, it does not take over.
  • Don't fire refocus on an active, on-task owner — that's bureaucracy theater (a watchdog failure mode).
  • Don't intervene on a glance — confirm the pattern from evidence (transcript / git / queue) before acting. A false alarm costs the fleet trust and tokens.
  • Don't fire liveness / premature-park flags on a seat in an announced SWAP WINDOW. A seat mid-handover looks idle/parked to the detectors. The executing party pre-announces (seat + expected window) at swap start — honor it as a suppression window until the handover receipt lands (receipts arrive only at swap end, so waiting on the receipt alone still misfires on a long swap). See retiring-and-inheriting-a-seat.

Cheap + deep model economics

Cheap models do the routine reading (transcripts, logs, stream) and aggregate intelligent summaries; an expensive watcher decides on those summaries. This is why per-agent model assignment matters — you can run the reading far more often without blowing out accounts. Design the pod so the deep model never touches the raw firehose.

See also

  • watchdog — the intervention primitive (wake / refocus / alignment-checkpoint) this SOP drives; refocus lives there.
  • refocus — the drift doctrine watchdog operationalizes.
  • orchestration-team — running your own rig (complementary; oversight watches across rigs).
  • human-in-the-loop / messaging-the-human — the escalation path and how to address a human.
  • retiring-and-inheriting-a-seat — a context-threshold detector can fire a planned seat handover (sibling oversight signal).

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/pods/oversight-team of mvschwarz/openrig.

Open the folder on GitHubat commit a29dfbc

Compare with similar skills

Oversight Team next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Oversight Team compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Oversight Team this skillmvschwarz/openrig6.2k—~1.6kAutomated safety check: PassApache-2.0
Orca CLIstablyai/orca88k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    88k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed

  • Paseo Advisor Second Opinion

    getpaseo/paseo

    Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed

  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated 11 days ago
    Agent WorkflowsAuto-check passed

  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.2k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    6.2k GitHub stars~864 tokensUpdated today
    Auto-check passed

  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    6.2k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Seat Continuity and Handover

    mvschwarz/openrig

    Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    6.2k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Addressable Markdown Loader

    mvschwarz/openrig

    Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    6.2k GitHub stars~341 tokensUpdated today
    Auto-check passed

  • Agent Starters

    mvschwarz/openrig

    Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.

    6.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Oversight Team

What does Oversight Team do?

A skill your agent uses 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…. Oversight Team is an agent skill from mvschwarz/openrig. 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.

When should I use Oversight Team?

Oversight Team fits situations like: you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy); running the drift detectors; choosing whether to intervene vs escalate.

How do I install Oversight Team in Claude Code?

Run `npx skills add mvschwarz/openrig --skill oversight-team -a claude-code`. Or copy the skill folder (skills/_canonical/pods/oversight-team in mvschwarz/openrig) into .claude/skills/oversight-team in your project. Claude Code loads it when a task matches its description.

How do I install Oversight Team in Codex?

Run `npx skills add mvschwarz/openrig --skill oversight-team -a codex`. Or copy the skill folder (skills/_canonical/pods/oversight-team in mvschwarz/openrig) into .agents/skills/oversight-team in your project. Codex loads it when a task matches its description.

Can I use Oversight Team in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill oversight-team -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oversight-team, .gemini/skills/oversight-team, .github/skills/oversight-team and .opencode/skills/oversight-team in your project.

What does Oversight Team need to run?

SKILL.md names no scripts, command-line tools or credentials: Oversight Team is instructions for the agent only.

Does Oversight Team access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Oversight Team safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Oversight Team use?

Oversight Team is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Oversight Team use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Oversight Team?

Skills that share tags, products or a category with Oversight Team: Orca CLI (stablyai/orca, 88k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Oversight Team?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,242 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.