What problem does Intent-Router solve?

It compiles a vague request into a typed IntentSpec contract before work starts: it looks up what the repo, ticket system or docs already answer, asks only what no file can answer, flags contradictions or ambiguous readings, and refuses to emit while the intent is underspecified.

How does Intent-Router relate to Jev?

The project describes itself as the input layer for routers and typed-decision models like Jev and Laya: it produces the typed contract that a decision model or router then acts on, and it checks delivered work against that contract one constraint at a time.

How do I install Intent-Router?

Run npx skills add angel291592/Intent-Router. The README says there is no install, no API key and no dependencies because it is a skill; a manual install path is documented for agents the installer does not know.

Where does the IntentSpec live?

It is written to .intent/ .intent.yaml before the reply that carries it. Probed fields carry evidence pointers, the file records its own state, and the result of checking delivered work against the spec is written back into the same file.

Do I need a TypeSafe or other API key?

No key is needed to use the skill itself, per the README's no install, no API key, no dependencies line. It ships with an L0 prompt-only backend badge and works without installing anything.

What do the project's evals show?

The 2026-09-24 delivery eval compares 5 bare runs with 3 skill runs: every skill run asked exactly one question and all 3 delivered caches stated their failure policy, while none of the 5 bare deliveries did (N=5 bare, N=3 skill).

Who maintains Intent-Router and under what licence?

It is maintained by GitHub user angel291592 and released under the MIT licence, with a public eval report and CI workflow linked from the README.

Jev directory

CommunityJev Agents & MCP

Intent-Router

An intent compiler for AI agents: it probes what files and tickets already answer, asks only what they can't, and emits a typed IntentSpec YAML saved to .intent/<intent>.intent.yaml before work is routed. The README positions it as the input layer for routers and typed-decision models like Jev and Laya.

See highlights Open github.com

Stars: 763
Language: Python
License: MIT
Reading time: 2 min
Published by: Community
Author: angel291592
Last verified: Oct 2026

angel291592/intent-router

User repository on GitHub

View on GitHub

Intent compiler for AI agents — converges vague requests into typed IntentSpec contracts (probe, ask, or halt before routing), the input layer for routers and typed-decision models like Jev & Laya

Forks: 92
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

Tagscommunity catalog-import madewithjev intent skills decision-model

Works forJev for Routing Jev for Decision gating

Used inJev for Software & DevTools

Languages: Python
Platforms: CLI
Capabilities: Open source

Highlights

Probes the repo, tickets and docs first, then asks the one question no file can answer before emitting its contract.
Every run ends in a machine-readable IntentSpec saved to .intent/<intent>.intent.yaml before the reply that carries it.
A later session reads that file before probing: answered questions are never asked again and settled contracts are implemented as written.
Install is one line with no API key and no dependencies: npx skills add angel291592/Intent-Router.
The project's own eval reports every skill run asked exactly one question and 3 of 3 delivered caches stated a failure policy, against 0 of 5 bare runs.

Quickstart

bash

npx skills add angel291592/Intent-Router

Watch out

Copy reviewed against the repo README on 2026-10-15; the delivery comparison and the 8-of-10-case run numbers are the project's own evals with small samples (N=5 bare, N=3 with the skill) and were not independently reproduced.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

MCP tool routing: Jev in front of the tool call

Oct 16, 2026

Tool menus can outgrow the context that reads them. The catalog's Jev-based routers and gates narrow the list: benchmarked tool search, per-tool scoring, fail-closed approvals, and WebMCP in the browser.

Jev Agents & MCP#mcp#tool-routing#agents

Read article

Approval policies for coding agents: hooks, guards, and gateways

Oct 16, 2026

How the Jev guard family turns coding-agent permissions into auto-approve, deny, or ask: hooks that enforce, guards that fail safe, and gateways that gate generation.

Jev Agents & MCP#coding-agents#guardrails#hooks