cli-classifier - Classifier Transport Hub
One public skill identity for classifier models that return typed judgments: the hosted Jev service and the Deem model served on this machine. This 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-usage |
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 |
cli-deem |
cli-deem |
transport |
A Deem availability check, a probability, one option key, an ordered level or a batch of keyed answers from the local Deem server |
Read and Bash only, mutates nothing |
A caller names its backend. The two transports answer the same judgment types and never fail over to each other 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.
- Starting, stopping or updating the Deem server. That is the operator's step with
deem-ctl.
2. SMART ROUTING
Routing is registry-driven. mode-registry.json lists every packet. hub-router.json decides whether the result is one transport, both transports in order or a defer.
Compiled routing (default-on, flag-gated, additive). Resolve the mode via the compiled router contract first:
node .skilled/bin/compiled-route.cjs --hub cli-classifier --prompt "<task>"
Follow the returned decision: route (use its targets), clarify/defer (disambiguate), reject (refuse). On a {"servingAuthority":"legacy"} sentinel or any error, use the routing below. The front door self-gates on serving-authority. Compiled routing is now the default for cli-classifier. Set SPECKIT_COMPILED_ROUTING=0 to force legacy routing fleet-wide. That is the explicit kill-switch.
Two-Axis Model
packetKind: "transport" marks a bridge to an external tool. It selects a value and never mutates this workspace.
- A transport declares
mutatesWorkspace: false, forbids Write, Edit and Task and is registered under the transport-axis extension.
- The advisor resolves the hub identity and stays blind to the transports (
routingClass: "metadata"). The hub owns the resolution.
- Mode
cli-jev runs over the packet folder cli-usage, as mode research of system-deep-loop runs over deep-research.
Routing Rule
read hub-router.json
-> score routerSignals and vocabularyClasses
-> apply routerPolicy.tieBreak (cli-jev, then cli-deem)
-> read mode-registry.json for packetKind, backendKind, toolSurface and advisorRouting
-> load the selected packet
Outcomes
single: one dominant judgment intent routes to its transport. A Jev request routes to cli-jev, a Deem request to cli-deem.
orderedBundle: a request that names both backends by their aliases, such as a jev judgment checked against a deem judgment, routes to both transports in tieBreak order, cli-jev first.
defer: unclear intent asks for disambiguation rather than guessing a value. A request that names only the hub defers, because the hub name does not choose a backend.
3. HOW IT WORKS
Layout
cli-classifier/
SKILL.md
README.md
mode-registry.json
hub-router.json
ROUTER.md # stage-two control, stage1-only
description.json
graph-metadata.json
leaf-manifest.json
changelog/
manual-testing-playbook/
benchmark/
shared/
cli-usage/ # mode cli-jev
SKILL.md
README.md
references/
assets/
feature-catalog/
manual-testing-playbook/
benchmark/
changelog/
cli-deem/ # mode cli-deem
SKILL.md
README.md
references/
feature-catalog/
scripts/
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 control document, router_state: stage1-only until an author promotes it with a concrete leaf map.
description.json owns hub-doctor metadata.
graph-metadata.json is the one skill-graph identity node for the hub.
Extensions
transport-axis: declares transports: ["cli-deem", "cli-jev"]. The per-hub gate enforces the whole transport contract: routingClass metadata, mutatesWorkspace: false, the forbidden tool set and membership in the axis.
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 both transports 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 the other without the caller asking for it.
- Never start
jev-mcp from a shell, and never start the Deem server from this hub or its packets.
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.
cli-deem health exits non-zero. Deem is not usable for this run, and the hub says so rather than inventing a judgment.
5. REFERENCES
RELATED RESOURCES
manual-testing-playbook/manual-testing-playbook.md - the hub's operator-facing scenario index.
cli-usage/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-classifier-23description: "Routes classifier judgment requests to the cli-jev (hosted Jev) or cli-deem (local Deem) transport through mode-registry.json. Holds no packet-local logic."4allowed-tools: [Read, Bash, Grep, Glob]5version: 1.1.0.06metadata:7 source: https://skillmd.com/skills/michelkerkmeester/cli-classifier-28---910<!-- Keywords: cli-classifier, cli-jev, cli-usage, cli-deem, jev, typed judgment, jev-mcp, local classifier, deem, deem model, deem judgment, deem health, noul, choice, score, local deem server -->1112# cli-classifier - Classifier Transport Hub1314One public skill identity for classifier models that return typed judgments: the hosted Jev service and the Deem model served on this machine. This 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-usage` | 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 |25| `cli-deem` | `cli-deem` | transport | A Deem availability check, a probability, one option key, an ordered level or a batch of keyed answers from the local Deem server | Read and Bash only, mutates nothing |2627A caller names its backend. The two transports answer the same judgment types and never fail over to each other silently.2829### When NOT to Use3031- 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.32- Running `jev-mcp` from a shell. Its stdio carries MCP frames, so it belongs in an MCP host configuration.33- Starting, stopping or updating the Deem server. That is the operator's step with `deem-ctl`.3435---3637## 2. SMART ROUTING3839Routing is registry-driven. `mode-registry.json` lists every packet. `hub-router.json` decides whether the result is one transport, both transports in order or a defer.4041> **Compiled routing (default-on, flag-gated, additive).** Resolve the mode via the compiled router contract first:42> ```bash43> node .skilled/bin/compiled-route.cjs --hub cli-classifier --prompt "<task>"44> ```45> Follow the returned decision: `route` (use its `targets`), `clarify`/`defer` (disambiguate), `reject` (refuse). On a `{"servingAuthority":"legacy"}` sentinel or any error, use the routing below. The front door self-gates on serving-authority. Compiled routing is now the default for `cli-classifier`. Set `SPECKIT_COMPILED_ROUTING=0` to force legacy routing fleet-wide. That is the explicit kill-switch.4647### Two-Axis Model4849- `packetKind: "transport"` marks a bridge to an external tool. It selects a value and never mutates this workspace.50- A transport declares `mutatesWorkspace: false`, forbids `Write`, `Edit` and `Task` and is registered under the `transport-axis` extension.51- The advisor resolves the hub identity and stays blind to the transports (`routingClass: "metadata"`). The hub owns the resolution.52- Mode `cli-jev` runs over the packet folder `cli-usage`, as mode `research` of `system-deep-loop` runs over `deep-research`.5354### Routing Rule5556```text57read hub-router.json58 -> score routerSignals and vocabularyClasses59 -> apply routerPolicy.tieBreak (cli-jev, then cli-deem)60 -> read mode-registry.json for packetKind, backendKind, toolSurface and advisorRouting61 -> load the selected packet62```6364### Outcomes6566- `single`: one dominant judgment intent routes to its transport. A Jev request routes to `cli-jev`, a Deem request to `cli-deem`.67- `orderedBundle`: a request that names both backends by their aliases, such as a jev judgment checked against a deem judgment, routes to both transports in `tieBreak` order, `cli-jev` first.68- `defer`: unclear intent asks for disambiguation rather than guessing a value. A request that names only the hub defers, because the hub name does not choose a backend.6970---7172## 3. HOW IT WORKS7374### Layout7576```text77cli-classifier/78 SKILL.md79 README.md80 mode-registry.json81 hub-router.json82 ROUTER.md # stage-two control, stage1-only83 description.json84 graph-metadata.json85 leaf-manifest.json86 changelog/87 manual-testing-playbook/88 benchmark/89 shared/90 cli-usage/ # mode cli-jev91 SKILL.md92 README.md93 references/94 assets/95 feature-catalog/96 manual-testing-playbook/97 benchmark/98 changelog/99 cli-deem/ # mode cli-deem100 SKILL.md101 README.md102 references/103 feature-catalog/104 scripts/105 changelog/106```107108### Companion Metadata109110- `mode-registry.json` owns `workflowMode`, `packetKind`, `backendKind`, `toolSurface`, packet folder identity, aliases and `advisorRouting`. Its `transport-axis` extension lists the transports.111- `hub-router.json` owns `routerPolicy`, `routerSignals`, `vocabularyClasses` and outcomes.112- `ROUTER.md` is the stage-two control document, `router_state: stage1-only` until an author promotes it with a concrete leaf map.113- `description.json` owns hub-doctor metadata.114- `graph-metadata.json` is the one skill-graph identity node for the hub.115116### Extensions117118- `transport-axis`: declares `transports: ["cli-deem", "cli-jev"]`. The per-hub gate enforces the whole transport contract: routingClass `metadata`, `mutatesWorkspace: false`, the forbidden tool set and membership in the axis.119120---121122## 4. RULES123124### ALWAYS125126- Resolve the packet through `mode-registry.json`. Never hardcode a transport's path in prose-only logic.127- Keep `SKILL.md` thin: routing, invariants and navigation only.128- Keep both transports non-mutating. A transport returns a value and selects. A workflow mode acts.129- Keep every transport `routingClass: "metadata"`. The hub resolves it and the advisor stays blind to the axis.130- Keep exactly one `graph-metadata.json`, at the hub root.131132### NEVER133134- Never grant `Write`, `Edit` or `Task` to a transport.135- Never add a second packet array or a packet-local `graph-metadata.json`.136- Never let a transport complete a task on its own.137- Never fail over from one backend to the other without the caller asking for it.138- Never start `jev-mcp` from a shell, and never start the Deem server from this hub or its packets.139140### ESCALATE IF141142- A request needs a judgment and an edit but no workflow mode is selected. Report the gap instead of mutating from a transport.143- `command -v jev` fails. Mode `cli-jev` is not routable on this machine, and the hub says so rather than inventing a judgment.144- `cli-deem health` exits non-zero. Deem is not usable for this run, and the hub says so rather than inventing a judgment.145146---147148## 5. REFERENCES149150- Registry: [`mode-registry.json`](./mode-registry.json).151- Router: [`hub-router.json`](./hub-router.json).152- Root router: [`ROUTER.md`](./ROUTER.md).153- Mode `cli-jev`: [`cli-usage/SKILL.md`](./cli-usage/SKILL.md), [`cli-usage/references/cli-reference.md`](./cli-usage/references/cli-reference.md), [`cli-usage/references/providers-and-models.md`](./cli-usage/references/providers-and-models.md), [`cli-usage/references/integration-patterns.md`](./cli-usage/references/integration-patterns.md), [`cli-usage/references/mcp-server.md`](./cli-usage/references/mcp-server.md).154- Mode `cli-deem`: [`cli-deem/SKILL.md`](./cli-deem/SKILL.md), [`cli-deem/references/wire-contract.md`](./cli-deem/references/wire-contract.md), [`cli-deem/references/deem-ctl-lifecycle.md`](./cli-deem/references/deem-ctl-lifecycle.md), [`cli-deem/references/model-pin.md`](./cli-deem/references/model-pin.md).155- Hub metadata: [`description.json`](./description.json), [`graph-metadata.json`](./graph-metadata.json), [`leaf-manifest.json`](./leaf-manifest.json).156- Hub changelog: [`changelog/v1.1.0.0.md`](./changelog/v1.1.0.0.md).157158---159160## RELATED RESOURCES161162- `manual-testing-playbook/manual-testing-playbook.md` - the hub's operator-facing scenario index.163- `cli-usage/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.