ZenlixAI / skill-dock

# Skill Registry
English | 简体中文
> A self-hosted control plane for discovering, publishing, installing, and governing reusable agent skills.
Skill Registry has two operational surfaces:
- the **catalog server**, which owns catalog data, hosted releases, install resolution, packaging, visibility, governance, and audit records;
- the **`skills` CLI**, which discovers sources, installs skills locally, refreshes local state, and invokes catalog workflows.
Bundles live in an external npm-compatible artifact repository. A bundle becomes a published release only when the catalog server accepts its release record.
## Workflows
| Workflow | Command | Authority |
| --- | --- | --- |
| Catalog discovery | `skills find` | Catalog server; optional `skills.sh` results |
| Installation | `skills add` | Server for registry packages; CLI for local and git sources |
| Local inventory | `skills list`, `skills remove` | Local files and lock files |
| Registry refresh | `skills update` | Server release resolution |
| Source refresh | `skills sync` | Recorded local or git source |
| Authoring | `skills init`, `skills inspect` | Local filesystem |
| Publication | `skills publish`, `skills import-*` | Server packaging and release workflow |
After installing a local or git source, the CLI attempts a server import by default. This best-effort operation does not change the installation into a registry install. Set `syncOnAdd` to `false` in the merged global or project `skills.config.json` to disable it.
## Docker Compose
For local development, use the root Compose file. It starts Catalog, PostgreSQL, and a local npm-compatible artifact repository; it does not start the static website:
 [code] 
The Catalog API is available at ; its npm proxy is available at . Verify the service and an authenticated catalog read with:
 [code] 
Stop it with `docker compose down`; add `-v` only when you also want to remove local database and artifact data.
For a production deployment, use the production deployment guide. It runs only Catalog and PostgreSQL; connect Catalog to an external npm-compatible artifact repository and put a TLS reverse proxy in front of it.
## Build and run Catalog with Dockerfile
Build and run the standalone Catalog image with SQLite for local evaluation. This command does not configure an external artifact repository, so it is not a complete registry-install or publication deployment. Configure PostgreSQL, an npm-compatible artifact repository, and the public install URL before using it for production.
 [code] 
Use real secrets and configure PostgreSQL plus an npm-compatible artifact repository before production. See deployment and server configuration.
## Documentation
- Documentation index
- CLI package README
## Configuration
### Server
| Variable | Purpose |
| --- | --- |
| `SKILL_REGISTRY_DATABASE_URL` | SQLite or PostgreSQL URL |
| `SKILL_REGISTRY_SHARED_WORKSPACE_ROOT` | Writable packaging workspace root |
| `SKILL_REGISTRY_ARTIFACT_READ_URL` | Artifact reposit