capabilities — the system's map of itself (registry + curator)

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

Commands, APIs and runtime behavior described below are conditional examples for a compatible upstream installation; they are not evidence of execution in this package.

The upstream registry organizes available module descriptions into a layered tree for planning. Inventory entries must be checked against actual installed capabilities.

python -m skills.capabilities.cli map               # ASCII layered system tree
python -m skills.capabilities.cli list --json       # the registry
python -m skills.capabilities.cli curate "test my desktop app"

Layers (the arborescence)

Each skill's layer comes from a layer: field in its SKILL.md frontmatter, else a built-in map, else ACT. The generated docs/system-map.txt snapshot belongs to the upstream runtime and is not bundled here.

The curator

curate(goal) ranks the capabilities most relevant to a goal (local lexical match) — the librarian that hands the Conductor (and you) the right branches of the tree to use. Built on [[skill-finder]].

This registry is the foundation for the Conductor (goal → decision tree → ordered plan of capabilities, executed local-first) and the control loop (measure → adapt). Related: [[skill-finder]], [[auto-router]], [[bootstrap]].