knowledge-router
Route one question or source event through a supplied knowledge catalog to validated source, owner, escalation, and follow-up skill references. Use for evidence discovery and ownership routing, not broad business-action fanout or answering the question itself.
- License 许可
- MIT
- 所属仓库
- ZachDreamZ/runx
- 最近更新
- 2026-07-17
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- knowledge-router
- runx
- { "category": "ops" }
- description
- Route one question or source event through a supplied knowledge catalog to validated source, owner, escalation, and follow-up skill references. Use for evidence discovery and ownership routing, not broad business-action fanout or answering the question itself.
02 资源文件 2
- 脚本validate_route.mjs4.4 KB
- 参考文档X.yaml5.5 KB
03 SKILL.md 正文
Knowledge Router
Produce a validated retrieval and ownership route from a bounded source catalog. This skill decides where evidence should come from and who owns the answer; it does not answer the question or perform the follow-up operation.
business-ops routes a business signal across action lanes such as release,
outreach, spend, and proof. knowledge-router instead resolves references
inside an explicit knowledge catalog. Its deterministic validator rejects
invented sources, owners, and skills.
Source catalog
Supply:
{
"sources": [
{"id": "auth-docs", "kind": "docs", "summary": "API authentication and key scopes"}
],
"owners": [
{"id": "security-team", "domains": ["authentication"]}
],
"skills": [
{"id": "research", "purpose": "Resolve a bounded source-backed question"}
]
}
Every selected reference must exist in the corresponding catalog collection. The route may return no follow-up skill when more context or manual review is the honest outcome.
Procedure
- Match the question or event to supplied source summaries and owner domains.
- Propose the smallest source set needed to resolve the question.
- Select an owner only when the catalog supports the ownership relationship.
- Select a follow-up skill only when its declared purpose matches the next job.
- Use
manual_reviewfor consequential legal, billing, security, privacy, or destructive decisions—not merely because the topic belongs to those teams. - Validate every source, owner, and skill reference deterministically.
- Return
needs_more_contextwhen no supported route exists.
Output
route: domain, rationale, and validated source references.source_matches: validated source references and matching signals.owner_recommendation: validated owner reference, rationale, and escalation posture, ornull.next_skill: validated skill reference and rationale, ornull.verdict:routed,needs_more_context,manual_review, or the deterministic validator'srefusedresult for an invented reference.validation: catalog digest inputs, invalid-reference findings, and result.
Inputs
question(required): question, event, or thread summary to route.available_sources(required): explicitsources,owners, andskillscollections.constraints(optional): allowed sources, sensitivity, excluded systems, or preferred owners. Constraints are not authority.
04 同仓库更多 Skills
zapier-handoff
Validate a runx execution context and hand off a governed payload to a Zapier Catch Hook with scoped auth, idempotency, and receipt expectations.
x402-pay
Execute a governed x402 payment by delegating to the canonical spend flow with the x402 runtime path selected.
work-plan
Decompose a build objective into governed runx execution steps.
web-fetch
Fetch and extract one web source within an explicit allowlist, returning the content by digest with full provenance.
weather-forecast
Normalize provider weather evidence into an action-safe forecast packet with provenance, uncertainty, and stop conditions for downstream agents.
vuln-triage
Triage dependency or ecosystem vulnerability risk into remediation and advisory packets, grounding on verified CVE evidence when it is supplied.