loom

agents

Marketplace for the guild / griot / loom agent framework, shipped as a family of Claude Code plugins. Source-of-truth for skills, subagents, CLIs, and accumulated learnings used across Evan's projects (originally evolved in aart.camp, now lifted here so other projects — and other machines — can consume it without being coupled to one repo).

Install

The marketplace ships as six self-contained Claude Code plugins:

Plugin	What it provides	Depends on
griot@krambuhl	Learnings substrate: griot CLI + griot-* skills + judge/rewriter agents	—
guild@krambuhl	Antagonist-panel substrate: guild CLI + guild-* skills + whiteboard-* / evaluator-* / generator-* agents	—
loom@krambuhl	Project substrate: loom CLI + loom-* skills (plans, research, sessions, checkins, retros, archives)	guild, griot
ev@krambuhl	Execution loops: ev-loop-confidence, ev-loop-interactive, ev-run skills	loom, guild, griot
review-skill@krambuhl	Standalone code-review skill	—
agent-loop-full@krambuhl	Meta-bundle: zero-content plugin that cascade-installs the full family	all five above

Recommended: turnkey install with --scope user

claude plugin marketplace add krambuhl/agents
claude plugin install agent-loop-full@krambuhl --scope user

--scope user writes the enabled-plugins record to ~/.claude/settings.json (per-user-global, never lands in any repo). This is the recommended scope at Patreon and any environment where colleagues sharing the repo should NOT see the plugin in their own Claude Code sessions. See § Install scopes below for the load- bearing rationale.

agent-loop-full@krambuhl is zero-content; its only job is to cascade-install griot + guild + loom + ev + review-skill in dependency order. The cascade is a Claude Code feature (confirmed empirically in the migration's V4 smoke test).

Granular install (cherry-pick a plugin)

claude plugin marketplace add krambuhl/agents
claude plugin install loom@krambuhl --scope user

Each plugin's dependencies are declared in the marketplace manifest, so installing loom also pulls in guild + griot. Installing griot alone is fine too — no deps.

Install scopes

Claude Code supports four scopes for plugin installs. The relevant two:

• --scope user (recommended for personal + work machines): writes to ~/.claude/settings.json. Per-user-global. Invisible to colleagues by construction — nothing about the install lands in any project repo.

• --scope local (per-project variant): writes to <repo>/.claude/settings.local.json inside the project you're in when you run claude plugin install. Load-bearing requirement: the consumer repo's .gitignore MUST include .claude/settings.local.json. If the file is accidentally committed, colleagues cloning the repo will have the plugin honored on their own Claude Code sessions at local-settings precedence — the file is gitignored by Claude Code convention, not enforcement. The migration's V1 verification established this empirically via the docs (--scope project's "makes the plugin available to everyone who clones the project repository" doc language applies at local scope on whoever loads the repo). If you want a per-project install for any reason, triple-check the .gitignore first.

--scope user is the default recommended path because it avoids the .gitignore footgun entirely.

After install: per-project griot init

For consumer projects that want griot to land learnings/captures into a project-local learnings/ tree (so the rollup can grow over time without polluting the user's global learnings), run inside each consumer repo:

griot init

This idempotently creates learnings/{session-notes,nightly}/ and appends learnings/ to the project's .gitignore if it's not already present. No-ops on re-run.

What's inside