cli-classifier - Classifier Transport Hub
One public skill identity for typed classifier judgments. The hub holds the hosted Jev transport as mode cli-jev today, with its own packet. A future classifier backend joins as a new mode and packet. The hub holds no packet-local logic; it routes by workflowMode through mode-registry.json and uses hub-router.json for router policy, signals and outcomes.
1. WHEN TO USE
Use this skill when a request needs a typed judgment from a classifier or needs to know whether one is usable.
| Mode |
Packet |
Kind |
Use it for |
Tool posture |
cli-jev |
cli-jev |
transport |
A hosted Jev judgment through the jev CLI or its MCP surface: a probability, one option key, an ordered score position or a batch of keyed answers |
Read and Bash only, mutates nothing |
This is the hub's only mode today. A future classifier backend belongs in its own new mode and packet. A caller names the classifier it wants, and transports never fail over silently.
When NOT to Use
- Work that needs an edit, a review or a multi-step process. Dispatch the judgment to a transport and pair it with a workflow mode.
- Running
jev-mcp from a shell. Its stdio carries MCP frames, so it belongs in an MCP host configuration.
2. SMART ROUTING
Stage one scores hub-router.json routerSignals against vocabularyClasses and applies routerPolicy.tieBreak to select a classifier mode.
vocabularyClasses is the one authored mode vocabulary.
The vocabulary check at .skilled/skills/sk-doc/sk-create-skill/scripts/ci-hub-vocabulary-source.cjs fails on the alias, stage-two, triggers and packets legs; stage-two-reverse only reports.
Stage two lives in the root ROUTER.md, which maps each classifier intent to packet-local leaves.
The hub selects a mode, and ROUTER.md selects that mode's leaves.
The advisor routes classifier requests to the single identity cli-classifier.
Today, cli-jev is the only registered mode.
Resolve a mode with node .skilled/bin/compiled-route.cjs --hub cli-classifier --prompt "<task>".
Follow the decision: route loads targets, clarify and defer ask for disambiguation, and reject refuses.
routerPolicy.defaultMode is null, so an unclear request or one naming only this hub defers for clarification rather than selecting cli-jev.
Run the compiled-routing directive in ROUTER.md before selecting hub resources.
3. HOW IT WORKS
Terms
workflowMode: the public mode key this hub resolves to a packet, cli-jev today.
packetKind: the axis a mode sits on, where transport marks a bridge to an external tool that selects a value and never mutates this workspace.
backendKind: which backend runs the mode, recorded per mode in mode-registry.json.
mode-registry.json: the registry that owns each mode's workflowMode, packetKind, backendKind, toolSurface, packet folder, aliases and advisorRouting.
hub-router.json: stage one's authored policy, holding routerPolicy, routerSignals, vocabularyClasses and the outcomes.
vocabularyClasses: the one authored mode vocabulary that routerSignals are scored against.
tieBreak: the routerPolicy order applied to select a mode when more than one scores.
transport-axis: the mode-registry.json extension that declares the registered transports, cli-jev today.
routingClass: "metadata": the class that keeps a transport out of the advisor, so the hub resolves it and the advisor stays blind to the axis.
- leaf: a packet-local resource file that a selected mode loads, named in
leaf-manifest.json and mapped by ROUTER.md.
ROUTER.md: the stage-two surface router, which maps each classifier intent to the packet-local leaves of its mode.
defer: the outcome that asks for disambiguation rather than guessing a classifier.
Layout
cli-classifier/
SKILL.md
README.md
mode-registry.json
hub-router.json
ROUTER.md # stage-two surface router, active
description.json
graph-metadata.json
leaf-manifest.json
changelog/
manual-testing-playbook/
benchmark/
shared/
cli-jev/ # mode cli-jev
SKILL.md
README.md
references/
assets/
feature-catalog/
manual-testing-playbook/
benchmark/
changelog/
Companion Metadata
mode-registry.json owns workflowMode, packetKind, backendKind, toolSurface, packet folder identity, aliases and advisorRouting. Its transport-axis extension lists the transports.
hub-router.json owns routerPolicy, routerSignals, vocabularyClasses and outcomes.
ROUTER.md is the stage-two surface router, router_state: active: the Jev intents map to packet-local leaves from leaf-manifest.json.
description.json owns hub-doctor metadata.
graph-metadata.json is the one skill-graph identity node for the hub.
Extensions
transport-axis: declares the currently registered transport, cli-jev. The per-hub gate enforces the whole transport contract: routingClass metadata, mutatesWorkspace: false, the forbidden tool set and membership in the axis.
Offline Measurement
benchmark/injection-screen/score-injection-screen.mjs measures one question offline: whether Jev's noul spots text that tries to instruct an agent better than flag-nothing or a fixed lexical screen. Its default run makes zero model calls, and --jev runs the hosted classifier only after its gate passes.
The injection screen runs that measured question as an advisory on Claude Code, Devin, OpenCode and Pi. It adds one line when a fetched section reads as instructions aimed at an agent, and never blocks the fetch.
shared/scripts/jev-transport.mjs answers choice and noul questions through Pi's classifier runtime first when no transport is named, and through the jev CLI wherever Pi's preflight fails. JEV_TRANSPORT=jev forces the CLI. shared/scripts/tests/jev-transport.test.mjs pins both paths with stubs and no socket.
4. RULES
ALWAYS
- Resolve the packet through
mode-registry.json. Never hardcode a transport's path in prose-only logic.
- Keep
SKILL.md thin: routing, invariants and navigation only.
- Keep every registered transport non-mutating. A transport returns a value and selects. A workflow mode acts.
- Keep every transport
routingClass: "metadata". The hub resolves it and the advisor stays blind to the axis.
- Keep exactly one
graph-metadata.json, at the hub root.
NEVER
- Never grant
Write, Edit or Task to a transport.
- Never add a second packet array or a packet-local
graph-metadata.json.
- Never let a transport complete a task on its own.
- Never fail over from one backend to another without the caller asking for it.
- Never start
jev-mcp from a shell.
ESCALATE IF
- A request needs a judgment and an edit but no workflow mode is selected. Report the gap instead of mutating from a transport.
command -v jev fails. Mode cli-jev is not routable on this machine, and the hub says so rather than inventing a judgment. Point the user at uv tool install jev-cli.
5. REFERENCES
6. RELATED RESOURCES
manual-testing-playbook/manual-testing-playbook.md - the hub's operator-facing scenario index.
cli-jev/manual-testing-playbook/manual-testing-playbook.md - the cli-jev transport's own scenario index.
.skilled/skills/sk-doc/sk-create-skill/references/parent-skill/parent-skills-nested-packets.md - the parent-hub pattern this hub follows.
1---2name: cli-classifier3description: "Routes typed classifier judgment requests to the hosted Jev transport via mode-registry.json; future classifiers join as modes."4allowed-tools: [Read, Bash, Grep, Glob]5version: 0.8.9.06metadata:7 source: https://skillmd.com/skills/michelkerkmeester/cli-classifier8---910<!-- Keywords: cli-classifier, cli-jev, cli-usage, jev, typed judgment, jev-mcp, hosted classifier, noul, jev choice, jev score -->1112# cli-classifier - Classifier Transport Hub1314One public skill identity for typed classifier judgments. The hub holds the hosted Jev transport as mode `cli-jev` today, with its own packet. A future classifier backend joins as a new mode and packet. The hub holds no packet-local logic; it routes by `workflowMode` through `mode-registry.json` and uses `hub-router.json` for router policy, signals and outcomes.1516---1718## 1. WHEN TO USE1920Use this skill when a request needs a typed judgment from a classifier or needs to know whether one is usable.2122| Mode | Packet | Kind | Use it for | Tool posture |23|------|--------|------|------------|--------------|24| `cli-jev` | `cli-jev` | transport | A hosted Jev judgment through the `jev` CLI or its MCP surface: a probability, one option key, an ordered score position or a batch of keyed answers | Read and Bash only, mutates nothing |2526This is the hub's only mode today. A future classifier backend belongs in its own new mode and packet. A caller names the classifier it wants, and transports never fail over silently.2728### When NOT to Use2930- Work that needs an edit, a review or a multi-step process. Dispatch the judgment to a transport and pair it with a workflow mode.31- Running `jev-mcp` from a shell. Its stdio carries MCP frames, so it belongs in an MCP host configuration.3233---3435## 2. SMART ROUTING3637Stage one scores `hub-router.json` `routerSignals` against `vocabularyClasses` and applies `routerPolicy.tieBreak` to select a classifier mode.38`vocabularyClasses` is the one authored mode vocabulary.39The vocabulary check at `.skilled/skills/sk-doc/sk-create-skill/scripts/ci-hub-vocabulary-source.cjs` fails on the `alias`, `stage-two`, `triggers` and `packets` legs; `stage-two-reverse` only reports.4041Stage two lives in the root [`ROUTER.md`](./ROUTER.md), which maps each classifier intent to packet-local leaves.42The hub selects a mode, and `ROUTER.md` selects that mode's leaves.4344The advisor routes classifier requests to the single identity `cli-classifier`.45Today, `cli-jev` is the only registered mode.46Resolve a mode with `node .skilled/bin/compiled-route.cjs --hub cli-classifier --prompt "<task>"`.47Follow the decision: `route` loads `targets`, `clarify` and `defer` ask for disambiguation, and `reject` refuses.48`routerPolicy.defaultMode` is `null`, so an unclear request or one naming only this hub defers for clarification rather than selecting `cli-jev`.49Run the compiled-routing directive in [`ROUTER.md`](./ROUTER.md) before selecting hub resources.5051---5253## 3. HOW IT WORKS5455### Terms5657- **`workflowMode`**: the public mode key this hub resolves to a packet, `cli-jev` today.58- **`packetKind`**: the axis a mode sits on, where `transport` marks a bridge to an external tool that selects a value and never mutates this workspace.59- **`backendKind`**: which backend runs the mode, recorded per mode in `mode-registry.json`.60- **`mode-registry.json`**: the registry that owns each mode's `workflowMode`, `packetKind`, `backendKind`, `toolSurface`, packet folder, aliases and `advisorRouting`.61- **`hub-router.json`**: stage one's authored policy, holding `routerPolicy`, `routerSignals`, `vocabularyClasses` and the outcomes.62- **`vocabularyClasses`**: the one authored mode vocabulary that `routerSignals` are scored against.63- **`tieBreak`**: the `routerPolicy` order applied to select a mode when more than one scores.64- **`transport-axis`**: the `mode-registry.json` extension that declares the registered transports, `cli-jev` today.65- **`routingClass: "metadata"`**: the class that keeps a transport out of the advisor, so the hub resolves it and the advisor stays blind to the axis.66- **leaf**: a packet-local resource file that a selected mode loads, named in `leaf-manifest.json` and mapped by `ROUTER.md`.67- **`ROUTER.md`**: the stage-two surface router, which maps each classifier intent to the packet-local leaves of its mode.68- **`defer`**: the outcome that asks for disambiguation rather than guessing a classifier.6970### Layout7172```text73cli-classifier/74 SKILL.md75 README.md76 mode-registry.json77 hub-router.json78 ROUTER.md # stage-two surface router, active79 description.json80 graph-metadata.json81 leaf-manifest.json82 changelog/83 manual-testing-playbook/84 benchmark/85 shared/86 cli-jev/ # mode cli-jev87 SKILL.md88 README.md89 references/90 assets/91 feature-catalog/92 manual-testing-playbook/93 benchmark/94 changelog/95```9697### Companion Metadata9899- `mode-registry.json` owns `workflowMode`, `packetKind`, `backendKind`, `toolSurface`, packet folder identity, aliases and `advisorRouting`. Its `transport-axis` extension lists the transports.100- `hub-router.json` owns `routerPolicy`, `routerSignals`, `vocabularyClasses` and outcomes.101- `ROUTER.md` is the stage-two surface router, `router_state: active`: the Jev intents map to packet-local leaves from `leaf-manifest.json`.102- `description.json` owns hub-doctor metadata.103- `graph-metadata.json` is the one skill-graph identity node for the hub.104105### Extensions106107- `transport-axis`: declares the currently registered transport, `cli-jev`. The per-hub gate enforces the whole transport contract: routingClass `metadata`, `mutatesWorkspace: false`, the forbidden tool set and membership in the axis.108109### Offline Measurement110111`benchmark/injection-screen/score-injection-screen.mjs` measures one question offline: whether Jev's `noul` spots text that tries to instruct an agent better than flag-nothing or a fixed lexical screen. Its default run makes zero model calls, and `--jev` runs the hosted classifier only after its gate passes.112113The injection screen runs that measured question as an advisory on Claude Code, Devin, OpenCode and Pi. It adds one line when a fetched section reads as instructions aimed at an agent, and never blocks the fetch.114115`shared/scripts/jev-transport.mjs` answers `choice` and `noul` questions through Pi's classifier runtime first when no transport is named, and through the `jev` CLI wherever Pi's preflight fails. `JEV_TRANSPORT=jev` forces the CLI. `shared/scripts/tests/jev-transport.test.mjs` pins both paths with stubs and no socket.116117---118119## 4. RULES120121### ALWAYS122123- Resolve the packet through `mode-registry.json`. Never hardcode a transport's path in prose-only logic.124- Keep `SKILL.md` thin: routing, invariants and navigation only.125- Keep every registered transport non-mutating. A transport returns a value and selects. A workflow mode acts.126- Keep every transport `routingClass: "metadata"`. The hub resolves it and the advisor stays blind to the axis.127- Keep exactly one `graph-metadata.json`, at the hub root.128129### NEVER130131- Never grant `Write`, `Edit` or `Task` to a transport.132- Never add a second packet array or a packet-local `graph-metadata.json`.133- Never let a transport complete a task on its own.134- Never fail over from one backend to another without the caller asking for it.135- Never start `jev-mcp` from a shell.136137### ESCALATE IF138139- A request needs a judgment and an edit but no workflow mode is selected. Report the gap instead of mutating from a transport.140- `command -v jev` fails. Mode `cli-jev` is not routable on this machine, and the hub says so rather than inventing a judgment. Point the user at `uv tool install jev-cli`.141142---143144## 5. REFERENCES145146- Registry: [`mode-registry.json`](./mode-registry.json).147- Router: [`hub-router.json`](./hub-router.json).148- Root router: [`ROUTER.md`](./ROUTER.md).149- Mode `cli-jev`:150 - [`cli-jev/SKILL.md`](./cli-jev/SKILL.md).151 - [`cli-jev/references/cli-reference.md`](./cli-jev/references/cli-reference.md).152 - [`cli-jev/references/providers-and-models.md`](./cli-jev/references/providers-and-models.md).153 - [`cli-jev/references/integration-patterns.md`](./cli-jev/references/integration-patterns.md).154 - [`cli-jev/references/mcp-server.md`](./cli-jev/references/mcp-server.md).155- Hub metadata: [`description.json`](./description.json), [`graph-metadata.json`](./graph-metadata.json), [`leaf-manifest.json`](./leaf-manifest.json).156- Hub changelog: [`changelog/v0.8.6.0.md`](./changelog/v0.8.6.0.md).157158---159160## 6. RELATED RESOURCES161162- `manual-testing-playbook/manual-testing-playbook.md` - the hub's operator-facing scenario index.163- `cli-jev/manual-testing-playbook/manual-testing-playbook.md` - the `cli-jev` transport's own scenario index.164- `.skilled/skills/sk-doc/sk-create-skill/references/parent-skill/parent-skills-nested-packets.md` - the parent-hub pattern this hub follows.