guild-cli 0.4.0__tar.gz → 0.5.0__tar.gz

guild_cli-0.5.0/.claude/skills/guild/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: guild
+description: >
+  Run guildmaster's skills-supplier overview and narrate it. Run `guild
+  overview` (via scripts/overview.sh) for the deterministic evidence pack — the
+  canonical skill set + versions/origins, the docs/skill-sources.md ledger, and
+  skills-scoped drift signals — then narrate three separated layers: observed
+  facts, inferred relationships, and suggestions (each naming the command that
+  enacts it). Use when an operator asks "what skills do we supply", "who
+  consumes what", "is anything drifting", or "what should I teach next".
+  Skills-scoped and reflect-only — it surfaces and interprets supplier-side
+  skill/version signals; it does NOT narrate the agent relationship graph or
+  judge alignment (that stays with steward's org-overview / steward doctor).
+  The skills-scoped excerpt of steward's `org-overview` narration contract
+  (cite-don't-import, issue #12).
+type: command
+---
+
+# guild — narrate guildmaster's own supplier surfaces
+
+guildmaster is the mesh's skills **supplier**, and it owns the *inventory*
+surfaces ([issue #12](https://github.com/agentculture/guildmaster/issues/12)).
+The per-agent half (`guild show`) is backed by the vendored `agent-config`
+skill. **This skill is the supplier half: the affordance for `guild overview`.**
+It houses the scripts that run guildmaster's own read-only CLI surfaces and the
+contract for narrating them — `overview` is the one script today.
+
+Unlike the vendored skills, this one is **guildmaster's own** (origin =
+`guildmaster`, not cited from steward): `guild overview` is a pure-Python,
+read-only CLI verb, and `scripts/overview.sh` is the thin deterministic wrapper
+that invokes it. The script picks how to call `guild` (installed console
+script → `uv run` → `python -m guild`) and delegates; it interprets nothing.
+
+**The load-bearing split** (this is the skills-scoped excerpt of steward's
+`org-overview` narration contract — issue #12, cite-don't-import):
+
+- **The CLI (`guild overview`) emits only deterministic facts** — the canonical
+  skill set, the ledger view, and neutral drift signals. No LLM, no
+  interpretation, mutates nothing.
+- **This skill is where the agent interprets** — turning those facts into
+  inferred relationships and suggestions. **Never present an inference as a
+  fact**, and keep the layers in separate sections.
+
+## What `overview` answers
+
+A skills-scoped evidence pack — **not** `steward overview`'s ecosystem
+relationship graph (issue #12: inventory → guildmaster; judgment → steward):
+
+1. **Canonical skill set + versions** — every skill guildmaster supplies, its
+   origin (`guildmaster`, or a sibling it only re-broadcasts), and the current
+   canonical version, plus per-skill consumers.
+2. **Ledger view** — who-consumes-which-skill, read from `docs/skill-sources.md`.
+3. **Drift signals** — canonical skills no one consumes, canonical skills the
+   ledger doesn't track yet, and per-agent kit gaps. These feed `teach` /
+   `onboard`.
+
+**Pre-cutover** the guildmaster ledger is still a consumer-side view with no
+"Downstream" column, so the supplier ledger is empty and drift is inactive; the
+verb reports the canonical set and says so plainly (see `docs/cutover.md`).
+
+**`--scope mesh`** is the ledger-free alternative: it surveys every agent in the
+workspace (`<workspace>/*/culture.yaml`) live off the filesystem and reports, per
+agent, each canonical skill as **current** / **stale** (the agent's copy differs
+from guildmaster's by content fingerprint) / **missing**, plus any non-canonical
+"extra" skills. Use it to answer "what's missing or stale, and where" *today*,
+without waiting for the cutover. Still skills-scoped — no relationship graph.
+
+## When to use
+
+- An operator asks "what skills do we supply" / "what's the canonical set".
+- "Who has skill `<x>`?" / "who consumes what?" / "is anything drifting?"
+- "What should I `teach` next?" — overview's gaps are the input to `teach`.
+- Before `guild teach` / `guild onboard`, to see uncovered skills and kit gaps.
+
+## How to run
+
+One script. Pick the scope (or just run `guild overview`, which this wraps):
+
+```bash
+# Whole mesh — the canonical set + ledger + drift across all agents (default)
+.claude/skills/guild/scripts/overview.sh
+
+# One agent — that agent's kit + gaps (first positional → --scope self)
+.claude/skills/guild/scripts/overview.sh daria
+
+# Mesh survey — every agent's skills + missing/stale, live off the filesystem
+.claude/skills/guild/scripts/overview.sh --scope mesh
+
+# Machine-readable evidence for precise reasoning
+.claude/skills/guild/scripts/overview.sh --json
+.claude/skills/guild/scripts/overview.sh --scope mesh --json
+```
+
+The script prints the CLI's markdown by default: the canonical-skill table, a
+ledger section, and a drift section. The exact per-skill consumer and gap lists
+live in `--json`.
+
+## Narrate three layers — never blur them
+
+`guild overview` emits only deterministic facts; this skill is where you
+interpret them. Keep the three layers in separate sections, and never present
+an inference as a fact:
+
+1. **Observed facts.** Summarize the canonical set + versions/origins and the
+   ledger view in your own words — lead with what the counts reveal (the
+   canonical set, who's behind, who's unregistered). State only what the CLI
+   reported; don't reproduce the raw signal lists verbatim (read `--json` only
+   when you need an exact list to act on). Pre-cutover, say so plainly: the
+   ledger has no downstream column yet, so consumers are empty and drift is
+   inactive.
+2. **Inferred relationships** (mark clearly as inferred). Connect facts no
+   single ledger row states outright — e.g. two consumers vendored from the
+   same upstream skill *both* lag a canonical bump (a shared exposure), or a
+   skill only `guildmaster` carries is a single point of supply.
+3. **Suggestions** (kept separate from facts, and *named, not run*). Seed these
+   from the skills-scoped drift signals — for each, name the concrete next step
+   and the command that enacts it, then stop.
+
+### Signal → suggestion (skills-scoped only)
+
+These are the **skill/version** signals `guild overview` emits — guildmaster's
+supplier lane:
+
+| Drift signal (from `guild overview`) | Reading | Named follow-up — name it, do NOT auto-run |
+|--------------------------------------|---------|--------------------------------------------|
+| `unledgered_skills` | a canonical skill the ledger doesn't track (no owner row) | Fix the ledger: add it to `docs/skill-sources.md` |
+| `uncovered_skills` | a canonical skill no agent consumes (orphan) | Confirm intentional, then `teach` it, or retire it |
+| `agent_gaps` (per-agent missing skill) | a consumer behind / missing a skill | `guild teach --skill <name> --to <agent>` to close the gap |
+| agent not registered in the ledger | a sibling not yet onboarded | `guild onboard --agent <owner/repo>` |
+| consumer behind the canonical pin (post-cutover) | a team on an outdated procedure | Re-vendor: `guild teach` / `onboard` to the current pin |
+
+### Out of scope — steward's lane
+
+The **relationship** signals — `overlap`, `over-connected-agent`,
+`isolated-repo` — and the typed agent relationship graph are **not** narrated
+here. Those belong to steward's `org-overview` / `steward overview`. guildmaster
+narrates skills/version drift, not the ecosystem graph or alignment judgment.
+
+### Reflect-only
+
+This skill **sees, reflects, and suggests — it does not act.** For every
+suggestion, name the concrete next step and the command that enacts it, then
+stop. Editing the ledger, filing an issue, or running `teach` / `onboard` is a
+separate, explicit step the operator chooses. The skill writes nothing to disk
+and mutates no repo — output is the chat conversation only. Read-only: no
+`--apply`, no mutation, no network/LLM call.

guild_cli-0.5.0/.claude/skills/guild/scripts/overview.sh

@@ -0,0 +1,76 @@
+#!/usr/bin/env bash
+set -euo pipefail
+# overview — assemble the `guild overview` skills-supplier evidence pack for
+# narration.
+#
+# The guildmaster agent runs this, then narrates the supplier view (the
+# canonical skill set + versions/origins, the docs/skill-sources.md ledger, and
+# the drift signals that feed `teach` / `onboard`). See SKILL.md.
+# Deterministic glue only: resolve guildmaster's repo root, run from there,
+# resolve how to invoke guild, pick the scope, and delegate to `guild overview`.
+# No interpretation.
+#
+# Usage:
+#   overview.sh                  # whole ledger across the mesh (--scope all)
+#   overview.sh <agent>          # one agent's kit + gaps       (--scope self)
+#   overview.sh --scope mesh     # live filesystem survey of every agent
+#   overview.sh --json           # all, JSON evidence
+#   overview.sh <agent> --json   # one agent, JSON evidence
+#
+# Contract: the FIRST argument, if it does not start with '-', is the agent
+# (self scope). All remaining arguments pass through to `guild overview`.
+#
+# Exit codes:
+#   0   success (delegates to `guild overview`; its exit code propagates)
+#   1   environment error (no way to invoke guild)
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# Resolve guildmaster's repo root and run from there, so `guild overview` always
+# reports guildmaster's canonical set regardless of the caller's working
+# directory (the CLI reads its repo from cwd). Prefer git (robust); fall back to
+# climbing out of the fixed .claude/skills/<name>/scripts/ layout when git is
+# unavailable.
+REPO_ROOT="$(git -C "$SCRIPT_DIR" rev-parse --show-toplevel 2>/dev/null || true)"
+if [ -z "$REPO_ROOT" ]; then
+    REPO_ROOT="$(cd "$SCRIPT_DIR/../../../.." && pwd)"
+fi
+cd "$REPO_ROOT"
+
+# Resolve how to invoke guild: installed console script, then uv, then module.
+if command -v guild >/dev/null 2>&1; then
+    GUILD=(guild)
+elif [ -f "$REPO_ROOT/pyproject.toml" ] && command -v uv >/dev/null 2>&1; then
+    GUILD=(uv run --project "$REPO_ROOT" guild)
+elif command -v python3 >/dev/null 2>&1; then
+    GUILD=(python3 -m guild)
+else
+    echo "overview: cannot invoke guild (need 'guild', 'uv', or 'python3' on PATH)" >&2
+    exit 1
+fi
+
+# Honor an explicit --scope passed through (advanced use); otherwise pick one.
+has_scope=false
+for arg in "$@"; do
+    case "$arg" in
+        --scope | --scope=*)
+            has_scope=true
+            break
+            ;;
+    esac
+done
+
+overview_args=()
+if [ "$#" -gt 0 ] && [[ "$1" != -* ]]; then
+    # First arg is an agent → one-agent (self) scope.
+    agent="$1"
+    shift
+    $has_scope || overview_args+=(--scope self)
+    overview_args+=("$agent")
+else
+    # No leading agent → whole-ledger (all) view.
+    $has_scope || overview_args+=(--scope all)
+fi
+overview_args+=("$@")
+
+exec "${GUILD[@]}" overview "${overview_args[@]}"

{guild_cli-0.4.0 → guild_cli-0.5.0}/CHANGELOG.md

@@ -5,6 +5,79 @@ All notable changes to this project will be documented in this file.
 Format follows [Keep a Changelog](https://keepachangelog.com/). This project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.0] - 2026-05-24
+
+### Changed
+
+- **steward → guildmaster cutover (guildmaster's side).** Migrated
+  `docs/skill-sources.md` from the consumer-side "Upstream / Notes" view to the
+  **supplier shape**: a canonical-set table with a "Downstream copies (known)"
+  column (upstream reassigned `steward` → `guildmaster`), the devague-origin
+  re-broadcast table, and a "Retained by steward" section recording the
+  steward-specific skills (`org-overview`, steward's alignment `agent-config`
+  variant, `discord-notify`, `jekyll-test`, `notebooklm`) that stay with steward.
+  The downstream consumer lists were carried over verbatim from steward's ledger
+  at cutover. This activates resync-detection in `teach` / `onboard` and
+  skills-scoped drift in `guild overview --scope all` / `--scope self`
+  ([issue #1 §1](https://github.com/agentculture/guildmaster/issues/1),
+  `docs/cutover.md`).
+- **`docs/cutover.md`** updated to the in-progress state: guildmaster's side is
+  done and the handshake ping sent; the one remaining gate before `--apply` goes
+  live is steward's ack that it has stopped broadcasting (no two live
+  broadcasters, per [#10](https://github.com/agentculture/guildmaster/issues/10)).
+
+## [0.4.2] - 2026-05-24
+
+### Added
+
+- **`guild overview --scope mesh`** — a live filesystem survey of the whole
+  workspace, the answer to "what skills does every agent have, and what's
+  missing or stale, and where" without waiting for the cutover. Discovers every
+  agent (`<workspace>/*/culture.yaml`, via the new `discover_agents` helper) and
+  reports, per agent, each canonical skill as **current** / **stale** (the
+  agent's copy differs from guildmaster's by content fingerprint —
+  `skill_fingerprint`) / **missing**, plus any non-canonical "extra" skills.
+  Markdown + `--json`; `--workspace-root DIR` overrides the surveyed root
+  (default: the parent of this repo). Read-only, inventory only — no
+  dependency/relationship graph (that stays steward's lane). The existing
+  ledger-based `--scope all` / `--scope self` are unchanged.
+
+### Changed
+
+### Fixed
+
+- Mesh-survey robustness (Qodo review on #15): `discover_agents` and
+  `iter_skills` now skip non-UTF-8 / unreadable `culture.yaml` and `SKILL.md`
+  (one bad file in a surveyed repo no longer crashes the run), and
+  `skill_fingerprint` skips symlinks (never follows links outside the skill dir;
+  keeps the digest deterministic).
+
+## [0.4.1] - 2026-05-24
+
+### Added
+
+- **`guild` skill** — the backing affordance + narration skill for `guild
+  overview`, the supplier-overview half of the inventory split (sibling to the
+  vendored `agent-config` skill that backs `guild show`). `scripts/overview.sh`
+  is a deterministic wrapper that resolves how to invoke `guild` (installed →
+  `uv` → `python -m guild`) and delegates to `guild overview`; `SKILL.md` is the
+  **skills-scoped excerpt of steward's `org-overview` narration contract**
+  ([#12](https://github.com/agentculture/guildmaster/issues/12),
+  cite-don't-import): narrate three separated layers — observed facts, inferred
+  relationships, suggestions (each naming its enacting `teach` / `onboard` /
+  ledger command), reflect-only. Skills/version scope only — does NOT narrate
+  steward's relationship-graph signals (`overlap` / `over-connected-agent` /
+  `isolated-repo`). Recorded in `docs/skill-sources.md` as guildmaster-origin
+  (not vendored).
+
+### Changed
+
+- `SELF_SKILLS` now includes `guild` — guildmaster's own affordance skill is
+  excluded from the canonical kit it supplies to siblings (like `teach` /
+  `onboard`), since it wraps the `guild` binary and is meaningless elsewhere.
+
+### Fixed
+
 ## [0.4.0] - 2026-05-24
 
 ### Added

{guild_cli-0.4.0 → guild_cli-0.5.0}/CLAUDE.md

@@ -113,11 +113,17 @@ owns the mesh's *inventory* surfaces per
 **inventory → guildmaster; judgment ("how do agents relate / are they aligned?")
 → steward.** Neither verb clones `steward overview`'s relationship graph.
 
-- `guild overview [--scope all|self <agent>]` — the supplier view: canonical
-  skill set + versions/origins, the `docs/skill-sources.md` ledger, and drift
-  signals (uncovered skills, per-agent kit gaps). Pure-Python, read-only, **no
-  `--apply`**. Pre-cutover the ledger has no downstream column, so drift is
-  inactive and the verb says so (reads whichever ledger is authoritative).
+- `guild overview [--scope all|self <agent>|mesh]` — the supplier view:
+  canonical skill set + versions/origins, the `docs/skill-sources.md` ledger,
+  and drift signals (uncovered skills, per-agent kit gaps). Pure-Python,
+  read-only, **no `--apply`**. Pre-cutover the ledger has no downstream column,
+  so `--scope all`/`self` drift is inactive and the verb says so (reads
+  whichever ledger is authoritative). `--scope mesh` is the ledger-free
+  alternative: it surveys every agent in the workspace
+  (`<workspace>/*/culture.yaml`) live off the filesystem and reports, per agent,
+  each canonical skill as current / **stale** (content fingerprint differs from
+  guildmaster's copy) / **missing** — answering "what's missing or stale, and
+  where" today. Still inventory only — no relationship graph.
 - `guild show <path-or-suffix>` — one agent's full config: detected prompt file
   (`CLAUDE.md` / `AGENTS.md` / `GEMINI.md`), parallel `culture.yaml`, and the
   `.claude/skills` index. Thin wrapper that shells out to the vendored

{guild_cli-0.4.0 → guild_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: guild-cli
-Version: 0.4.0
+Version: 0.5.0
 Summary: guildmaster — an agent and CLI that manages skills for the AgentCulture mesh.
 Project-URL: Homepage, https://github.com/agentculture/guildmaster
 Project-URL: Issues, https://github.com/agentculture/guildmaster/issues
@@ -104,12 +104,13 @@ read-only — no `--apply`, no mutation, no drift verdict (judgment stays with
 
 | Verb | What it does |
 |------|--------------|
-| `guild overview [--scope all\|self <agent>]` | 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`. |
+| `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. |
 
 ```bash
 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_cli-0.4.0 → guild_cli-0.5.0}/README.md

@@ -86,12 +86,13 @@ read-only — no `--apply`, no mutation, no drift verdict (judgment stays with
 
 | Verb | What it does |
 |------|--------------|
-| `guild overview [--scope all\|self <agent>]` | 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`. |
+| `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. |
 
 ```bash
 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_cli-0.5.0/docs/cutover.md

@@ -0,0 +1,52 @@
+# Broadcaster cutover — steward → guildmaster
+
+guildmaster's `teach` / `onboard` verbs are the mesh's skill-broadcast surface
+(see the README "Supplier verbs" section and
+[issue #1 §1](https://github.com/agentculture/guildmaster/issues/1)). Standing
+them up does **not** make guildmaster the live broadcaster the moment the code
+merges. There is a hard precondition.
+
+## Status: in progress — awaiting steward's ack (2026-05-24)
+
+guildmaster's side of the cutover has landed: `teach` / `onboard` are green and
+reviewed, and `docs/skill-sources.md` has been migrated to the **supplier
+shape** (canonical set + Downstream column carried over from steward's ledger).
+The handshake ping (step 1 below) has been sent. The **one remaining gate** is
+steward's ack that it has stopped broadcasting (step 2). Until that ack lands,
+`--apply` stays **off** — operate in dry-run only.
+
+## Precondition (load-bearing)
+
+> **`teach` / `onboard` must not broadcast in production (`--apply`) until
+> `steward` has confirmed it stopped broadcasting.** While both sides could
+> broadcast, running guildmaster's verbs with `--apply` would mean **two live
+> broadcasters** and double-posted briefs — exactly what
+> [issue #10](https://github.com/agentculture/guildmaster/issues/10) forbids.
+
+`--dry-run` (the default) is always safe: it renders briefs and ledger /
+verification diffs without posting. Only `--apply` is gated.
+
+## The cutover, step by step
+
+1. **[done]** guildmaster's `teach` / `onboard` are green and reviewed.
+2. **[done]** guildmaster migrates `docs/skill-sources.md` to the supplier shape
+   and takes ownership of the ledger + broadcast role + skill-version tracking
+   (this PR).
+3. **[done]** guildmaster pings `steward` that the broadcast surface is ready.
+4. **[pending — steward]** steward **stops broadcasting**, retires its
+   supplier-ledger ownership, and acks the handover.
+5. **[pending]** From then on, guildmaster is the sole broadcaster. No overlap,
+   no two competing ledgers — and `--apply` goes live.
+
+Until step 4's ack lands, treat any guildmaster `--apply` broadcast as **off** —
+operate in dry-run only.
+
+## Why no separate `announce-skill-update` verb
+
+Issue #10 asked guildmaster to stand up its own `announce-skill-update`
+subcommand (steward's skill-major, one-skill-→-N-consumers verb). guildmaster
+fulfills the same broadcast **role** through `teach` / `onboard` instead — which
+are **agent-major** (one issue per agent, bundling per-skill sections). `teach`
+with one skill to one agent covers the single-skill case, so a separate verb
+would be redundant. The reconciliation is tracked on issue #10; see
+`docs/specs/` and `docs/plans/` for the converged design.

guild_cli-0.5.0/docs/skill-sources.md

@@ -0,0 +1,144 @@
+# Skill supplier — guildmaster's canonical skills
+
+guildmaster is the AgentCulture mesh's **skill supplier/manager**. Per the
+settled division of labor ([issue #1 §1](https://github.com/agentculture/guildmaster/issues/1))
+and the completed steward → guildmaster cutover (`docs/cutover.md`), guildmaster
+owns the canonical upstream copies of the cross-sibling skill set, this
+upstream/downstream ledger, the broadcast verbs (`teach` / `onboard`), and skill
+version tracking. `steward` has retreated to agent-alignment (`steward doctor` /
+`steward overview`) and is no longer the live broadcaster.
+
+This file is the deterministic upstream/downstream map handed over from
+steward's `docs/skill-sources.md` at cutover. Each skill has exactly one
+canonical source repo (the **upstream/origin** column); other repos hold
+downstream copies that may lag and should periodically re-sync from upstream.
+`guild teach` / `guild onboard` read the **Downstream** column to auto-frame each
+`(skill, agent)` as *new* vs *resync*, and `guild overview` reads it for
+skills-scoped drift.
+
+Everything here follows **cite, don't import**: each skill is *copied* into
+`.claude/skills/<name>/`, not symlinked or installed as a cross-repo dependency.
+Each consumer owns its copy and may diverge; nothing reaches across skill
+boundaries at runtime. When upstream changes, downstream copies do **not**
+auto-update — re-sync explicitly from the cited source.
+
+## Canonical supplied skills (upstream = `guildmaster`)
+
+These are the cross-sibling skills guildmaster owns and broadcasts. Source of
+truth is guildmaster's own copy under `.claude/skills/<name>/`; downstream
+consumers re-sync from there. Ownership transferred from `steward` at cutover;
+the downstream lists below were carried over from steward's ledger and are kept
+current by `guild overview --scope mesh`.
+
+| Skill | Upstream | Downstream copies (known) | Notes |
+|-------|----------|---------------------------|-------|
+| `agent-config` | `guildmaster` (`.claude/skills/agent-config/`) | — | Inventory variant backing `guild show` ([#12](https://github.com/agentculture/guildmaster/issues/12)); `show.sh` + `data/backend-fingerprints.yaml` vendored verbatim from steward, SKILL.md reframed from alignment-judgment to inventory + `type: command` added. **Forked from steward:** steward retains its own alignment-focused `agent-config` variant; the inventory variant is guildmaster's to supply. |
+| `cicd` | `guildmaster` (`.claude/skills/cicd/`) — layered on `agex pr` (in `agentculture/agex-cli`) | `afi-cli`, `agex-cli` (adapted-thin delegate — owns `agex pr`; see [agex-cli#53](https://github.com/agentculture/agex-cli/pull/53)), `agtag`, `antoine`, `appsec`, `auntiepypi`, `cfafi` (still named `pr-review`), `code-lens-cli`, `culture` (still named `pr-review`), `devague`, `katvan`, `lecodeur`, `lepenseur`, `seer-cli`, `telek` | Thin delegate to `agex pr` for lint / open / read / reply / delta, plus guildmaster's `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (composes `agex pr read --wait` with `status`, non-zero exit on Sonar ERROR / unresolved threads) extensions. **Inverted case:** agex-cli, as the `agex pr` upstream, vendors the skill adapted-thin — a `workflow.sh`-only pure delegate ([agex-cli#53](https://github.com/agentculture/agex-cli/pull/53)). Renamed from `pr-review` in steward 0.7.0; downstream copies may keep the old name on their own cadence. |
+| `communicate` | `guildmaster` (`.claude/skills/communicate/`) | `afi-cli`, `agex-cli` (identifier-only — vendored steward 0.11.0; scripts current as of 0.18.0), `agtag`, `antoine`, `appsec`, `auntiepypi`, `code-lens-cli`, `culture` (still named `coordinate`), `devague`, `katvan`, `lecodeur`, `lepenseur`, `seer-cli`, `telek` | Cross-repo + mesh communication: file issues / hand off briefs to sibling-repo agents (auto-signed), comment on existing issues, fetch issues to inline state into briefs, and send live messages to Culture mesh channels (unsigned — nick is the speaker). Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` (as `fetch-issues.sh`) in 0.9.1. Issue I/O backed by `agtag` (>=0.1) since steward 0.11.0 — signature resolves from local `culture.yaml` (override via `--as`). |
+| `doc-test-alignment` | `guildmaster` (`.claude/skills/doc-test-alignment/`) | `devague`, `lecodeur`, `lepenseur` | Stub; real implementation TBD. `scripts/check.sh` exits not-yet-implemented today. |
+| `pypi-maintainer` | `guildmaster` (`.claude/skills/pypi-maintainer/`) | `agtag` | Switches a PyPI package install between pypi / test-pypi / local. Generalised from the original culture-specific `change-package`. |
+| `run-tests` | `guildmaster` (`.claude/skills/run-tests/`) | `agtag`, `antoine`, `appsec`, `code-lens-cli`, `culture`, `culture-sonar-cli`, `devague`, `lecodeur`, `lepenseur`, `seer-cli`, `shushu`, `telek` | Coverage source resolves from `[tool.coverage.run]` in `pyproject.toml`, so the script is portable across siblings without modification. |
+| `sonarclaude` | `guildmaster` (`.claude/skills/sonarclaude/`) | `antoine`, `appsec`, `code-lens-cli`, `devague`, `lecodeur`, `lepenseur`, `seer-cli`, `telek` | SonarCloud API client. Project key resolves from `$SONAR_PROJECT` or `--project KEY`. |
+| `version-bump` | `guildmaster` (`.claude/skills/version-bump/`) | `afi-cli`, `agtag`, `antoine`, `appsec`, `auntiepypi`, `cfafi`, `code-lens-cli`, `culture`, `devague`, `lecodeur`, `lepenseur`, `seer-cli`, `shushu`, `telek` | Pure Python, prepends a Keep-a-Changelog entry; no per-repo customization needed. |
+
+> **How the downstream column is maintained.** The "Downstream copies (known)"
+> entries are kept in sync with guildmaster's own drift detector:
+> `guild overview --scope mesh` walks every workspace repo that declares an agent
+> (`culture.yaml`) and reports, per agent, each canonical skill as current /
+> stale / missing. Two classes carried over from steward are **not** yet captured
+> (deliberate follow-up, not oversight):
+>
+> - **No `culture.yaml`** (invisible to the detector): `tipalti`,
+>   `cultureagent`, `cultureflare`, `irc-lens`, `agentirc`, `zehut`.
+> - **Old skill-dir name** (`pr-review` / `coordinate`, which the detector
+>   doesn't canonicalize): `daria`, `shushu`, `culture-sonar-cli` vendor `cicd`
+>   under `pr-review`. `cfafi` / `culture` are already listed with a "still
+>   named `pr-review`/`coordinate`" note.
+>
+> `agentpypi` was **renamed to `auntiepypi`** on GitHub (the old name redirects);
+> `auntiepypi` is the live consumer recorded above.
+
+## Inbound workflow skills (origin = `devague`, re-broadcast by `guildmaster`)
+
+These three flow the **opposite** direction of guildmaster's supplier role: a
+sibling, [`devague`](https://github.com/agentculture/devague), is their
+author/upstream; guildmaster pulls them from devague (formerly via steward) and
+re-broadcasts them to the mesh. The `cite, don't import` rule still applies.
+They are the `idea → spec → plan → implement` workflow operators that drive the
+**deterministic** `devague` CLI (no LLM inside the CLI). Vendored at devague
+`0.11.1` ([`c04b595`](https://github.com/agentculture/devague/commit/c04b595)),
+**MIT**-licensed. Re-sync, when these later change upstream, from
+`../devague/.claude/skills/<name>/`.
+
+**Divergence from verbatim — `type: command` frontmatter.** devague's upstream
+SKILL.md files carry only `name` + `description`. The copies here **add
+`type: command`**: culture/agex's `core.skill_loader` requires `name`,
+`description`, **and** `type:`, and a SKILL.md lacking `type:` is *silently
+skipped* by `backends/claude_code/probe.py`. guildmaster declares an agent in
+`culture.yaml`, so the addition is load-bearing on the culture backend and
+harmless on `claude-code`. This is the only divergence from upstream.
+
+| Skill | Origin | Downstream copies (known) | Notes |
+|-------|--------|---------------------------|-------|
+| `think` | `devague` (`agentculture/devague`, `../devague/.claude/skills/think/`) | — (broadcast pending) | Operator for the **idea→spec** leg (announcement frame → capture/classify claims → interrogate with honesty conditions → park open vagueness → `export` once the frame converges). Renamed from `devague` in devague 0.4.0. **Divergence:** `type: command` added. Runtime dep: `uv tool install devague`. |
+| `spec-to-plan` | `devague` (`agentculture/devague`, `../devague/.claude/skills/spec-to-plan/`) | — (broadcast pending) | Operator for the **spec→plan** leg (`devague plan ...`): seed from a converged frame, cover every coverage target with acceptance-gated, acyclically-ordered tasks, park unknowns as risks, `export` once the plan converges. New in devague 0.4.0. **Divergence:** `type: command` added. Runtime dep: `uv tool install devague`. |
+| `assign-to-workforce` | `devague` (`agentculture/devague`, `../devague/.claude/skills/assign-to-workforce/`) | — (broadcast pending) | Operator for the **implementation** leg: reads `devague plan waves` (read-only) and fans out independent tasks to one agent per task per wave in isolated git worktrees, with main-agent TDD-gated merges. Three human gates: spec / split plan / final PR. The CLI stays non-orchestrating ([devague#20](https://github.com/agentculture/devague/issues/20)). New in devague 0.10.0. **Divergence:** `type: command` added. Runtime deps: `uv tool install devague`, `git worktree`, the vendored `cicd` skill (for gate-3 `agex pr open`). |
+
+Downstream is empty by design: these are still being introduced to the mesh.
+`guild teach --new --skill <name> --to <repos>` frames them as *new* skills to
+add fresh (not stale copies to resync).
+
+## guildmaster-origin skills (origin = `guildmaster`)
+
+These are guildmaster's **own** operator skills — not vendored from anyone and
+**not** part of the canonical set it supplies to siblings (so this table has no
+Downstream column and the supplier surface does not track them). They are the
+affordance + narration layer for guildmaster's own CLI surfaces.
+
+| Skill | Origin | Notes |
+|-------|--------|-------|
+| `guild` | `guildmaster` (this repo) | Houses guildmaster's own read-only supplier surfaces. Today: `scripts/overview.sh`, the wrapper backing the pure-Python `guild overview` verb ([#12](https://github.com/agentculture/guildmaster/issues/12)) — the skills-supplier half of the inventory split, sibling to the vendored `agent-config` skill that backs `guild show`. Its `SKILL.md` is the skills-scoped excerpt of steward's `org-overview` narration contract (three layers: facts / inferred / suggestions; reflect-only). Surfaces skills/version drift that feeds `teach` / `onboard`; does NOT narrate steward's relationship graph or judge alignment. |
+| `teach` | `guildmaster` (this repo) | Supplier broadcast verb: propagate a set of skills to a set of agents, one agent-major issue per target. Dry-run by default. |
+| `onboard` | `guildmaster` (this repo) | Supplier ceremony verb: onboard a new sibling with the full canonical kit + identity + ledger registration. Dry-run by default. |
+
+## Retained by `steward` (not guildmaster's to supply)
+
+The cutover transferred only the **cross-sibling canonical set** above. These
+steward skills stay with steward — they are steward-specific or otherwise not
+part of guildmaster's supplied kit, and guildmaster does not broadcast them:
+
+- `agent-config` (steward's **alignment-judgment** variant — distinct from
+  guildmaster's inventory fork above; resolves Culture agent suffixes).
+- `org-overview` — steward's reflect-only narration layer over `steward overview`;
+  not portable without steward installed.
+- `discord-notify` — generic webhook notifier; optional in the sibling baseline.
+- `jekyll-test` — conditional; only meaningful for siblings shipping a Jekyll /
+  Pages site.
+- `notebooklm` — generates GitHub blob URLs for repo docs.
+
+`cfafi`-origin skills (`cfafi`, `cfafi-write`, `poll`) remain with `cfafi`.
+
+## Vendoring policy
+
+- **Cite, don't import.** Skills are copied into the consuming repo, not
+  symlinked or installed as a dependency. Each consumer owns and may modify
+  their copy.
+- **Re-sync explicitly.** When upstream changes, downstream copies do not
+  auto-update; re-sync from the cited source and record the new pin here.
+  `guild teach` / `guild onboard` are the broadcast paths that notify consumers.
+- **Diverge intentionally.** A copy may diverge for repo-specific reasons
+  (e.g. the `type: command` addition above, or `cfafi`'s CloudFlare-API
+  reviewers in its `cicd`). Record the divergence here and in the skill's
+  `SKILL.md` frontmatter `description`.
+
+## When a skill should be promoted upstream
+
+A skill currently owned downstream (e.g. `poll` in `cfafi`) should be promoted
+to `guildmaster` when:
+
+1. At least one other sibling has copy-pasted it, OR
+2. Its scripts have no repo-specific assumptions (no hard-coded API credentials,
+   no per-product paths), AND
+3. Its `SKILL.md` describes a pattern (not a single product's workflow).
+
+Promotion is a manual decision.