Hermes BibleUnofficial Docs
← All docs Docs / Guides & Tutorials

Build a Hermes Plugin

This guide walks through building a complete Hermes plugin from scratch. By the end you'll have a working plugin with multiple tools, lifecycle hooks, shipped d

Guides & Tutorials
Section
Guides & Tutorials
Source
hermesbible.com/docs/guides/build-a-hermes-plugin

This guide walks through building a complete Hermes plugin from scratch. By the end you'll have a working plugin with multiple tools, lifecycle hooks, shipped d

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. What you're building
  2. Step 1: Create the plugin directory
  3. Step 2: Write the manifest
  4. Step 3: Write the tool schemas
  5. Step 4: Write the tool handlers
  6. Step 5: Write the registration
  7. Step 6: Test it
  8. Debugging plugin discovery
  9. Your plugin's final structure
  10. What else can plugins do?
  11. Ship data files
  12. Bundle skills
  13. Gate on environment variables
  14. Lazy-install optional Python dependencies

Section map

What you're building

Maps what you're building to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 1: Create the plugin directory

Maps step 1: create the plugin directory to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 2: Write the manifest

Maps step 2: write the manifest to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 3: Write the tool schemas

Maps step 3: write the tool schemas to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 4: Write the tool handlers

Maps step 4: write the tool handlers to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 5: Write the registration

Maps step 5: write the registration to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 6: Test it

Maps step 6: test it to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Debugging plugin discovery

Maps debugging plugin discovery to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: What you're building, Step 1: Create the plugin directory, Step 2: Write the manifest, Step 3: Write the tool schemas, Step 4: Write the tool handlers. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: build, plugin, walks, through, building. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitGuides & Tutorials documentation

Use when you need orientation for build a hermes plugin before applying exact upstream commands.

Verify firstWhat you're building

Open the source anchor for What you're building and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
  2. Start with the source section for What you're building; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Step 1: Create the plugin directory if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page