route

Routes content to the correct knowledge base using tags, rules, and model classification.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill route-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: route
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/kb/skills/route
Command: npx skills add https://github.com/AlmogBaku/aos --skill route-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a skill or capability holds content to file but the destination knowledge base is not obvious, this Skill resolves one write to exactly one base without interrupting the user mid-capture, while guaranteeing that model-classified content never lands in a shared base. ## Core Features & Use Cases - Ordered resolution pipeline: Tries explicit user tags first, then channel bindings and keyword rules from the registry, then a single model classification call, and finally a default-base fallback. - Shared-base safety invariant: Model classification only runs when every candidate base is private, and kb lint fails any shared base carrying an llm-routed record. - Grant-aware candidate filtering: Only bases where the writing subject holds a route-into grant are considered; with zero candidates the payload is handed back tagged refused and recorded via kb refuse. - Use Case: A capture pipeline receives a note from a chat channel; the Skill matches the channel binding in the registry, writes it to the bound base with kb capture, and stamps kb_routing.method=rule via kb set. ## Quick Start Ask your agent to file this content in the right knowledge base using the route skill, reading the registry at $AOS_REGISTRY to pick the destination.

Frequently Asked Questions about route

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route content to the correct knowledge base automatically?▼

Read the kb-registry.yaml for base entries, then resolve in order: explicit user tags, channel bindings and keyword rules, a single model classification call against private bases only, and finally the default base. Stamp the result with kb set using kb_routing.method and kb_routing.status fields.

How does knowledge base routing decide between rules and model classification?▼

Rules always run first: channel bindings, then case-insensitive keyword substring matches, with no model call. Model classification runs only if no rule matched and every remaining candidate base is private, accepting results at or above the confidence_bar of 0.7.

Can model-classified content be written to a shared knowledge base?▼

No. Model classification is only allowed when every candidate base has audience private, and shared bases accept only explicit-tagged or rule-matched writes. The kb lint command fails any shared base carrying a kb_routing.method of llm.

What happens when no knowledge base grants route-into permission?▼

The payload is handed back to the caller tagged kb_routing.status refused, and a refusal entry is recorded with kb refuse against the explicitly named default base. The content is never silently dropped.

Why does routed content land in the default base with status uncertain?▼

The fallback step writes to the default base with method default and status uncertain when no tag, rule, or confident model match exists. The nightly pass re-classifies these but files better destinations as findings for human review rather than moving them.