guildmaster
An agent and CLI that manages skills for the AgentCulture mesh.
guildmaster is a sibling to steward
(resident-agent alignment), culture
(the IRC-based agent mesh), and daria
(the awareness agent) in the Organic Development framework. Its mission is skill
and skillversion management plus an overview surface for the mesh: per the
settled division of labor (issue #1),
guildmaster becomes the skills supplier/manager while steward retreats to
agent-alignment. It onboards as a consumer first — vendoring the canonical
skills like every other sibling — before taking over the upstream ledger,
broadcast, and version tracking.
The repo and the Culture agent are named guildmaster; the CLI ships as
guild-cli on PyPI and installs the guild binary.
Install
# From PyPI (Trusted Publishing):
uv tool install guild-cli
# From source (dev):
uv sync
uv run guild --version
Commands
All verbs are read-only, offline, and deterministic — safe to call in agent
loops. Add --json to any of them for structured output.
| Verb | What it does |
|---|---|
guild whoami |
Report this agent's identity — suffix + backend (from culture.yaml) + version. The smallest identity probe. |
guild learn |
Survey the repo: the CLI verbs, the vendored skills under .claude/skills/, and a pointer to CLAUDE.md. |
guild explain <topic> |
Explain one topic in depth — print a vendored skill's SKILL.md, or a verb's summary. |
uv run guild whoami
uv run guild learn
uv run guild explain cicd
Supplier verbs — teach & onboard
As the mesh's skills supplier, guildmaster propagates skills to sibling agents
through two agent-first write verbs. Both default to dry-run (render the
issues and the ledger/verification diffs); --apply files them.
| Verb | What it does |
|---|---|
guild teach --skill <name> … --to <agent> … |
Teach a chosen set of skills to a chosen set of mesh agents. |
guild onboard --agent <owner/repo> |
Welcome a brand-new sibling with the full canonical kit, an identity-setup section, ledger registration, and a verification record. |
Agent-major, not skill-major. A run files one GitHub issue per target
agent, bundling a per-skill section for every skill that agent receives —
not one issue per skill. New-vs-resync framing is auto-detected per
(skill, agent) from the docs/skill-sources.md ledger. Skills must be chosen
explicitly (--skill, repeatable, or --all) — there is no implicit default.
These supersede a separate announce-skill-update verb. teach is the
single render-and-post engine; onboard is "teach the whole canonical kit"
plus ledger registration, the identity section, and a verification record. There
is no standalone broadcast verb (cf.
issue #10, which asked
for one — guildmaster fulfills the broadcast role via these two verbs instead).
Before → after. Today guildmaster has no broadcast verb of its own —
steward runs the live broadcaster, and teaching a set of skills or standing up
a new sibling is manual (hand-rendered briefs, hand-edited ledger, no
verification). After: one command propagates a skill set, or onboards a
sibling end-to-end. Going live is gated on the staged steward→guildmaster
cutover — see docs/cutover.md.
Inventory verbs — overview & show
guildmaster owns the mesh's inventory surfaces (the read-only "what kit +
config does an agent have?" view) per
issue #12. Both are
read-only — no --apply, no mutation, no drift verdict (judgment stays with
steward overview / steward doctor).
| Verb | What it does |
|---|---|
guild overview [--scope all|self <agent>|mesh] |
The supplier view: the canonical skill set + versions/origins, the docs/skill-sources.md ledger, and drift signals (uncovered skills, per-agent kit gaps). Feeds teach / onboard. --scope mesh instead surveys every agent's vendored skills live off the filesystem and flags what's missing/stale per agent. |
guild show <path-or-suffix> |
One agent's full config in one view — its detected prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), its parallel culture.yaml, and its .claude/skills index. |
uv run guild overview # whole ledger + canonical set
uv run guild overview --scope self daria # one agent's kit + gaps
uv run guild overview --scope mesh # live survey: every agent's skills + missing/stale
uv run guild show ../culture # config by path
uv run guild show daria # config by registered suffix
uv run guild show ../culture --json # structured config object
guild show resolves a registered suffix via the Culture server manifest
(culture_server_yaml in .claude/skills.local.yaml); pass an explicit
directory path to skip the lookup. Pre-cutover the ledger is still a
consumer-side view with no downstream column, so overview's drift signals
activate only after the steward→guildmaster cutover — the verb says so plainly.
guild harness use — switch the mesh-resident harness
guild harness use <name> writes one thing: the harness a clone's
culture.yaml declares — the backend/model/acp-command combination the
Culture daemon starts for that resident agent. Dry-run by default (renders the
culture.yaml diff); --apply writes.
This is deliberately narrow. Two different "which harness" selections exist over one clone, and this verb touches only one of them:
| Selection | What it means | Changed by |
|---|---|---|
| Interactive harness | Whichever binary you run in the repo right now (claude, colleague, qwen, …). All four can be run at will; it is never a config change. |
Invoking that binary directly — never this verb. |
| Mesh-resident harness | The single backend culture.yaml declares, which the Culture daemon starts for this clone. |
guild harness use <name> |
| Verb | What it does |
|---|---|
guild harness use <name> [--agent SUFFIX] |
Rewrite culture.yaml's backend/model/acp_command fields to match the named harness (claude, colleague, associate, qwen, acp — see guild/scaffold/harness.py). --agent picks which declared agent to switch when culture.yaml lists more than one. |
uv run guild harness use qwen # dry-run: show the culture.yaml diff
uv run guild harness use qwen --apply # write culture.yaml
uv run guild harness use claude --apply --agent daria # multi-agent culture.yaml
The write touches culture.yaml only — no file is created, fetched, or
re-provisioned, and no network call is made. Commit the result normally; a
fresh clone runs the new harness with no local setup step. This is not the
force path for an interactive session — forcing which binary you run right now
is invocation-level and never goes through culture.yaml.
Develop
uv sync
uv run pytest -n auto -v
uv run black --check guild tests && uv run isort --check-only guild tests
uv run flake8 guild tests && uv run bandit -c pyproject.toml -r guild
Every PR bumps the version (CI's version-check enforces it):
python3 .claude/skills/version-bump/scripts/bump.py patch
See CLAUDE.md for the full project shape, conventions, and the
build/test/publish toolchain.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file guild_cli-0.26.0.tar.gz.
File metadata
- Download URL: guild_cli-0.26.0.tar.gz
- Upload date:
- Size: 449.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
dcc4a50eb3b470ebba7e89894172dcf315ec9e7f330575ccf054c4078c2f2d0a
|
|
| MD5 |
71cb382fffb4225802fb675e051f9f0b
|
|
| BLAKE2b-256 |
7f43549bd555ba6ad59f9ca2f192ad90af2b89ad59f8064884c0640e00c1c2b9
|
File details
Details for the file guild_cli-0.26.0-py3-none-any.whl.
File metadata
- Download URL: guild_cli-0.26.0-py3-none-any.whl
- Upload date:
- Size: 84.0 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
uv/0.12.10 {"installer":{"name":"uv","version":"0.12.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f5142e9f05a5be4f167b4ff3a2175992563ddaf5d1ef8318dacae23b45b7e20e
|
|
| MD5 |
0934ae09acea91501e952938f680fde5
|
|
| BLAKE2b-256 |
07ffcb8b1779507d0169f5b5e5f84e6911d1de77f92f38fde8242bf25b445ba0
|
