---
id: "question-skill-discovery"
type: "open-question"
source_timestamps: ["21:30:00", "22:00:00"]
tags: ["ecosystem", "infrastructure"]
related: ["entity-product-openbrain", "action-use-community-repo"]
resolutionPath: "The emergence of dominant package managers or registries (similar to npm for Node.js) specifically designed for LLM skills, moving beyond ad-hoc GitHub repositories."
sources: ["s43-file-format-agreement"]
sourceVaultSlug: "s43-file-format-agreement"
originDay: 43
---
# How will the ecosystem standardize skill discovery?

## Open Question

How will the ecosystem standardize **skill discovery**?

## Why It Matters

Today, skill sharing happens in ad-hoc GitHub repositories like [[entity-product-openbrain]]. There is no canonical registry, no semantic versioning standard, and no signature/trust model for skills. As organizations rely more on agent pipelines, the discovery problem becomes acute.

## Resolution Path

Likely resolution: the emergence of dominant **package managers or registries** (similar to npm for Node.js or PyPI for Python) specifically designed for LLM skills — with:

- semantic versioning
- discoverability metadata
- trust signals (signatures, audits, popularity)
- testing/eval scores attached to versions

## Related

- [[action-use-community-repo]] — current best practice in the absence of a registry