# CLI Classifier

> Routes typed classifier judgment requests to the hosted Jev transport via mode-registry.json; future classifiers join as modes.

- Skill: `michelkerkmeester/cli-classifier` (Agent Skill, multi-file: 71 files)
- Install (CLI): `npx get-skill add michelkerkmeester/cli-classifier`
- Raw SKILL.md: https://api.skillmd.com/api/skills/michelkerkmeester/cli-classifier/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: MichelKerkmeester (https://skillmd.com/u/michelkerkmeester)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/michelkerkmeester/cli-classifier

---


<!-- Keywords: cli-classifier, cli-jev, cli-usage, jev, typed judgment, jev-mcp, hosted classifier, noul, jev choice, jev score -->

# 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`](./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`](./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

```text
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

- Registry: [`mode-registry.json`](./mode-registry.json).
- Router: [`hub-router.json`](./hub-router.json).
- Root router: [`ROUTER.md`](./ROUTER.md).
- Mode `cli-jev`:
  - [`cli-jev/SKILL.md`](./cli-jev/SKILL.md).
  - [`cli-jev/references/cli-reference.md`](./cli-jev/references/cli-reference.md).
  - [`cli-jev/references/providers-and-models.md`](./cli-jev/references/providers-and-models.md).
  - [`cli-jev/references/integration-patterns.md`](./cli-jev/references/integration-patterns.md).
  - [`cli-jev/references/mcp-server.md`](./cli-jev/references/mcp-server.md).
- Hub metadata: [`description.json`](./description.json), [`graph-metadata.json`](./graph-metadata.json), [`leaf-manifest.json`](./leaf-manifest.json).
- Hub changelog: [`changelog/v0.8.6.0.md`](./changelog/v0.8.6.0.md).

---

## 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.

