# Guild: Hermes Agent plugin

> Shared skill library for a team's Hermes agents, or for one person's machines and profiles, kept in a git repository the team controls.

Canonical: https://hermeswatcher.com/plugins/guild  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/guild  
Last updated in catalog: 2026-11-14

Shared skill library for a team's Hermes agents, or for one person's machines and profiles, kept in a git repository the team controls. A skill an agent saved is scrubbed of API keys, home folder paths, e-mail addresses and private IPs, pushed as a proposal branch, and merged only after a teammate approves it from the CLI, TUI or Desktop. Each member's agent then loads approved skills read-only. If an agent tries to edit a team skill, a pre_tool_call hook refuses the edit and tells it to use guild_propose. Hermes Desktop gets a Guild page to review diffs and approve or decline. Commands: `hermes guild init|join|propose|review|show|approve|reject|revert|log` and `/guild`.

## Good to know before installing

Runs local `git` subprocesses (repository hooks disabled, no terminal prompts, only the environment variables git and ssh need) that fetch from and push to the remote you configure, using your existing git credentials; contacts nothing else and stores no credentials. Only the files of a skill you propose, or that your agent proposes after the approval prompt, leave the machine, with your member name in the commit. Optional background sync at session start (auto_sync_minutes, default 15, 0 turns it off); a sync moves a local skill identical to the team copy, or your own accepted proposal, into the plugin's backups folder. In a solo guild proposals are committed straight to main with no review. `init` and `join` add the library folder to the profile's skills.external_dirs and `leave` removes it. The write check reads tool arguments and does not inspect execute_code. The reviewer list is enforced by the plugin only; use branch protection on the git host for a server-side guarantee.

From the plugin's catalog listing.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install guild
```

2. Said no? Turn it on later:

```bash
hermes plugins enable guild
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Automation & multi-agent
- Maintained by: Nnadijoshuac (Community)
- Needs: No API keys declared
- Adds tools: `guild_status`, `guild_sync`, `guild_propose`, `guild_review`
- Requires Hermes: `>=0.23.0`
- Version: 0.1.0
- In the catalog since: 2026-11-14

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/guild)
- [Source code](https://github.com/Nnadijoshuac/hermes-guild#readme)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt
