gastown
Multi-agent orchestrator for Claude Code. Use when user mentions gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination, beads, hooks, molecules, workflows, the witness, the mayor, the refinery, the deacon, dogs, escalation, or wants to run multiple AI agents on projects simultaneously. Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill gastown --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Orchestrates multi-agent coordination for Claude Code projects, handling installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.
How it works
- The skill positions the user as an Overseer in the Gas Town engine room and requires you to execute all gt and bd commands via the Bash tool.
- It defines roles (Mayor, Witness, Refinery, Polecats, Crew, Dogs, Deacon) and a workflow where work arrives as a bead, is slung to a rig, spawned as polecats/crews, and processed through HOOKs, with monitoring and automatic merges by Witness/Refinery.
- It enforces operational boundaries: the engine handles beads, session naming, routing, and spawning; the user-supplied commands are executed by the agent, with results reported in-world style.
- It mandates using the AskUserQuestion tool for guided interactions in several decision points (first contact, execution mode, next steps, etc.).
- It includes a comprehensive set of commands organized into Engine Control, Work Management, Workers, Diagnostics, Beads, Refinery, and Patrol Activation.
When to use it
- Use when the user mentions terms like gastown, convoys, polecats, beads, hooks, workflows, the witness, the mayor, the refinery, the deacon, or when the goal is to run multiple AI agents on projects simultaneously.
- Use for setup/install ( gt, bd, workspace at ~/gt ), ongoing operation (sling, convoy, hook checks, status), and monitoring (doctor, status, peek).
What it can touch
- Tools: claude-code (declared), accessed via Bash for executing gt and bd commands.
- Beads management (bd create, bd list/show/sync), gT commands (gt sling, gt status, gt hook, gt doctor, gt refinery, etc.).
- Patrol activation via email commands (gt mail send ...).
Caveats
- Witness and Refinery are Claude agents, not daemons.
- You must not manually create agent beads; GT handles bead creation.
- Session names are managed by GT and shown via gt polecat list.
- Patrols may require triggering via mail; not self-activating.
# Gas Town Skill The Cognition Engine. Track work with convoys; sling to agents. ## Your Identity **You are a Gas Town expert.** You have complete mastery of this system. You know: - Every command and its purpose - Every agent role and how they coordinate - Every workflow and how work flows through hooks - Where to find any information you need **You never guess.** If you're unsure about exact syn
What does the gastown skill do?
Multi-agent orchestrator for Claude Code. Use when user mentions gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination, beads, hooks, molecules, workflows, the witness, the mayor, the refinery, the deacon, dogs, escalation, or wants to run multiple AI agents on projects simultaneously. Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill gastown --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.