Dashboard: Catalog
Five screens under the Catalog group, plus a shared detail component.
Registry
Route: /catalog/packages (CatalogBrowse.tsx)
Browse, search, and install packages from configured registries. Row click opens Package Detail; "New Workflow"/similar create-flows from other screens route here rather than to a separate create form (see workflows.md).
Competencies / Skills / Integrations
Routes: /competencies, /skills, /integrations (+ /:id detail)
List views over installed packages of each type. Row click for Competencies and Skills opens the shared Package Detail; Integrations additionally exposes connect/disconnect/reconnect/status actions (see reference/api/integrations.md) directly from its own detail page rather than the generic Package Detail template.
Package Detail
Route: /catalog/packages/:name (PackageDetail.tsx)
One shared component for every package type, reached from Registry, Competencies, Skills, and Integrations rows, and from Workflow Detail's "view package" link. Shows manifest metadata, version history (GET .../versions), dependency resolution, and install/uninstall actions with live installed-state tracking. "Edit in Studio" links to Studio.
Studio
Route: /catalog/studio?type=<competency|skill|workflow|integration>&package=<name> (CatalogStudio.tsx)
A placeholder for all four package types, not a working authoring surface. Every tab in the shipped component renders a "Not yet available" card with an explanatory note and a link to view an example package instead — there is no editor behind any of the four tabs:
| Tab | Status |
|---|---|
| Competency | "Competency authoring (system prompt, settings schema, skill dependencies) isn't built in Studio yet" |
| Skill | "Skill authoring (tool definitions, runtime config) isn't built in Studio yet" |
| Workflow | Workflows enter the system exclusively via Registry install — there is no direct-save path for workflow definitions |
| Integration | "Integration adapter authoring (MCP/REST/SOAP definitions) isn't built in Studio yet" |
Don't confuse this with Workflow Studio (/workflows/:id/studio) — a different, genuinely functional ReactFlow node-graph editor for visualizing/exploring a workflow's step DAG. That one renders and lets you edit a diagram; it doesn't persist changes either, and is reached from Workflow Detail, not from this Catalog Studio screen.
Authoring any package type means editing MANIFEST.toml/payload files directly and using hoziron-cli package build/publish or hoziron-cli catalog registry from the CLI — see the relevant guides/ authoring guide per package type.
Related:
- reference/cli/catalog.md, reference/cli/package.md — the CLI paths that actually author/publish packages today
- guides/competencies/authoring.md, guides/catalog/publishing-packages.md
- workflows.md — Workflow list/detail/Studio/Run Detail
- agents.md — where equipped competencies surface on an agent