Private Facets

Private facets let you share skills, agents, commands, and MCP servers without making them available to everyone. The registry controls who can discover and download them. Once installed, they work like any other facet.

​

Visibility

• Public. Anyone can discover and install the facet from the registry.
• Private. Only signed-in users with access can discover and install it.

Each facet declares its visibility in the manifest. Private facets must use a scope you own, such as @ada/review-kit or @acme/review-kit. See the private field for the exact manifest rules and Publish a Facet for the publishing workflow.

​

Your private facets

Your username owns its matching personal scope. A facet named @ada/review-kit belongs to the ada account, and that account must be signed in to publish or access its private versions. Personal private publishing is free during the open beta. At general availability, personal private facets will be available on a paid plan. Anything published during the open beta will remain accessible for free forever.

​

Private facets for teams

An organization owns its matching scope. A facet named @acme/review-kit belongs to the acme organization instead of one person. Organization members with access can discover and install its private versions. Private team publishing is a paid offering during the open beta. Access is activated by request. At general availability, team access becomes self-service.

​

Find and install private facets

Sign in before searching for or installing a private facet. facet search includes private facets your account can access, and facet add installs them by scoped name. The registry checks access on every private read. It does not reveal private facets that your account cannot access.