Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Baseado na classificação ocupacional SOC
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/gastownhall/gascity --skill gc-workO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Exibindo SKILL.md
Routing work to agents with gc sling and formulas
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.
City lifecycle — status, start, stop, init
| name | gc-work |
| description | Finding, creating, claiming, and closing work items (beads) |
Everything in Gas City is a bead — tasks, messages, molecules, convoys.
The gc bd CLI is the primary interface for bead CRUD.
Each rig has its own .beads/ database with its own ID prefix (e.g.
fe- for frontend, be- for beads). A bead must live in the
same database as the agent that will work on it. When you sling a bead
to a rig-scoped agent, sling operates on the agent's rig database — so
the bead must already exist there. The bead ID prefix tells you which
rig it belongs to.
Use gc rig list to see rig names, paths, and prefixes.
Use --rig to create beads in the right database. If the work will
be dispatched to a rig-scoped agent, create the bead in that agent's rig:
gc bd create "title" --rig frontend # Create in frontend's db (fe- prefix)
gc bd create "title" --rig beads # Create in beads db (be- prefix)
gc bd create "title" # Create in current directory's .beads/
gc bd create "title" -t bug # Create with type
gc bd create "title" --label priority=high # Create with labels
gc bd list # List beads in current .beads/
gc bd list --rig <rigname> # List beads in a specific rig
gc bd ready # List beads available for claiming
gc bd ready --label role:worker # Filter by label
gc bd show <id> # Show bead details
gc ready # Same frontier, federated over every store the city uses
On a city that serves a coordination class from its own [storage] binding,
gc bd ready (and gc bd list --ready) is refused with exit 1: it reads one
ledger and the city's ready set spans more than one. Use gc ready there. It
takes --assignee, --unassigned, --metadata-field, --exclude-type,
--exclude-label, --sort, --limit, --include-ephemeral, --status and
--json — not the label, parent, type or priority selectors gc bd ready
forwards.
gc bd update <id> --claim # Claim a bead (sets assignee + in_progress) — races in a multi-agent city; prefer `gc hook --claim` there
gc bd update <id> --status in_progress # Update status
gc bd update <id> --add-label <key>=<value> # Add/update labels
gc bd update <id> --append-notes "progress..." # Append a note (does not replace existing notes)
gc bd close <id> # Close a completed bead
gc bd close <id> --reason "done" # Close with reason
gc hook [agent] # Show routed work for an agent (defaults to $GC_AGENT)
gc hook --claim # Atomically claim one routed work item onto this agent's hook