Skip to content
Back to search

skillhub

Self-hosted, open-source agent skill registry for enterprises. Publish & version skill packages, govern with RBAC and audit logs, deploy on-premise with Docker or Kubernetes.

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 11 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/iflytek/skillhub 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/iflytek/skillhub'

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/iflytek--skillhub/badge.svg)](/listings/iflytek--skillhub)

HTML

<a href="/listings/iflytek--skillhub"><img src="/api/listings/iflytek--skillhub/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Start the full local stack with:

rm -rf /tmp/skillhub-runtime
curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up

The default command pulls the `latest` stable release images. Use `--version edge` if you want the newest build from `main`.

**Configure public URL (recommended for production):**

curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com

The `--public-url` parameter sets the public access URL for your SkillHub instance. This ensures: - CLI install commands show the correct registry URL - Agent setup instructions display the correct skill.md URL - OAuth callbacks and device auth links work properly

**For users in China (Aliyun mirror):**

curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest

If deployment runs into problems, clear the existing runtime home and retry.

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 · 655 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src="./skillhub-logo.svg" alt="SkillHub Logo" width="120" height="120" />
  3. <h1>SkillHub</h1>
  4. <p>An enterprise-grade, open-source agent skill registry — publish, discover, and manage reusable skill packages across your organization. </p>
  5. </div>
  6. <div align="center">
  7. [![DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/iflytek/skillhub)
  8. [![Docs](https://img.shields.io/badge/docs-zread.ai-4A90E2?logo=gitbook&logoColor=white)](https://zread.ai/iflytek/skillhub)
  9. [![Discord](https://img.shields.io/badge/discord-join-5865F2?logo=discord&logoColor=white)](https://discord.gg/qHYvtDNPHS)
  10. [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](./LICENSE)
  11. [![Build](https://github.com/iflytek/skillhub/actions/workflows/publish-images.yml/badge.svg)](https://github.com/iflytek/skillhub/actions/workflows/publish-images.yml)
  12. [![Docker](https://img.shields.io/badge/docker-ghcr.io-2496ED?logo=docker&logoColor=white)](https://ghcr.io/iflytek/skillhub)
  13. [![Java](https://img.shields.io/badge/java-21-ED8B00?logo=openjdk&logoColor=white)](https://openjdk.org/projects/jdk/21/)
  14. [![React](https://img.shields.io/badge/react-19-61DAFB?logo=react&logoColor=black)](https://react.dev)
  15. [![GitHub Stars](https://img.shields.io/github/stars/iflytek/skillhub?style=social)](https://github.com/iflytek/skillhub/stargazers)
  16. [![GitHub Watchers](https://img.shields.io/github/watchers/iflytek/skillhub?style=social)](https://github.com/iflytek/skillhub/watchers)
  17. </div>
  18. <div align="center">
  19. <a href="https://trendshift.io/repositories/24384?utm_source=repository-badge&amp;utm_medium=badge&amp;utm_campaign=badge-repository-24384" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/repositories/24384" alt="iflytek%2Fskillhub | Trendshift" width="250" height="55"/></a>&nbsp;&nbsp;<a href="https://aaif.io/" target="_blank" rel="noopener noreferrer"><img src="https://cdn.sanity.io/images/4o10fa7h/production/16dd7d8270b673d376cadca831ab3d5ea003bb89-838x203.svg" alt="AAIF Associate Member" height="55"/></a>
  20. </div>
  21. <div align="center">
  22. [English](./README.md) | [中文](./README_zh.md)
  23. </div>
  24. ---
  25. <div align="center">
  26. <img src="https://xfyun-doc.xfyun.cn/lc-sp-skillhub-demo-1775551643410.gif" alt="SkillHub Demo" width="800" />
  27. </div>
  28. SkillHub is a self-hosted platform that gives teams a private,
  29. governed place to share agent skills. Publish a skill package, push
  30. it to a namespace, and let others find it through search or
  31. install it via CLI. Built for on-premise deployment behind your
  32. firewall, with the same polish you'd expect from a public registry.
  33. > ⭐ If SkillHub fits your team, **star** the repo to help other teams find it, and **Watch → Custom → Releases** to get notified when a new version ships.
  34. ## Share Great Skills
  35. Great Skills become more valuable when they are shared. If you have a Skill that has
  36. proved useful in real work or everyday life, share it with the SkillHub community and
  37. help grow an open, practical Skill ecosystem. We welcome Skills for daily life, office
  38. work, learning and research, travel and events, content creation, data analysis, and
  39. software development—not only engineering workflows.
  40. High-quality community contributions may join the curated starter collection, making new
  41. SkillHub deployments useful from day one. You do not need to finish the full adaptation
  42. before joining in: [open an issue](https://github.com/iflytek/skillhub/issues/new/choose)
  43. with the Skill's source and the problem it solves, or submit a PR by following the
  44. [Skill sharing guide](./builtin-skills/README.md).
  45. ## Documentation
  46. - **[User Guide](https://iflytek.github.io/skillhub/)** — [中文](docs/skillhub/quickstart.md) / [English](docs/skillhub/en/quickstart.md): find, install, and use skills in your agent
  47. - **[CLI reference](cli/README.md)** — Authentication, installation, upgrades, namespace synchronization, and local inventory
  48. - **[Skill Suites](docs/skillhub/en/guide/skill-suites.md)** — Install a versioned collection and use its entry skill; [Suite Bundle import](docs/skillhub/en/guide/suite-bundle.md) is the separate authoring workflow
  49. - **[Self-hosting](docs/skillhub/en/guide/deployment.md)** — Docker Compose configuration and upgrades; [Kubernetes](docs/skillhub/en/guide/kubernetes.md) for clusters
  50. - **[Developer workflow](docs/dev-workflow.md)** — Source development, checks, and documentation maintenance; [operations reference](docs/09-deployment.md) for deployment details
  51. - **[Generated code overview](https://zread.ai/iflytek/skillhub)** — Supplementary architecture exploration; repository source and versioned documentation define current behavior
  52. - **[Python Examples](./examples/python)** — Search, download, and publish skills via the REST API
  53. ## Governance and Safety
  54. - **[Privacy and Data Governance](docs/PRIVACY_AND_DATA_GOVERNANCE.md)** —
  55. Data categories, operator responsibilities, retention, portability, and incident
  56. handling for public and self-hosted instances
  57. - **[Content Safety](docs/CONTENT_SAFETY.md)** — Package safety expectations,
  58. review and reporting controls, appeals, and child-safety responsibilities
  59. - **[Code of Conduct](CODE_OF_CONDUCT.md)** — Community standards and the private
  60. reporting channel
  61. - **[Security Policy](https://github.com/iflytek/.github/blob/main/SECURITY.md)** —
  62. Private vulnerability reporting and coordinated disclosure
  63. ## Highlights
  64. - **Self-Hosted & Private** — Deploy on your own infrastructure.
  65. Keep proprietary skills behind your firewall with full data
  66. sovereignty. One `make dev-all` command to get running locally.
  67. - **Publish & Version** — Upload agent skill packages with semantic
  68. versioning, custom tags (`beta`, `stable`), and automatic
  69. `latest` tracking.
  70. - **Discover** — Full-text search with filters by namespace,
  71. downloads, ratings, and recency. Visibility rules ensure
  72. users only see what they're authorized to.
  73. - **Team Namespaces** — Organize skills under team or global scopes.
  74. Each namespace has its own members, roles (Owner / Admin /
  75. Member), and publishing policies.
  76. - **Review & Governance** — Team admins review within their namespace;
  77. platform admins gate promotions to the global scope. Governance
  78. actions are audit-logged for compliance.
  79. - **Social Features** — Star skills, rate them, and track downloads.
  80. Build a community around your organization's best practices.
  81. - **Account Merging** — Consolidate multiple OAuth identities and
  82. API tokens under a single user account.
  83. - **API Token Management** — Generate scoped tokens for CLI and
  84. programmatic access with prefix-based secure hashing.
  85. - **CLI-First** — Native REST API plus a compatibility layer for
  86. existing ClawHub-style registry clients. Native CLI APIs are the
  87. primary supported path while protocol compatibility continues to
  88. expand.
  89. - **Pluggable Storage** — Local filesystem for development, S3 /
  90. MinIO for production. Swap via config.
  91. - **Internationalization** — Multi-language support with i18next: English, Simplified Chinese, Russian, and Korean.
  92. ## Quick Start
  93. To host your own registry using release images, start with:
  94. ```bash
  95. curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up
  96. ```
  97. The default command pulls the `latest` stable release images. Use `--version edge` if you want the newest build from `main`.
  98. **Configure public URL (recommended for production):**
  99. ```bash
  100. curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
  101. ```
  102. The `--public-url` parameter sets the public access URL for your SkillHub instance. This ensures:
  103. - CLI install commands show the correct registry URL
  104. - Agent setup instructions display the correct skill.md URL
  105. - OAuth callbacks and device auth links work properly
  106. **For users in China (Aliyun mirror):**
  107. ```bash
  108. curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest
  109. ```
  110. Keep the existing runtime home when rerunning or updating the deployment. The
  111. runtime script reuses its `.env.release` file; deleting the directory discards
  112. your custom configuration, including the public URL and generated anonymous
  113. download cookie secret.
  114. If deployment runs into problems, inspect the `ps` and `logs` lifecycle commands
  115. printed by the runtime script, then retry `up` with the same runtime home. If you
  116. intentionally want a fresh configuration, back up `.env.release` before clearing
  117. the runtime home.
  118. ## SkillHub CLI
  119. Install and manage Agent skills from the command line:
  120. ```bash
  121. # Install CLI
  122. npm install -g @astron-team/skillhub
  123. # Or run directly
  124. npx @astron-team/skillhub@latest version
  125. # Login
  126. skillhub login --token sk_xxx --registry https://skill.xfyun.cn
  127. # Search and install skills
  128. skillhub search pdf
  129. skillhub install pdf-parser --agent codex
  130. # List installed skills
  131. skillhub list
  132. ```
  133. 📖 Full guide: [docs/skillhub/en/guide/cli.md](docs/skillhub/en/guide/cli.md)
  134. ### Prerequisites
  135. - Docker & Docker Compose for container dependencies and release deployments
  136. - For source development: Java 21, Node.js 22.13+ (22.x) or 24.x, and the pnpm version declared in `web/package.json`
  137. - For CLI development: Bun (see [`cli/README.md`](cli/README.md))
  138. ### Local Development
  139. ```bash
  140. make dev-all
  141. ```
  142. > **For developers in China**: If Maven dependency download times out, configure Aliyun mirror. See [Local Development Guide](docs/dev-workflow.md) for details.
  143. Then open:
  144. - Web UI: `http://localhost:3000`
  145. - Backend API: `http://localhost:8080`
  146. By default, `make dev-all` starts the backend with the `local` profile.
  147. In that mode, local development keeps the mock-auth users below and also
  148. creates a password-based bootstrap admin account by default:
  149. - `local-user` for normal publishing and namespace operations
  150. - `local-admin` with `SUPER_ADMIN` for review and admin flows
  151. Use them with the `X-Mock-User-Id` header in local development.
  152. The local bootstrap admin is enabled by default in `application-local.yml`:
  153. - username: `admin`
  154. - password: `ChangeMe!2026`
  155. - To disable it, set `BOOTSTRAP_ADMIN_ENABLED=false` before starting the backend.
  156. Stop everything with:
  157. ```bash
  158. make dev-all-down
  159. ```
  160. Only when deliberately discarding local dependency data, reset with:
  161. ```bash
  162. make dev-all-reset
  163. ```
  164. Run `make help` to see all available commands.
  165. Useful backend commands:
  166. ```bash
  167. make test
  168. make test-backend-app
  169. make build-backend-app
  170. ```
  171. Do not run `./mvnw -pl skillhub-app clean test` directly under `server/`.
  172. `skillhub-app` depends on sibling modules in the same repo, and a standalone clean build
  173. can fall back to stale artifacts from the local Maven repository, which surfaces misleading
  174. `cannot find symbol` and signature-mismatch errors. Use `-am`, or the `make test-backend-app`
  175. and `make build-backend-app` targets above.
  176. For the full development workflow (local dev → staging → PR), see [docs/dev-workflow.md](docs/dev-workflow.md).
  177. ### API Contract Sync
  178. OpenAPI types for the web client are checked into the repository.
  179. When backend API contracts change, regenerate the SDK and commit the
  180. updated generated file:
  181. ```bash
  182. make generate-api
  183. ```
  184. For a stricter end-to-end drift check, run:
  185. ```bash
  186. ./scripts/check-openapi-generated.sh
  187. ```
  188. This starts local dependencies, boots the backend, regenerates the
  189. frontend schema, and fails if the checked-in SDK is stale.
  190. ### Container Runtime
  191. Published runtime images are built by GitHub Actions and pushed to GHCR.
  192. This is the supported path for anyone who wants a ready-to-use local
  193. environment without building the backend or frontend on their machine.
  194. Published server and web images target `linux/amd64`, `linux/arm64`, and
  195. `linux/riscv64`; the scanner image currently targets `linux/amd64` and
  196. `linux/arm64`.
  197. **Quick deployment with curl:**
  198. ```bash
  199. # Default (GHCR images)
  200. curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --public-url https://skillhub.your-company.com
  201. # Aliyun mirror (recommended for users in China)
  202. curl -fsSL https://imageless.oss-cn-beijing.aliyuncs.com/runtime.sh | sh -s -- up --aliyun --public-url https://skillhub.your-company.com --version latest
  203. ```
  204. **Deployment parameters:**
  205. | Parameter | Description | Example |
  206. |-----------|-------------|---------|
  207. | `--public-url <url>` | Public access URL (recommended) | `--public-url https://skill.example.com` |
  208. | `--version <tag>` | Specific image tag | `--version v0.2.25` |
  209. | `--ref <git-ref>` | Git ref for deployment files (GitHub raw mode) | `--ref v0.2.25` |
  210. | `--aliyun` | Use Aliyun mirror (China) | `--aliyun` |
  211. | `--home <dir>` | Runtime directory | `--home /opt/skillhub` |
  212. | `--no-scanner` | Disable security scanner | `--no-scanner` |
  213. `--version` selects image tags; it does not pin the deployment files. By default,
  214. those files come from `main`. To pin the installer, Compose file, environment
  215. template and application image tag together, use a released Git ref and tag:
  216. ```bash
  217. curl -fsSL https://raw.githubusercontent.com/iflytek/skillhub/v0.2.25/scripts/runtime.sh | sh -s -- up --ref v0.2.25 --version v0.2.25 --home /opt/skillhub --public-url https://skillhub.your-company.com
  218. ```
  219. This example uses GitHub raw and requires access to it. With the updated installer,
  220. `--aliyun` keeps only the three core files (`runtime.sh`, `compose.release.yml`, and
  221. `.env.release.example`) on the OSS root. The five optional analytics/Collector
  222. configuration files are fetched on demand through `gh-proxy.org`, using `--ref`
  223. (or `SKILLHUB_REF`, default `main`), just like the ordinary GitHub source. There is
  224. no installer-side commit or checksum list to update when editing these templates.
  225. Every use downloads the selected ref again; `main` is mutable and proxy caching
  226. means it is not guaranteed to reflect the latest commit immediately. For production,
  227. select a reviewed release tag or commit with `--ref` and a matching image `--version`.
  228. OSS core files are still not versioned by `--ref`; the publisher must keep them
  229. compatible with the chosen release. `--version` alone does not select a file ref.
  230. Download failures, empty responses and obvious wrong-format responses stop the optional
  231. operation without replacing the existing destination. This basic format check is
  232. not full YAML validation or cryptographic source verification: using the proxy
  233. requires trusting that third party. Availability is not guaranteed, and there is
  234. no silent fallback to another ref.
  235. Likewise, a custom `SKILLHUB_RAW_BASE` takes precedence over the Git-ref URL.
  236. The explicit custom source retains its existing behavior and does not use the
  237. default proxy path. Neither OSS core files nor an explicit custom source should
  238. be described as pinned by `--ref`.
  239. The script preserves an existing `.env.release`; record its settings and explicit
  240. image overrides separately. Pinning the application tag does not freeze every
  241. dependency image or replace a database backup.
  242. > **Important**: Configure `--public-url` for production deployments to ensure CLI install commands and Agent setup instructions display the correct URLs.
  243. For sub-path deployments, keep the public URL and runtime base path aligned in
  244. `.env.release`: set `SKILLHUB_PUBLIC_BASE_URL=https://skill.example.com/skillhub`,
  245. `SKILLHUB_WEB_BASE_PATH=/skillhub/`, and `SKILLHUB_WEB_API_BASE_URL=/skillhub`.
  246. **Manual deployment:**
  247. 1. Copy the runtime environment template.
  248. 2. Pick an image tag.
  249. 3. Start the stack with Docker Compose.
  250. ```bash
  251. cp .env.release.example .env.release
  252. ```
  253. Recommended image tags:
  254. - `SKILLHUB_VERSION=latest` for the latest stable release (default)
  255. - `SKILLHUB_VERSION=edge` for the latest `main` build
  256. - `SKILLHUB_VERSION=vX.Y.Z` for a fixed release
  257. Start the runtime:
  258. ```bash
  259. make validate-release-config
  260. docker compose --env-file .env.release -f compose.release.yml up -d
  261. ```
  262. Then open:
  263. - Web UI: `SKILLHUB_PUBLIC_BASE_URL` 对应的地址
  264. - Backend API: `http://localhost:8080`
  265. Stop it with:
  266. ```bash
  267. docker compose --env-file .env.release -f compose.release.yml down
  268. ```
  269. The runtime stack uses its own Compose project name, so it does not
  270. collide with containers from `make dev-all`.
  271. The production Compose stack now defaults to the `docker` profile only.
  272. It does not enable local mock auth. The release template (`.env.release.example`)
  273. enables the bootstrap admin by default, so zero-config quickstart via
  274. `runtime.sh` works out of the box:
  275. - username: `admin`
  276. - password: `ChangeMe!2026`
  277. Recommended production baseline:
  278. - set `SKILLHUB_PUBLIC_BASE_URL` to the final HTTPS entrypoint
  279. - if the service is published under a sub-path such as `/skillhub/`, set
  280. `SKILLHUB_WEB_BASE_PATH=/skillhub/` and `SKILLHUB_WEB_API_BASE_URL=/skillhub`
  281. as well
  282. - keep PostgreSQL / Redis bound to `127.0.0.1`
  283. - use external S3 / OSS via `SKILLHUB_STORAGE_S3_*`
  284. - change `BOOTSTRAP_ADMIN_PASSWORD` to a strong password (`validate-release-config.sh` rejects the default `ChangeMe!2026`)
  285. - rotate or disable the bootstrap admin after initial setup
  286. - run `make validate-release-config` before `docker compose up -d`
  287. If the GHCR package remains private, run `docker login ghcr.io` before
  288. `docker compose up -d`.
  289. ### Upload Allowlist Override
  290. Skill package upload validation uses the default extension allowlist from
  291. [`SkillPackagePolicy.java`](./server/skillhub-domain/src/main/java/com/iflytek/skillhub/domain/skill/validation/SkillPackagePolicy.java).
  292. `SkillPublishProperties` uses that same list by default for
  293. `skillhub.publish.allowed-file-extensions`.
  294. If you need to replace the default allowlist at runtime, set:
  295. ```bash
  296. SKILLHUB_PUBLISH_ALLOWED_FILE_EXTENSIONS=.md,.json,.xsd,.xsl,.dtd,.docx,.xlsx,.pptx
  297. ```
  298. Spring Boot binds this environment variable to
  299. `skillhub.publish.allowed-file-extensions`. When set, it replaces the default
  300. allowlist instead of appending to it.
  301. ### Monitoring
  302. The optional [`monitoring/`](./monitoring) directory provides Prometheus and Grafana deployment examples. It is not a ready-to-scrape backend configuration: the default application exposes only `health` and `info` Actuator endpoints. `/actuator/prometheus` also requires the `SUPER_ADMIN` or `AUDITOR` role under the current route policy, while the example scraper has no credentials configured.
  303. Before enabling monitoring, configure metrics exposure and an authenticated access path appropriate to your deployment; verify that the scraper can actually read the endpoint. Do not make management endpoints public merely to satisfy the example. The example targets `host.docker.internal:8080`, which must resolve to your backend from the Prometheus container.
  304. After adapting that configuration, start the optional stack:
  305. ```bash
  306. cd monitoring
  307. docker compose -f docker-compose.monitoring.yml up -d
  308. ```
  309. Prometheus uses port `9090` and Grafana uses port `3001`. Replace the example Grafana administrator credentials before exposing it. Confirm scrape targets are healthy and metrics are present; starting the containers alone does not establish monitoring coverage. For tracing and request correlation, see the [observability developer guide](docs/observability-developer-guide.md).
  310. ## Kubernetes
  311. Basic Kubernetes manifests are available under [`deploy/k8s/`](./deploy/k8s):
  312. - `configmap.yaml`
  313. - `secret.yaml.example`
  314. - `backend-deployment.yaml`
  315. - `frontend-deployment.yaml`
  316. - `services.yaml`
  317. - `ingress.yaml`
  318. For a configurable deployment with bundled PostgreSQL and Redis dependencies,
  319. use the Helm chart under [`charts/skillhub/`](./charts/skillhub):
  320. ```bash
  321. helm dependency build ./charts/skillhub
  322. helm upgrade --install skillhub ./charts/skillhub \
  323. --namespace skillhub \
  324. --create-namespace \
  325. -f values-production.yaml
  326. ```
  327. See the [Helm chart guide](./charts/skillhub/README.md) for required secrets,
  328. Ingress/TLS, external data services, storage migration, and upgrade constraints.
  329. Apply them after creating your own secret:
  330. ```bash
  331. kubectl apply -f deploy/k8s/configmap.yaml
  332. kubectl apply -f deploy/k8s/secret.yaml
  333. kubectl apply -f deploy/k8s/backend-deployment.yaml
  334. kubectl apply -f deploy/k8s/frontend-deployment.yaml
  335. kubectl apply -f deploy/k8s/services.yaml
  336. kubectl apply -f deploy/k8s/ingress.yaml
  337. ```
  338. ## Smoke Test
  339. A lightweight smoke test script is available at [`scripts/smoke-test.sh`](./scripts/smoke-test.sh).
  340. Run it against a local backend:
  341. ```bash
  342. ./scripts/smoke-test.sh http://localhost:8080
  343. ```
  344. Local Compose and staging runs can keep using one backend URL. For an ingress
  345. deployment where the public URL exposes application APIs but keeps Actuator on
  346. the backend service, set a separate Actuator target:
  347. ```bash
  348. ACTUATOR_BASE_URL=http://skillhub-server:8080 \
  349. ./scripts/smoke-test.sh https://skillhub.example.com
  350. ```
  351. The health check requires an Actuator JSON response, so an HTML SPA fallback is
  352. reported as a routing or target error instead of a successful health response.
  353. Admin label-management smoke checks run only when current admin credentials are
  354. supplied explicitly:
  355. ```bash
  356. SMOKE_ADMIN_USERNAME=admin SMOKE_ADMIN_PASSWORD='current-password' \
  357. ./scripts/smoke-test.sh http://localhost:8080
  358. ```
  359. Use `SMOKE_ADMIN_CHECKS=false` for persistent environments where only non-admin
  360. smoke checks should run. The script no longer falls back to bootstrap admin
  361. password defaults.
  362. ## Architecture
  363. <div align="center">
  364. <img src="./docs/skillhub/public/diagrams/architecture-overview.png" alt="SkillHub system architecture" width="900" />
  365. </div>
  366. **Backend (Spring Boot 3.2.3, Java 21):**
  367. - Multi-module Maven project with clean architecture
  368. - Modules: app, domain, auth, search, storage, infra
  369. - PostgreSQL with Flyway migrations (16 by default, 17 verified)
  370. - Redis for session management
  371. - S3/MinIO for skill package storage
  372. **Frontend (React 19, TypeScript, Vite):**
  373. - TanStack Router for routing
  374. - TanStack Query for data fetching
  375. - Tailwind CSS + Radix UI for styling
  376. - OpenAPI TypeScript for type-safe API client
  377. - i18next for internationalization
  378. ## SkillHub and the Agent Skills Ecosystem
  379. SkillHub is a **registry and governance platform** — not a skill collection.
  380. It is complementary to open skill catalogs such as
  381. [`anthropics/skills`](https://github.com/anthropics/skills): that repository
  382. popularized the **Agent Skill format** (a `SKILL.md` with `name` / `description`
  383. frontmatter plus supporting files) and ships a curated set of example skills.
  384. SkillHub is where your organization **hosts, versions, governs, and distributes**
  385. those skills privately.
  386. | | [`anthropics/skills`](https://github.com/anthropics/skills) | **SkillHub** |
  387. |---|---|---|
  388. | What it is | A curated collection of example Agent Skills + the format spec | A self-hosted registry & governance platform for skills |
  389. | Layer | Content — the skills themselves | Infrastructure — hosting, versioning, discovery, access control |
  390. | Hosting | Public GitHub repository | Your own infrastructure, behind your firewall |
  391. | Versioning | Git history | Semantic versions, tags (`beta` / `stable`), `latest` tracking |
  392. | Access control | Public | Namespaces, RBAC, review & audit logging |
  393. | Distribution | Clone / copy files | Full-text search + CLI install |
  394. Because SkillHub speaks the same `SKILL.md` format, skills from `anthropics/skills`
  395. — or any Agent Skill folder — publish straight into your registry:
  396. ```bash
  397. # Grab a skill from an open collection...
  398. git clone https://github.com/anthropics/skills
  399. # ...and publish it into your private SkillHub registry
  400. export SKILLHUB_REGISTRY=https://skillhub.your-company.com
  401. export SKILLHUB_TOKEN=YOUR_API_TOKEN
  402. npx @astron-team/skillhub@latest publish ./skills/<category>/<skill-name>
  403. ```
  404. > ⚖️ **Licensing**: honor each skill's own license when republishing. Most skills in
  405. > `anthropics/skills` are Apache 2.0, but the document skills (DOCX/PDF/PPTX/XLSX) are
  406. > source-available rather than open source — check the skill's `LICENSE` before redistributing.
  407. **In short: use collections like `anthropics/skills` for content, and SkillHub to
  408. distribute it across your organization under governance.**
  409. ## Usage with Agent Platforms
  410. SkillHub works as a skill registry backend for several agent platforms. Point any of the clients below at your SkillHub instance to publish, discover, and install skills.
  411. ### [OpenClaw](https://github.com/openclaw/openclaw)
  412. [OpenClaw](https://github.com/openclaw/openclaw) is an open-source agent skill CLI. Configure it to use your SkillHub endpoint as the registry:
  413. ```bash
  414. # Configure registry URL
  415. export CLAWHUB_REGISTRY=https://skillhub.your-company.com
  416. # Authenticate once if needed
  417. clawhub login --token YOUR_API_TOKEN
  418. # Search and install skills
  419. npx clawhub search email
  420. npx clawhub install my-skill
  421. npx clawhub install my-namespace--my-skill
  422. # Publishing uses the first-party SkillHub CLI
  423. export SKILLHUB_REGISTRY=https://skillhub.your-company.com
  424. export SKILLHUB_TOKEN=YOUR_API_TOKEN
  425. npx @astron-team/skillhub@latest publish ./my-skill --namespace my-space
  426. ```
  427. `my-space--my-skill` is the canonical compat slug. SkillHub parses it as
  428. namespace `my-space` plus skill slug `my-skill`.
  429. ClawHub compatibility covers search, inspection, and installation. Its publish
  430. protocol is not compatible with SkillHub; use the first-party CLI shown above.
  431. > 💡 **Tip**: The above commands are not only applicable to OpenClaw, but also to other CLI Coding Agents or Agent assistants by specifying the installation directory (`--dir`). For example: `npx clawhub --dir ~/.claude/skills install my-skill`
  432. 📖 **[Complete OpenClaw Integration Guide →](./docs/openclaw-integration.md)**
  433. ### [Hermes Agent](https://github.com/NousResearch/hermes-agent)
  434. [Hermes Agent](https://github.com/NousResearch/hermes-agent) uses the standard `SKILL.md` format and recursively discovers skills under `$HERMES_HOME/skills/`. Use SkillHub CLI's explicit `--dir` option to install a complete SkillHub package into Hermes without a registry adapter, then verify it with `hermes skills list`.
  435. 📖 **[Complete Hermes Agent Integration Guide →](./docs/hermes-integration-en.md)**
  436. ### [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)
  437. [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (`dsh`) discovers standard `SKILL.md` packages from `.dsh/skills` and the shared `.agents/skills` roots. Install directly into its native user directory with the first-party SkillHub CLI:
  438. ```bash
  439. skillhub install my-skill --agent dsh --scope user
  440. ```
  441. Project-scoped installs use `<repository>/.dsh/skills`; run them from the repository root. dsh watches its skill roots, so newly installed skills are discovered without restarting the process.
  442. 📖 **[Complete DeepSeek Harness Integration Guide →](./docs/dsh-integration-en.md)**
  443. ### [HarnessClaw Engine](https://github.com/harnessclaw/harnessclaw-engine)
  444. [HarnessClaw Engine](https://github.com/harnessclaw/harnessclaw-engine) is a Go LLM programming assistant engine that exposes its capabilities over WebSocket. It loads skills from `SKILL.md` files with YAML frontmatter and parameter substitution, scanning each configured directory for `skill-name/SKILL.md` (default `~/.harnessclaw/workspace/skills/`, with earlier directories taking priority on name conflicts). Install a SkillHub package straight into that directory with the CLI's `--dir` option, no registry adapter required:
  445. ```bash
  446. npx clawhub --dir ~/.harnessclaw/workspace/skills install my-skill
  447. ```
  448. ### [AstronClaw](https://agent.xfyun.cn/astron-claw)
  449. [AstronClaw](https://agent.xfyun.cn/astron-claw) is a cloud AI assistant built on OpenClaw's core capabilities, providing 24/7 online service through enterprise platforms like WeChat Work, DingTalk, and Feishu. It features a built-in skill system with over 130 official skills. You can connect it to a self-hosted SkillHub registry to enable one-click skill installation, search repository, dialogue-based automatic installation, and even custom skills management within your organization.
  450. ### [Loomy](https://loomy.xunfei.cn/)
  451. [Loomy](https://loomy.xunfei.cn/) is a desktop AI work partner focusing on real office scenarios. It integrates deeply with local files and system tools to build efficient automated workflows for individuals and small teams. By connecting Loomy to your SkillHub registry, you can easily discover and install organization-specific skills to enhance your local desktop automation and productivity.
  452. ### [astron-agent](https://github.com/iflytek/astron-agent)
  453. [astron-agent](https://github.com/iflytek/astron-agent) is the iFlytek Astron agent framework. Skills stored in SkillHub can be referenced and loaded by astron-agent, enabling a governed, versioned skill lifecycle from development to production.
  454. ## Related Projects
  455. SkillHub is part of the **[iFlytek Astron](https://github.com/iflytek)** open-source ecosystem. If SkillHub is useful to you, these sibling projects may be too:
  456. - **[astron-agent](https://github.com/iflytek/astron-agent)** — Enterprise-grade, commercial-friendly agentic workflow platform for building next-generation SuperAgents. Skills published to SkillHub can be loaded and run by astron-agent.
  457. - **[astron-rpa](https://github.com/iflytek/astron-rpa)** — Agent-ready RPA suite with out-of-the-box automation tools, built for individuals and enterprises.
  458. ---
  459. > 🌟 **Show & Tell** — Have you built something with SkillHub? We'd love to hear about it!
  460. > Share your use case, integration, or deployment story in the
  461. > [**Discussions → Show and Tell**](https://github.com/iflytek/skillhub/discussions/categories/show-and-tell) category.
  462. ## Contributing
  463. Contributions are welcome. Please open an issue first to discuss
  464. what you'd like to change.
  465. - Contribution guide: [`CONTRIBUTING.md`](./CONTRIBUTING.md)
  466. - Code of conduct: [`CODE_OF_CONDUCT.md`](./CODE_OF_CONDUCT.md)
  467. ## 📞 Support
  468. - 💬 **Community Discussion**: [GitHub Discussions](https://github.com/iflytek/skillhub/discussions)
  469. - 🐛 **Bug Reports**: [Issues](https://github.com/iflytek/skillhub/issues)
  470. - 👾 **Discord**: [Join our Server](https://discord.gg/qHYvtDNPHS)
  471. - 👥 **WeChat Work Group**:
  472. ![WeChat Work Group](https://github.com/iflytek/astron-agent/raw/main/docs/imgs/WeCom_Group.png)
  473. ## License
  474. Apache License 2.0

Ratings and comments

Sign in to rate this skill.

Sign in

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