# Openrig Skills

Use when an agent running inside OpenRig needs the right skill or context for fleet...

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

## Install

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

## Description

Use when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent doesn't know what applies or nothing is projected on cold boot. Installing, starting or updating OpenRig, getting back to a team or bringing a stopped one back from a person's own session is the rigs skill.

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

# OpenRig skills, the index (start here)

You're running inside OpenRig. OpenRig ships a set of **skills**, small documents that tell you *when* to do something and *how*. This file is the map: what ships, when to reach for each, and how to load it. If you don't know which skill applies, or nothing is projected into your context, **start here.**

## How OpenRig context works (30 seconds)

Skills are **progressive disclosure**: a skill's *name + description* sit in your context ambiently (the "hot tier"); its *body* loads only when you open it. So you don't pre-read everything, you pattern-match a skill's "when" to your moment, then open just that one. This file recommends skills from the shipped set. (For bounded procedures, open `agent-operated-workflows`; for ongoing agent-backed applications, open `agent-operated-software`.)

Every row below names **how to reach the skill**, already-hot, or an exact load path. No row is a dead end.

## Loading an entry on demand, `rig context get`

Don't guess a file path or a name. Go **ask → ref → load** in three steps:

1. **Discover**, run `rig context list` for every shipped entry's **ref** and name. The *when* for
   each is the index below (or `rig context list --json`, which carries each entry's purpose), match
   your moment there.
2. **Select**, match your moment to a row's *when* and take its **ref**. Refs are canonical full paths
   that mirror the library layout, `skills/<namespace>/<name>` (e.g. `skills/core/rig-lifecycle`,
   `skills/process/systematic-debugging`). A unique bare name (e.g. `watchdog`) also resolves; any
   slash-bearing ref is an exact lookup and fails loud if it does not exist.
3. **Load**, `rig context get skills/<namespace>/<name>`:

```
rig context get skills/core/rig-lifecycle
```

The router itself is available through both forms it teaches:
`rig context get openrig-skills` and `rig context get skills/core/openrig-skills`.

The rest: https://github.com/mvschwarz/openrig/blob/HEAD/packages/daemon/assets/plugins/openrig-core/skills/openrig-skills/SKILL.md