Registry

OntoSkills uses a simple distribution model:

The user-facing CLI is ontoskills.

For a live searchable view of the official registry, use the dedicated marketplace page:

Registry Types

The official registry ships with the product. It does not need registry add-source.

Use it when you want published packages maintained by the OntoSkills project:

npx ontoskills search hello
npx ontoskills install marea.greeting/hello
npx ontoskills enable marea.greeting/hello

Third-party registries are opt-in. Add them when another team or community maintains a separate catalog:

ontoskills registry add-source acme https://example.com/index.json
ontoskills registry list

These sources are discoverable by ontoskills search and can be installed like the official registry, but they are not built in.

Raw source repositories contain SKILL.md files and are compiled locally.

ontoskills import-source-repo https://github.com/nextlevelbuilder/ui-ux-pro-max-skill

Source imports are cloned into ~/.ontoskills/skills/vendor/ and compiled outputs are written to ~/.ontoskills/ontoskills/vendor/.

Install compiled packages from a registry:

ontoskills install marea.greeting/hello

Enable or disable installed skills:

ontoskills enable marea.greeting/hello
ontoskills disable marea.greeting/hello

Enabled skills are the ones exposed to OntoMCP.

Update installed components explicitly:

ontoskills update mcp
ontoskills update core
ontoskills update marea.greeting/hello

Rebuild the local registry state and enabled index:

ontoskills rebuild-index

Remove a package or skill:

ontoskills remove marea.greeting/hello

Remove the entire managed user home:

ontoskills uninstall --all

This removes the whole ~/.ontoskills/ tree, including installed binaries, compiled ontologies, locks, caches, and any managed compiler install.

The managed home is organized like this:

~/.ontoskills/
  bin/
  core/
  ontoskills/
  skills/
  state/