Small decisions. Interesting possibilities.Submit contentSubmit
Jev Agent Skill Router preview

Jev Agent Skill Router

A typed router that sends each request to one specialist skill, to no skill, or to human review.

Added to Jevfast

How it uses Jev

A first noul question decides whether the request needs a specialised workflow at all. Choice questions then rank candidate skills in batches of eight, each candidate described only by its public description, and a final request combines a choice over the survivors with the specialist and review checks. Code applies the probability and confidence thresholds that turn an answer into a skill, no skill, or human review.

What Jev decides

Source-defined final routing question (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION

Choose the single specialist skill needed, or no skill, or human review.

STATE

The final call carries the request text and a Choice whose criteria are the surviving skill names plus two reserved options. The same request also asks whether a specialist is needed and whether clarification is needed; each fit check is its own noul question per candidate.

JEV · CHOICE
  1. pdf-report
  2. spreadsheet-cleanup
  3. __no_skill__
  4. __review__
Question 2 · needs specialist
YOUR APP
INSTRUCTION

Is the actual task a specialised workflow rather than an ordinary reply?

STATE

The final call carries the request text and a Choice whose criteria are the surviving skill names plus two reserved options. The same request also asks whether a specialist is needed and whether clarification is needed; each fit check is its own noul question per candidate.

JEV · NOUL
YesNo
Question 3 · needs review
YOUR APP
INSTRUCTION

Is clarification needed to identify one kind of work to perform?

STATE

The final call carries the request text and a Choice whose criteria are the surviving skill names plus two reserved options. The same request also asks whether a specialist is needed and whether clarification is needed; each fit check is its own noul question per candidate.

JEV · NOUL
YesNo

App workflow

  1. Name the candidates

    The caller supplies the request and a catalogue of skills, each with a public description.

  2. Ask whether a skill is needed

    A noul question separates specialised workflows from ordinary replies.

  3. Rank in batches

    Candidate skills are split into batches of eight and each batch is answered with its own Choice question.

  4. Pick the survivor

    A final request chooses among the survivors, with explicit options for no skill and human review.

  5. Apply the policy

    Confidence and probability thresholds decide whether the route is used, fell back, or handed to a person.

Why it is interesting

Routing is split into a bounded tournament instead of one huge choice, so a large catalogue stays within prompt limits. The policy also treats requests and descriptions as data, so an instruction inside a request cannot force a route.