Hermes Local Knowledge
stepanov1975/hermes-local-knowledge
Hermes plugin that routes a local question to the skill, script, runbook or document to open first
Hermes Local Knowledge is a Hermes Agent plugin that indexes your local skills, scripts, docs, cron jobs and MCP servers and tells the agent which whole artifact to inspect first. It is an artifact router, not chunk-based retrieval.
What Hermes Local Knowledge does
Hermes Local Knowledge routes a question about your own setup to the single artifact the agent should read first: a skill, a support document, a script, a runbook, a cron job, an MCP server or a generated tool note. The README is explicit that it is not chunk RAG. Search results are routing hints, and the agent is expected to read the selected source before acting.
The index draws on a curated source_root plus the Hermes runtime. Skills come from configured custom_skill_dirs and $HERMES_HOME/skills, scripts from script_dirs, cron jobs from $HERMES_HOME/cron/jobs.json, and MCP servers from the mcp_servers entries in config.yaml. Markdown docs are indexed when include_markdown_docs is enabled. The plugin registers five tools in the local_knowledge toolset: knowledge_search, knowledge_get, knowledge_neighbors, knowledge_feedback and knowledge_usage_report. Tool replies stay short and carry only routing metadata and warnings.
Key features
- knowledge_search finds likely artifacts by intent, with an optional type filter and forced rebuild
- knowledge_get fetches one artifact by ID, optionally with graph neighbors
- knowledge_neighbors walks conservative graph edges between artifacts
- knowledge_feedback records useful, missing, stale or wrong_artifact verdicts locally
- knowledge_usage_report summarizes usage, failures and zero-result queries
- Indexes skills, support docs, scripts, runbooks, cron jobs and MCP server entries
When to use it
- Finding which runbook or skill covers a task in a large personal Hermes setup
- Locating the cron job or MCP server entry that handles a given integration
- Reviewing which lookups returned nothing so missing documentation can be written
Who it is for: Hermes Agent users with many skills, scripts and runbooks who want the agent to pick the right one before it starts work.
How it fits with Hermes Agent
Built as a Hermes Agent plugin, tagged hermes-plugin, that reads the Hermes skills directory, cron jobs and config.yaml MCP entries directly.
FAQ
What is Hermes Local Knowledge?
Hermes Local Knowledge is a plugin that routes a local question to the whole artifact an agent should inspect first, such as a skill, script, runbook, cron job or MCP server. It is a router rather than chunk-level RAG.
Does Hermes Local Knowledge work with Hermes Agent?
Yes. It is written as a Hermes Agent plugin and reads $HERMES_HOME for skills, cron jobs and MCP configuration. It registers its tools in the local_knowledge toolset.
Is Hermes Local Knowledge free and open source?
Yes. The repository is released under the MIT license.
Similar memory for Hermes Agent
All memoryLocal-first project memory for AI coding agents, shared through plain files in .memory-bridge
Trainspotting31 MemoryBuddyShared memory server on Cloudflare Workers that Hermes and other MCP clients read and write
labyrinth-analytics LoreConvoLocal SQLite memory for AI sessions that carries context across Claude Code, Cursor, Codex and Hermes
aristoapp Membase Plugin for HermesPersistent long-term memory for Hermes Agent using hybrid vector search and a knowledge graph
alejandroiglesias Hermes DreamingBackground memory consolidation plugin that tidies Hermes MEMORY.md and USER.md on a schedule
haitao338241-collab Hermes Hindsight GuideChinese guide to a local Hermes memory setup with Ollama and Hindsight that reduces memory clutter
Related guides: SOUL.md for Hermes Agent: what it is and how to write one · Run multiple Hermes agents with profiles