Menu
Managing rigs — add, list, status, suspend, resume
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | gc-rigs |
| description | Managing rigs — add, list, status, suspend, resume |
A rig is a project directory registered with the city. Agents can be
scoped to rigs via the dir field.
Each rig has its own .beads/ database with a unique prefix (e.g.
hw- for hello-world). To create or query beads for a rig, run bd
from the rig directory or pass --dir:
bd create "title" --dir /path/to/rig # Create in rig's database
bd list --dir /path/to/rig # List rig's beads
Running bd from the city root hits the city-level .beads/, not
the rig's. Use gc rig list to find rig paths.
The canonical location for rigs is <city-root>/rigs/<rig-name>. Always
use this path unless the user explicitly provides an alternative. Do not
create rigs at the city root or as siblings of the city directory.
If the user asks to create a rig but does not specify where, ask them
before proceeding: confirm the rigs/ convention and offer the choice of
a custom path. Do not silently pick a location.
gc rig add <path> # Register a directory as a rig
gc rig list # List all registered rigs
gc rig status <name> # Show rig status, agents, health
gc status # City-wide overview (includes rigs)
gc rig suspend <name> # Suspend rig (all its agents stop)
gc rig resume <name> # Resume a suspended rig
gc rig restart <name> # Restart all agents in a rig
gc restart # Restart entire city
Project conventions for writing, editing, restructuring, or reviewing the Gas City user documentation — the Mintlify site under docs/. Use this whenever you touch anything in docs/ (pages, tutorials, guides, reference, concept pages, diagrams, navigation) or write/edit prose about Gas City, even when the request is just "fix the docs", "write a docs page", "the docs are wrong/confusing", "rename X across the docs", or an edit to a file under docs/. It defines the canonical six-primitive model, required terminology (orchestrator not controller, platform not SDK, formulas v2 as the value), the prose / emphasis / diagram conventions, the information architecture, the rule that generated docs are edited at their source, and the gates to run before docs work is done.
Routing work to agents with gc sling and formulas
Finding, creating, claiming, and closing work items (beads)
API server and web dashboard — config, start, monitor
Managing agents — list, peek, nudge, suspend, drain
City lifecycle — status, start, stop, init