local-knowledge-router

Local Knowledge Router

When to use

Use this skill before guessing paths or doing broad file searches when a user asks about local or private operational knowledge, including:

• installed or custom Hermes skills and their support docs;
• generated tool OKFs, runbooks, operational docs, and memory docs;
• helper scripts and automation entry points;
• cron jobs and scheduled maintenance;
• MCP servers and wrapper scripts;
• service workflows in the configured local source tree.

The plugin indexes whole artifacts. It identifies the first artifact to inspect; it does not replace reading that source.

Workflow

1. Search for the user's intent:

   knowledge_search(query="backup runbook", limit=8)
   knowledge_search(query="paperless review automation", limit=8)
   knowledge_search(query="siyuan mcp wrapper", limit=8)
   

2. Fetch the best artifact before acting:

   knowledge_get(artifact_id="skill:example-skill", include_neighbors=true)
   

   Use knowledge_neighbors separately when graph context will help:

   knowledge_neighbors(artifact_id="cron:daily-review", limit=20)
   

3. Inspect the routed source of truth:

   • skill → load it with skill_view.
   • script → read the script and help text before running it.
   • tool_okf → use it as routing context, then inspect the live tool schema/docs before high-impact calls.
   • runbook, memory_doc, doc, or skill_support_doc → read the file before changing systems.
   • cron_job → verify the live cron registry before mutating jobs.
   • mcp_server → inspect the live wrapper/config before troubleshooting.

4. Check freshness when it matters. Managed lookups rebuild an index that is missing, corrupt, older-format, or marked dirty by completed tool-OKF publication. They do not detect ordinary source-file, cron-registry, or MCP-config changes. When those changed recently or results look stale, force a rebuild:

   knowledge_search(query="new helper script", limit=8, rebuild=true)