agent-config
Show a Culture agent's full configuration in one read-only view: its system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the agent's local .claude/skills index. Use when an operator says "show agent <name>", "what does <agent> look like", or before teaching/onboarding an agent and you need to see its current kit + config. Backs the `guild show` verb. Vendored from steward (cite-don't-import); inventory only — it reports, it does not judge alignment or drift.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-29
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- agent-config
- type
- command
- description
- Show a Culture agent's full configuration in one read-only view: its system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the agent's local .claude/skills index. Use when an operator says "show agent <name>", "what does <agent> look like", or before teaching/onboarding an agent and you need to see its current kit + config. Backs the `guild show` verb. Vendored from steward (cite-don't-import); inventory only — it reports, it does not judge alignment or drift.
02 资源文件 2
- 参考文档data/backend-fingerprints.yaml2.0 KB
- 脚本scripts/show.sh4.6 KB
03 SKILL.md 正文
agent-config — surface a Culture agent's config in one view
guildmaster is the mesh's skills supplier and owns the inventory surfaces: "what kit + config does this agent have?" This skill answers exactly that for a single agent, showing the three artifacts that together define it:
- System-prompt file (
CLAUDE.md/AGENTS.md/GEMINI.md) — the prompt-side guidance for the agent's backend. The script detects which file is present from a backend-fingerprint registry. culture.yaml— the runtime-side config (agents:list withsuffix,backend,model,system_prompt,channels,tags,acp_command,extras). Lives parallel to the prompt file at the project root..claude/skills/*/SKILL.md— the per-project skills the agent can invoke, one line each (name + truncated description).
This is the inventory half of the steward → guildmaster split
(issue #12): it reports
the config, it does not interpret drift or judge alignment. The relationship
graph and the "is this agent aligned?" judgment stay with steward overview /
steward doctor.
When to use
- Before
guild teach/guild onboard— see an agent's current kit + config. - When an operator asks "show me agent
<name>" or "what does<agent>run". - Read it, don't guess — before answering a question about what an agent does.
How to run
One script, two ways to call it (or just run guild show, which wraps it):
# Path mode — point at any directory with a prompt file + culture.yaml
.claude/skills/agent-config/scripts/show.sh ../culture
# Suffix mode — resolve a registered agent suffix via the Culture server's
# manifest (location set by culture_server_yaml in skills.local.yaml)
.claude/skills/agent-config/scripts/show.sh daria
Output is three sections: the detected system-prompt file, culture.yaml (or
(missing)), and a one-line summary per local skill (name + description,
truncated to 120 chars).
What to look at in culture.yaml
| Field | Why it matters |
|---|---|
suffix |
Identifies the agent on the mesh. |
backend |
One of claude / codex / copilot / acp. The all-backends rule means a feature in one must land in all four. |
model |
Drift here changes behavior silently. |
system_prompt |
Should not contradict the prompt file. |
channels |
Where the agent listens. |
tags, extras, acp_command |
Backend-specific. |
Notes
- Read-only. The script never edits agent files. It reports; it does not flag or fix drift — that judgment is steward's lane.
- Backend-aware. Prompt-file detection comes from
data/backend-fingerprints.yaml(theprompt:mapping), falling back to the built-in(CLAUDE.md AGENTS.md GEMINI.md)list if the registry is absent. - Per-machine config. Suffix mode reads
culture_server_yamlfrom.claude/skills.local.yaml(git-ignored), falling back to.claude/skills.local.yaml.example. - Vendored from steward (
agent-config). guildmaster owns this copy and may diverge; re-sync from steward's canonical copy when it changes. Divergences: the SKILL.md is reframed for guildmaster's inventory role and addstype: commandfor the culture backend's skill loader.
04 同仓库更多 Skills
sample
Fixture skill proving the .qwen/skills leg carries at least one skill.
sample
Fixture skill proving the .qwen/skills leg carries at least one skill.
sample
Fixture skill proving the .qwen/skills leg carries at least one skill.
think
Think a vague feature idea into a buildable spec by working backwards (the idea→spec leg; drives the `devague` CLI). Start from the announcement ("pretend it shipped"), capture and classify claims, interrogate them with honesty conditions and hard questions, park open vagueness as a first-class object, and export a spec only once the frame *converges*. Use when the user says "think this through", "spec this", "work backwards", "turn this idea into a spec", "announcement frame", or "devague", or when a feature request is too vague to build yet. Explore scope first when the idea touches an existing codebase — the sibling `scope` skill is the optional opening leg ahead of `think`. Once a spec exports, hand off to the sibling `spec-to-plan` skill to turn it into a plan. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.
summarize-delivery
Close the loop after an `assign-to-workforce` run by turning what actually happened into an accountability artifact — planned versus actual delivery, mid-work decisions, plan drift, evidence-backed delivery claims, and remaining work. The plan the user confirmed is the contract; this skill records where execution obeyed it, where it changed, and what is genuinely safe to claim as delivered. Runs on complete, partial, AND failed runs — failure is reported faithfully, never smoothed over. Use when the user says "summarize delivery", "delivery summary", "wrap up", "close the loop", "what did we actually ship", or "plan versus actual", or after `assign-to-workforce` merges (or fails to merge) a plan's waves. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the inbound skills here.
spec-to-plan
Turn a converged devague spec into a buildable plan by working forwards (the spec→plan leg; drives the `devague plan` CLI group). Seed a plan from a converged frame, add tasks that collectively cover every coverage target (the frame's confirmed claims + honesty conditions), give each task acceptance criteria and an honest dependency order, park genuine unknowns as first-class risks, and export a plan only once it *converges*. Use when the user says "spec to plan", "stp", "turn this spec into a plan", "plan this spec", "make a build plan", or after the `think` skill exports a spec. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.