rigs: your route into OpenRig

OpenRig runs a team of coding agents (Claude Code, Codex and others) side by side in tmux. A local daemon keeps their tasks, messages and state, so the team keeps working across restarts. This skill gets OpenRig installed, gets a team working on what the person wants, and shows how to work with that team from here.

The goal is a team doing the person's work, not just an install. Go through the steps in order and stop early only if the person asks you to. When they say what they want built, give it to OpenRig's operator (step 2) instead of building it yourself.

Tell the person what you're about to run and why before you run it. Don't install system packages or change their machine without a yes, and don't start a team, including rig up, without their yes to what it will start; a yes they already gave for that same launch counts, so don't ask twice. Starting OpenRig and a team writes files: Codex hooks and settings in ~/.codex/config.toml, Claude Code workspace trust in ~/.claude.json, discovery skills in ~/.claude/skills and ~/.agents/skills, and, in the repository, managed guidance in AGENTS.md or CLAUDE.md, activity hooks in .claude/settings.local.json and a status line there unless the project already has its own, plus the team's skills and plugins. Unless a permission policy, a per-seat choice or (for Codex) a named profile applies, the kernel's own seats run with an operational default: Codex with -s danger-full-access -a never, and Claude Code with its file tools, web fetches and operational commands, including reads under the home folder, allowed without asking. Say so before you start OpenRig (the full list).