Gas City Operating Adapter (using-gc)

A driving-adapter skill for operating a caller-selected Gas City 1.4 runtime while keeping GC runtime state out of AgentOps verdicts.

AutomationAdvanced★ 446⑂ 42AI score 8/10Last updated: Sep 26, 2026

What it does

Activates only when the caller explicitly selects Gas City, and treats GC as a replaceable execution adapter rather than a correctness or completion boundary.
Walks through installing/pinning the upstream gascity pack, registering a rig, and pre-qualifying the runtime contract with ao gc prepare and ao gc check before any model spend.
Gives concrete commands for pack registries, bead creation and formula launch (gc bd create, gc sling), plus a 1.4 upgrade and retirement checklist.
Defines a stall protocol: dispatch a still-ready bead once; never re-sling a routed bead — wake its worker with gc session wake instead.
Documents a four-layer visibility model (run/supervisor state → bead graph → tmux pane truth → doctor/health) and which layer to trust when they disagree.
States hard boundaries: a GC close is not AgentOps completion, and the skill performs no automatic retry, Git, release, or semantic validation.

Who it's for

Platform / agent-infrastructure engineers running AgentOps on top of Gas City 1.4.
Operators debugging multi-agent "software factory" pipelines.
Teams that insist completion be read from run/bead/artifact state, not chat prose.

Example uses

Onboard a repo as a rig, then run ao gc prepare --city ... --rig ... and ao gc check to catch pin or schema drift before spending tokens.
Kick off a first build: gc bd create "Add a --json flag to the export command" followed by gc sling gc.run-operator <bead-id> --on build-basic.
When a worker looks stuck, skip re-slinging: wake the session and capture the tmux pane to find the real cause (trust prompts, DNS/API failures).
Upgrade a legacy city with gc doctor --fix → gc import install → gc start, then verify against the post-upgrade checklist.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/boshu2/agentops/HEAD/packs/agentops-executor/skills/using-gc/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the packs/agentops-executor/skills/using-gc folder from the GitHub repo boshu2/agentops into my ~/.claude/skills/using-gc/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/boshu2/agentops.git /tmp/agentops && mkdir -p ~/.claude/skills && cp -r /tmp/agentops/packs/agentops-executor/skills/using-gc ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

Open a terminal.
Clone the repo: git clone https://github.com/boshu2/agentops.git /tmp/agentops
Create the skills directory: mkdir -p ~/.claude/skills
Copy the skill: cp -r /tmp/agentops/packs/agentops-executor/skills/using-gc ~/.claude/skills/
Restart Claude Code and confirm using-gc appears in your skill list.
Satisfy the prerequisites: a Gas City 1.4 binary (gc version reports 1.4.0), the AgentOps ao CLI, a Python that can import PyYAML, and tmux.
Invoke it explicitly with phrases like "using gc", "gas city", or "dispatch through gc".

View source on GitHub ↗License: Apache-2.0