Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/gastownhall/gascity --skill gc-rigsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| 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, route through
Gas City with the rig's configured name:
gc bd create "title" --rig <rig-name> # Create in rig's database
gc bd list --rig <rig-name> # List rig's beads
Running gc bd from the city root without --rig targets the city-level
store only when no stronger scope signal applies. Gas City also auto-detects
scope from a bead ID prefix, GC_RIG, or an enclosing rig/worktree. Use
gc bd --city <city-path> ... when HQ is required and gc bd --rig <rig-name> ... when a rig is required. Use gc rig list to find configured
rig names and 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
Routing work to agents with gc sling and formulas
Finding, creating, claiming, and closing work items (beads)
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.
Based on SOC occupation classification
