Skip to content
SkillCheatSheet Sign in

oversight-team

An AI agent skill from mvschwarz/openrig, scored 64 out of 100 by code.

64/ 100C

Code score by group

  • Spec20/20
  • Description11/20
  • Procedure7/15
  • Done criteria4/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Done criteria (11), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

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).

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
mvschwarz/openrig
Folder
skills/_canonical/pods/oversight-team
License
Apache-2.0
GitHub stars
8,830
SKILL.md lines
107
Other files
0

Add oversight-team to your agent

npx skills add mvschwarz/openrig --skill oversight-team

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from mvschwarz/openrig

  1. openrig-architect

    Use when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance / skills / culture), o…

    76B
  2. requirements-writer

    Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.

    75B
  3. dogfood

    Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "t…

    74B
  4. orienting-to-an-inherited-seat

    Use when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a wo…

    74B
  5. session-source-fork

    Use when authoring a rig spec member or `rig expand` payload that needs to start a new managed seat from a prior runtime conversation source — `session_source: { mode: fork, ref:…

    74B
  6. openrig-operating-model

    Use when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking…

    72B
  7. retiring-and-inheriting-a-seat

    Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from…

    72B
  8. seat-continuity-and-handover

    Use when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire/advise/…

    71B

All skills in mvschwarz/openrig

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.