Knowledge Router

Build a lightweight routing layer across existing knowledge sources such as MEMORY.md, daily memory files, self-improving notes, skill references, and audit...

lethehades

@lethehades

What This Skill Does

Analyzes a query's intent and routes it to the most relevant knowledge source (e.g., MEMORY.md, daily memory files, skill references, audit logs) before performing broad reading. It classifies sources by role, infers intent as rule/fact/method/evidence/improvement, recommends primary and secondary sources, and emits promotion hints when knowledge is mature enough to move to a more durable layer.

Replaces manually guessing which knowledge file to consult first by providing a lightweight, intent-driven routing layer across all existing knowledge sources.

When to Use It

  • Route a new question to the correct knowledge source before reading broadly
  • Decide whether a query is best answered by MEMORY.md, daily notes, or skill references
  • Detect which knowledge fragments are mature enough to promote into a durable layer
  • Classify a query's intent as rule, fact, method, evidence, or improvement
  • Generate a routing report that recommends primary and secondary sources for a given query
  • Avoid redundant re-storing of knowledge by routing instead of duplicating

Install

$ openclaw skills install @lethehades/knowledge-router

Knowledge Router

Route queries to the right knowledge layer before doing broad reading.

Core workflow

  1. Scan known knowledge sources and classify them by role.
  2. Infer the query intent: rule, fact, method, evidence, or improvement.
  3. Recommend primary and secondary sources.
  4. Emit promotion hints when knowledge seems mature enough to move upward into a more durable layer.

Read references as needed

  • Read references/source-types.md for the knowledge source model.
  • Read references/routing-rules.md for intent-to-source routing rules.
  • Read references/promotion-rules.md for when knowledge should be promoted or extracted.
  • Read references/report-format.md for the report structure.
  • Read references/release-minimal.md before packaging or publishing so the first public surface stays minimal.

Use scripts as needed

  • Use scripts/knowledge_router.py "<query>" [--scope ...] [--output report.txt] to build a routing report.

Operating rules

  • Prefer routing over re-storing knowledge.
  • Prefer a small number of clearly justified sources over broad search noise.
  • Treat audit logs as evidence, not as the first answer source for general method questions.
  • Keep the first version focused on source typing, query intent, and recommendation quality.

Top skills in this category