tiered-routing

Route requests through pattern matching, session state, keyword lookup, then LLM classification.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill tiered-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tiered-routing
Source: https://github.com/JNZader/javi-ai/tree/main/own/skills/tiered-routing
Command: npx skills add https://github.com/JNZader/javi-ai --skill tiered-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

4-tier cost-optimized routing protocol for the SDD orchestrator. Resolves routing via pattern match, session state, keyword lookup, and LLM classification — in that order. Trigger: When the orchestrator needs to route a user request to a skill or agent. Always active as routing logic.

Frequently Asked Questions about tiered-routing

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

FAQPage Schema
How do I reduce token costs for LLM routing in my orchestrator?

A tiered routing protocol minimizes LLM classification tokens by evaluating pattern matching, session state, and keyword lookups first. It only escalates ambiguous requests to the LLM when deterministic pre-checks fail, conserving computational resources.

When do I need deterministic pre-checks for request orchestration?

Deterministic pre-checks are needed for request orchestration to guarantee minimal computation and safe fallback behavior. By resolving paths via pattern match and session state first, you avoid unnecessary LLM classification tokens and ensure predictable routing.

How does session state and keyword lookup work in routing workflows?

In this routing workflow, session state and keyword lookup act as intermediate decision tiers. The system checks active session data and matches specific keywords to resolve requests deterministically before falling back to LLM classification for remaining ambiguity.

What is the best way to handle ambiguous user requests in a routing system?

The best way to handle ambiguous user requests is a tiered routing protocol with safe fallback behavior. It attempts pattern matching, session state, and keyword lookup first, escalating to LLM classification only when ambiguity remains.

Can I use tiered routing for general routing scenarios outside of SDD?

Yes, you can use tiered routing for general routing scenarios. While it covers SDD-style workflows, the four-tier decision process applies to any orchestrator needing cost-optimized routing with deterministic pre-checks and safe fallback behavior.