Skill Detail

Coordinate multi-agent coding rigs with Gas City

Define and supervise multi-agent coding rigs with declarative city configuration, runtime providers, work routing, formulas, waits, mail, and health patrols.

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Security Reviewed
⭐ 1k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill coordinate-multi-agent-coding-rigs-with-gas-city Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Gas City `gc` CLI, tmux, git, jq, pgrep, lsof, optional dolt, flock, gh, claude, codex, gemini, herdr, ACP, Kubernetes, or other configured runtime providers
Install & setup
Install with brew install gascity where available or build from source with the documented prerequisites, then create a city.toml, select runtime providers, and use the gc CLI/controller commands to run and supervise the configured multi-agent rig.
Author
gastownhall
Publisher
Organization
Last updated
Jul 18, 2026
Quick brief

Use Gas City when a team wants to build a repeatable multi-agent coding rig rather than manually juggling terminals and task notes. The operator defines a `city.toml`, chooses runtime providers such as tmux, subprocess, exec, ACP, Kubernetes, or herdr, routes work through formulas and orders, tracks work with beads-backed state, and lets the controller reconcile desired agent state against running sessions. In practice, the skill is useful for standing up named rigs, mapping roles and commands, carrying work through waits or mail, and checking health while several coding agents run. Invoke this instead of using individual coding CLIs normally when the workflow needs persistent routing rules, rig-scoped orchestration, health patrol, waits, mail, and provider abstraction across multiple projects or agents. The boundary is configurable multi-agent coding orchestration infrastructure. It is not a generic SDK listing because the documented workflow centers on city configuration, controller commands, and supervised coding-agent runtimes.