agentleFS
memi-designmemi-design/design-skills/skills/hermes-agent-bridge/SKILL.md

hermes-agent-bridge

Skill7 starsChanged 4 months agoMITView on GitHub

Run Hermes Agent from Memoire with CLI, skills, toolsets, worktree, and session recipes.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run Hermes Agent from Memoire with CLI, skills, toolsets, worktree, and session recipes.

    line 8
  2. Distinctive:

    Use this Note when a Memoire or Studio run needs hermes agent setup, Hermes CLI delegation, skills preload, worktree agent run.

    line 12
  3. Very specific:

    Check hermes --version and hermes doctor before wiring a session.

    line 16
  4. Very specific:

    Use hermes chat -q for non-interactive delegation and hermes --tui for interactive terminal work.

    line 17
  5. Very specific:

    Use hermes -w for isolated git worktree execution when multiple agent lanes should not collide.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hermes Agent Bridge

Run Hermes Agent from Memoire with CLI, skills, toolsets, worktree, and session recipes.

When to Use

Use this Note when a Memoire or Studio run needs hermes agent setup, Hermes CLI delegation, skills preload, worktree agent run.

Workflow

  1. Check hermes --version and hermes doctor before wiring a session.
  2. Use hermes chat -q for non-interactive delegation and hermes --tui for interactive terminal work.
  3. Preload focused skills with hermes -s skill-name or hermes chat -s skill-name -q ....
  4. Use hermes -w for isolated git worktree execution when multiple agent lanes should not collide.
  5. Record the provider, model, skills, workspace, and resume id in the Memoire run note.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.