skillbox + Jev skill routing

Watch out

The linked page is a post, not documentation, and it describes skillbox only in the author's own terms. What is documented: skillbox is a single MCP server over his skills, built because he was done syncing and symlinking skill files and folders across machines; skills group into bundles, bundles group into profiles, and an agent can be granted the whole box, one bundle or one profile. The Jev change is that the model reads the query and returns the relevant skills instead of the agent searching. Not documented anywhere: the repository URL appears in a reply rather than the post, the prompt, what the model sees when choosing (metadata or full skill text), the output shape, whether several skills can be returned, what happens when none fit, how many candidates are sent, and any accuracy, latency or cost figure. The reported improvement is the author's estimate of roughly 30 turns replaced by one call, with no measurement behind it. The skillbox repository is described only by its summary line, self-hosted, versioned, MCP, scoped clients, and its contents were not part of the captured page. Whether routing is one request per query or batched, and whether a Jev key is required at all, are both unstated. Copy reviewed against the linked page on 2026-10-04.