← Blog

· Hive AI

Knolo's Two Catalogs: Why Knowledge Packs and Skill Packs Stay Separate

Knolo keeps knowledge packs and skill packs in separate catalogs with one pin-check trust rule. What the hub does, what it does not, and what is still open.

Knolo is the open-source, local-first Knowledge Image runtime and format: Apache-2.0, published on npm as @knolo/core, and developed in the open in the Knolo core repository on GitHub. On 10 November 2026 the project merged a short planning document, docs/hub/COMMUNITY.md (PR #147), that sets one product rule for the open Knolo ecosystem: Knolo has two catalogs, and they stay separate.

This note explains that rule, why it matters for anyone building on Knolo, and what is still open.

The two Knolo catalogs

Catalog Identity Artifact
Knowledge packs publisher/slug@version .knolo Knowledge Image
Skill packs publisher/name knolo-skill-pack-v1

A Knolo knowledge pack is the evidence: a portable, digest-pinned Knowledge Image you query and verify locally. A Knolo skill pack is guidance for an agent, plus an optional pinned image it should search before acting. They have different identities, different commands and different lifecycles. Skill packs are not merged into knolo publish or knolo add, and knowledge packs are not installed as skills.

Keeping them apart means a consumer can always tell what kind of artifact they are trusting. Guidance can change how an agent behaves, while evidence changes what it is allowed to cite. Mixing the two in one namespace would blur exactly the line Knolo exists to make checkable.

What the Knolo Hub does, and what it does not

The plan states it plainly: the hub stores packs and pins. It does not run a model, and it does not answer questions. Installing a pack is a local decision by whoever runs the agent. Clients download bytes directly from content-addressed storage, so the hub is a catalog and not a proxy.

The same document restates how Knolo results should be read. A search hit is data. A receipt is an integrity check. SATISFIED means the evidence requirements were met; it does not mean a claim is proven. The read-only integrations, @knolo/mcp and @knolo/ai-sdk, stay read-only: they search, fetch and verify mounts already on disk and never download or publish a catalog pack.

One Knolo trust rule for both catalogs

The install pin check is the rule for both catalogs. If the downloaded bytes do not match the pin, the install is refused and nothing is written. For knowledge packs the hub already runs a secret scan during verification, owners can yank a version (yank returns 410 and keeps the digest visible), and signed-in users can report a pack.

For skill packs, trust today is the pin plus the hub account that published it. The plan deliberately adds no new publisher signature format, and it says outright that a pin does not prove the text is true. Reading of both catalogs is public; only publish and yank need a kno_ token with the publish scope.

What is still open in the Knolo ecosystem

The plan lists follow-ups without overstating them. Shipped in @knolo/cli 6.2.2 (PR #148): knolo setup, public skill install, and knolo skill search and info. Still to come, and tracked as hub work:

  • Skill versions, with @version, a latest pointer and a version endpoint. Until then, a skill name has one pin, and a different pin returns 409 pin_conflict.
  • Running the existing pack secret scanner on skill text before a skill is listed, failing closed.
  • Skill yank and report, with 410 keeping the digest visible.
  • A knolo-skills.lock.json written by install once versions exist.

These are the kinds of changes Knolo routes through public process. The Knolo lifecycle page describes how work moves from proposal to stable, the Knolo Improvement Proposals index tracks formal changes, and the Knolo specifications and compatibility pages cover what a conforming runtime must agree on.

Building on Knolo

If you are writing a client, a registry mirror or an agent integration, the two-catalog rule is the contract to design against: pin everything, verify locally, and treat guidance and evidence as different things. Developer documentation for the hub and CLI is on knolo.dev, and the source and issue tracker are in the Knolo GitHub repository.

knolo · open-technology · hub · skills · trust