Skip to content
Back to search

skill-dock

The open registry and delivery platform for agent skills.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 12 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ZenlixAI/skill-dock with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ZenlixAI/skill-dock'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zenlixai--skill-dock/badge.svg)](/listings/zenlixai--skill-dock)

HTML

<a href="/listings/zenlixai--skill-dock"><img src="/api/listings/zenlixai--skill-dock/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 114 lines
  1. # Skill Dock
  2. [English](README.md) | [简体中文](README.zh-CN.md)
  3. > A self-hosted control plane for discovering, publishing, installing, and governing reusable agent skills.
  4. Skill Dock has two operational surfaces:
  5. - the **catalog server**, which owns catalog data, hosted releases, install resolution, packaging, visibility, governance, and audit records;
  6. - the **`skills` CLI**, which discovers sources, installs skills locally, refreshes local state, and invokes catalog workflows.
  7. Bundles live in an external npm-compatible artifact repository. A bundle becomes a published release only when the catalog server accepts its release record.
  8. ## Workflows
  9. | Workflow | Command | Authority |
  10. | --- | --- | --- |
  11. | Catalog discovery | `skills find` | Catalog server; optional `skills.sh` results |
  12. | Installation | `skills add` | Server for registry packages; CLI for local and git sources |
  13. | Local inventory | `skills list`, `skills remove` | Local files and lock files |
  14. | Registry refresh | `skills update` | Server release resolution |
  15. | Source refresh | `skills sync` | Recorded local or git source |
  16. | Authoring | `skills init`, `skills inspect` | Local filesystem |
  17. | Publication | `skills publish`, `skills import-*` | Server packaging and release workflow |
  18. 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.
  19. ## Docker Compose
  20. 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:
  21. ```bash
  22. cp .env.example .env
  23. # Edit .env and replace every sample password and token.
  24. docker compose up --build -d
  25. ```
  26. The Catalog API is available at <http://localhost:8080/api/v1>; its npm proxy is available at <http://localhost:8080/repository/skills-npm/>. Verify the service and an authenticated catalog read with:
  27. ```bash
  28. curl -fsS http://localhost:8080/readyz
  29. curl -fsS http://localhost:8080/api/v1/skills \
  30. -H "Authorization: Bearer <reader-token>"
  31. ```
  32. Stop it with `docker compose down`; add `-v` only when you also want to remove local database and artifact data.
  33. For a production deployment, use the [production deployment guide](docs/03-deployment.md). 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.
  34. ## Build and run Catalog with Dockerfile
  35. 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.
  36. ```bash
  37. docker build -f zarf/docker/local/Dockerfile -t skill-registry-catalog .
  38. docker run --rm -p 8080:8080 -v skill-registry-data:/var/lib/skill-registry \
  39. -e SKILL_REGISTRY_READER_TOKEN=reader-secret \
  40. -e SKILL_REGISTRY_AUTHORING_TOKEN=authoring-secret \
  41. -e SKILL_REGISTRY_PUBLISHER_TOKEN=publisher-secret \
  42. skill-registry-catalog
  43. ```
  44. Use real secrets and configure PostgreSQL plus an npm-compatible artifact repository before production. See [deployment](docs/03-deployment.md) and [server configuration](docs/01-server-architecture.md).
  45. ## Documentation
  46. - [Documentation index](docs/README.md)
  47. - [CLI package README](apps/skills-cli/README.md)
  48. ## Website
  49. The site lives in `apps/site` and deploys as a Cloudflare Worker with static assets. The `/registry` page is a public skills.sh directory: search, all-time/trending/hot views, and an in-site detail drawer. The Worker serves the SPA and reverse-proxies `/api/skills-sh/*` to skills.sh, which avoids browser CORS and keeps the HTML parsing/sanitization on the edge.
  50. The site is bilingual. English pages live at `/`, and Simplified Chinese pages live under `/zh` (`/zh/registry`, `/zh/privacy`, `/zh/terms`). The header language menu preserves the current page, query string, and hash when switching. UI copy lives in `apps/site/src/lib/content.en.ts` and `apps/site/src/lib/content.zh.ts`; `npm run prerender` emits both locales with localized metadata and `hreflang` alternates.
  51. Deploy it with:
  52. ```bash
  53. cd apps/site
  54. npm run deploy
  55. ```
  56. Worker runtime settings live in `wrangler.jsonc` (`SKILLS_SH_ENABLED`, `SKILLS_SH_BASE_URL`). For local full-stack development, run `npm run dev:worker` after a build, or point the Vite dev proxy at the Worker with `VITE_SKILLS_SH_PROXY` (default `http://127.0.0.1:8787`). The Go catalog also exposes `/api/skills-sh/*` aliases for self-hosted/Docker deployments. See [website deployment](docs/03-deployment.md#website-deployment) for details.
  57. ## Configuration
  58. ### Server
  59. | Variable | Purpose |
  60. | --- | --- |
  61. | `SKILL_REGISTRY_DATABASE_URL` | SQLite or PostgreSQL URL |
  62. | `SKILL_REGISTRY_SHARED_WORKSPACE_ROOT` | Writable packaging workspace root |
  63. | `SKILL_REGISTRY_ARTIFACT_READ_URL` | Artifact repository URL for server reads |
  64. | `SKILL_REGISTRY_PUBLIC_INSTALL_URL` | Artifact URL exposed to clients |
  65. | `SKILLS_SH_ENABLED` | Enable skills.sh discovery (default `true`) |
  66. | `SKILL_REGISTRY_SKILLS_SH_URL` | skills.sh provider URL |
  67. | `SKILL_REGISTRY_READER_TOKEN` | Reader token |
  68. | `SKILL_REGISTRY_AUTHORING_TOKEN` | Authoring token |
  69. | `SKILL_REGISTRY_PUBLISHER_TOKEN` | Publisher token |
  70. | `SKILL_REGISTRY_INSTALL_TARGET_MODE` | `proxy` or `direct` |
  71. ### CLI
  72. | Variable | Purpose |
  73. | --- | --- |
  74. | `SKILLS_REGISTRY_URL` | Catalog server base URL |
  75. | `SKILLS_REGISTRY_TOKEN` | Bearer token for catalog requests |
  76. | `SKILLS_REGISTRY_ROLE` | Development role header |
  77. | `NPM_CONFIG_USERCONFIG` | npm credentials used for direct npm traffic |
  78. ## License
  79. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.