As a ToolHive user or Administrator, I want to discover, browse and manage Skills through the registry so that I can find available skills for Claude Code in a centralised catalog instead of searching scattered sources

[rdimitrov]

The following are some of the details around implementing this. If desired, those could be addressed as sub-issues. They are only meant to guide the implementation but not strictly describe it.

The implementation would consist of changes on ToolHive Registry Server but also on the toolhive types used to describe a file-based registry

Changes on ToolHive Registry Server

• Skills follow the skills.json specification from skillet
• Core fields supported: namespace, name, description, version, packages
• Optional fields supported: status, title, license, compatibility, allowedTools, repository, icons, metadata
• Skills stored in existing subregistry format alongside servers array
• OCI package references supported
• Git package references supported
• Use the extensions API format and match the existing functionality from the servers, i.e. publish, list, search, etc.

Changes on ToolHive

• Update the registry-related Go types to define the skills.json format and include it in the file-based registries.

Out of Scope

• Skill-to-MCP-server dependencies

Definition of Done

Skills can be listed, searched, published, deleted, and retrieved via the API, and appear in the registry UI.

References:

• THV-0029: Skills Support in ToolHive Registry Server (MVP) toolhive-rfcs#29
• https://docs.google.com/document/d/17P8LLu4SKHIJLtyltu9Htp7-aja7DJl_NV4NRCyrz5U/edit?tab=t.0#heading=h.tvmrxs3du88f