All plugins

puppetmaster-learn

Turns a Puppetmaster swarm into a Hermes skill. Puppetmaster runs durable worker jobs (swarms and flow graphs) for an agent. When a Hermes session ends, this plugin finds the swarm that finished during that session in the session's directory and, if it produced findings or a patch, writes its goal and findings (title, location, severity, failure scenario, evidence) as a skill candidate under $HERMES_HOME/skills-candidates/. Promote it with puppetmaster skills promote-candidate <slug>. It never writes a live skill or starts an agent or job, and writes one candidate per job. Needs the Puppetmaster CLI (PyPI puppetmaster-ai). Disclosure — at session end it reads the ending session's cwd and started_at from the Hermes session store (read-only, no messages), runs up to three read-only Puppetmaster CLI commands (last --json, status, artifacts) as child processes in that directory, 15 s timeout each, stdin closed, and reads the mcp_servers.puppetmaster entry of Hermes config.yaml (no credentials); it writes only under $HERMES_HOME/skills-candidates/; no network, no threads or background processes, no telemetry, no dependencies beyond the standard library.

professorpalmer478Automationv0.2.1Updated 6 days ago

About

Turns a Puppetmaster swarm into a Hermes skill. Puppetmaster runs durable worker jobs (swarms and flow graphs) for an agent. When a Hermes session ends, this plugin finds the swarm that finished during that session in the session's directory and, if it produced findings or a patch, writes its goal and findings (title, location, severity, failure scenario, evidence) as a skill candidate under $HERMES_HOME/skills-candidates/. Promote it with puppetmaster skills promote-candidate <slug>. It never writes a live skill or starts an agent or job, and writes one candidate per job. Needs the Puppetmaster CLI (PyPI puppetmaster-ai). Disclosure — at session end it reads the ending session's cwd and started_at from the Hermes session store (read-only, no messages), runs up to three read-only Puppetmaster CLI commands (last --json, status, artifacts) as child processes in that directory, 15 s timeout each, stdin closed, and reads the mcp_servers.puppetmaster entry of Hermes config.yaml (no credentials); it writes only under $HERMES_HOME/skills-candidates/; no network, no threads or background processes, no telemetry, no dependencies beyond the standard library.

puppetmaster-learn

A Hermes plugin that turns a finished Puppetmaster
swarm into a Hermes skill candidate.

Puppetmaster runs durable worker jobs (swarms and flow graphs) for an agent.
A swarm that finds something or produces a patch holds knowledge that is
worth keeping. This plugin keeps it: when a Hermes session ends, it writes
that swarm's goal and findings as a SKILL.md that you can review and promote.

What it does

When the session ends (on_session_finalize: quit, /new, a -z run, or a
gateway reset), the plugin:

  1. Reads the session's working directory and start time from the Hermes
    session store. This is correct in the gateway too, where one process ends
    many sessions.
  2. Asks the Puppetmaster CLI for the latest job of that directory
    (puppetmaster last --json).
  3. Continues only when that job is complete, finished during this session,
    produced findings or a patch, and has no candidate yet.
  4. Reads the job goal (puppetmaster status <job>) and its finding artifacts
    (puppetmaster artifacts <job>). Each finding keeps its title, location,
    severity, failure scenario and evidence.
  5. Writes a candidate. Where Hermes shows plugin session-end messages, it
    also tells you where the candidate is:
~/.hermes/skills-candidates/<YYYYMMDD>-<slug>/
  SKILL.md         # frontmatter (name, description), goal, findings, source job
  candidate.json   # job_id, goal, cwd, created_iso, source

The plugin never writes a live skill. To use a candidate, review it, then run
puppetmaster skills promote-candidate <slug> (or move the folder into
~/.hermes/skills/ yourself). puppetmaster skills list-candidates lists them.

Install

You need Puppetmaster (pip install puppetmaster-ai or uv tool install puppetmaster-ai)
with the puppetmaster command on PATH.

hermes plugins install puppetmaster-learn
hermes plugins enable puppetmaster-learn

puppetmaster setup can also copy and enable the plugin for you.

If Hermes starts with a short PATH (for example from a desktop launcher), the
plugin uses the interpreter in the mcp_servers.puppetmaster entry of Hermes
config.yaml, if that file exists. If it finds no Puppetmaster, it does nothing.

Disclosure

  • Child processes. At session end it runs up to three Puppetmaster CLI
    commands (last --json, status, artifacts) in the session's working
    directory, each with a 15 second limit. These commands only read job state.
  • Reads outside its own data. It reads the ending session's cwd and
    started_at from the Hermes session store (read-only), Puppetmaster's local
    job store (through the CLI), and the mcp_servers.puppetmaster entry of
    Hermes config.yaml. It reads no messages and no credentials.
  • Writes. It writes only under <hermes home>/skills-candidates/. The
    home follows the active Hermes profile.
  • No network, no background process, no telemetry. The plugin makes no
    network calls and starts no thread or daemon. It does not start an agent or
    a Puppetmaster job.
  • Failures are silent. Any error ends the hook with no message. Session
    teardown continues.

README from the reviewed commit d43d027; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section