Academy → Developer guideOfficial documentation · clear explanation

Build a Hermes Plugin

Build a Hermes الإضافات

Developer35 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Build a Hermes Plugin as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Portable Agent Plugins v1 packages, What you're building, Step 1: Create the plugin directory, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Build a Hermes Plugin without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Tool
A structured action the agent can call to read or change something.
Official page description

Step-by-step guide to building a complete Hermes plugin with tools, hooks, data files, and skills

Topic map

What does the source say, and in what order?

  1. 01
    Portable Agent Plugins v1 packages

    Start here to understand the core idea or structure.

  2. 02
    What you're building

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Step 1: Create the plugin directory

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Step 2: Write the manifest

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Step 3: Write the tool schemas

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Step 4: Write the tool handlers

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Step 5: Write the registration

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Step 6: Test it

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Debugging plugin discovery

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Your plugin's final structure

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

my-portable-plugin/ ├── plugin.json ├── skills/ │ └── summarize/ │ ├── SKILL.md │ └── references/ └── mcp.json
hermes plugins install owner/repository --no-enable hermes plugins list hermes plugins enable <plugin-name>
mkdir -p ~/.hermes/plugins/calculator cd ~/.hermes/plugins/calculator
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Build a Hermes Plugin” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?